Skip to main content
Unix & Linux

Return to Answer

add a note about root/sudo
Source Link
A.B
A.B
  • 39.5k
  • 2
  • 87
  • 134

With 192.168.0.10/24 already set on petalinux's eth0 linked to oip's eno1, to allow communication between oip and petalinux, run this on oipoip (as root user, meaning it probably should be prepended by sudo ):

ip addr add 192.168.0.11/24 dev eno1

And that's it: each should now be able to reach the other using the other's IP address: 192.168.0.10 or 192.168.0.11 (both being within 192.168.0.0/24). I don't see any strange problem here, except the superfluous information (libvirt and Docker are running too).

Note: petalinux won't be reachable directly from the PC (mentioned in comment) nor can it reach "outside" through oip for at least two reasons: Ubuntu's Docker sets filter/FORWARD to DROP, and the PC probably doesn't have an adequate route to 192.168.0.0/24. But that's not part of the question.

With 192.168.0.10/24 already set on petalinux's eth0 linked to oip's eno1, to allow communication between oip and petalinux, run this on oip:

ip addr add 192.168.0.11/24 dev eno1

And that's it: each should now be able to reach the other using the other's IP address: 192.168.0.10 or 192.168.0.11 (both being within 192.168.0.0/24). I don't see any strange problem here, except the superfluous information (libvirt and Docker are running too).

Note: petalinux won't be reachable directly from the PC (mentioned in comment) nor can it reach "outside" through oip for at least two reasons: Ubuntu's Docker sets filter/FORWARD to DROP, and the PC probably doesn't have an adequate route to 192.168.0.0/24. But that's not part of the question.

With 192.168.0.10/24 already set on petalinux's eth0 linked to oip's eno1, to allow communication between oip and petalinux, run this on oip (as root user, meaning it probably should be prepended by sudo ):

ip addr add 192.168.0.11/24 dev eno1

And that's it: each should now be able to reach the other using the other's IP address: 192.168.0.10 or 192.168.0.11 (both being within 192.168.0.0/24). I don't see any strange problem here, except the superfluous information (libvirt and Docker are running too).

Note: petalinux won't be reachable directly from the PC (mentioned in comment) nor can it reach "outside" through oip for at least two reasons: Ubuntu's Docker sets filter/FORWARD to DROP, and the PC probably doesn't have an adequate route to 192.168.0.0/24. But that's not part of the question.

Source Link
A.B
A.B
  • 39.5k
  • 2
  • 87
  • 134

With 192.168.0.10/24 already set on petalinux's eth0 linked to oip's eno1, to allow communication between oip and petalinux, run this on oip:

ip addr add 192.168.0.11/24 dev eno1

And that's it: each should now be able to reach the other using the other's IP address: 192.168.0.10 or 192.168.0.11 (both being within 192.168.0.0/24). I don't see any strange problem here, except the superfluous information (libvirt and Docker are running too).

Note: petalinux won't be reachable directly from the PC (mentioned in comment) nor can it reach "outside" through oip for at least two reasons: Ubuntu's Docker sets filter/FORWARD to DROP, and the PC probably doesn't have an adequate route to 192.168.0.0/24. But that's not part of the question.