The Nano have 2 NICs wlan0 set to sharing WiFi Hotspot for M1 with static IP 10.42.1.100 gateway 10.42.1.1 and eth0 set to sharing Ethernet for the Xavier with static IP 10.42.0.100 gateway 10.42.0.1.
I’ve followed the usb-dev-mode README and configure IPv4 forwarding + NAT for eth0 with its IP as above 10.42.0.1 but I can only ping others from Nano and vice versa but not from/to M1 to/from Xavier. Is there any additional setting needed for their communication?
Both boards using L4T images, versions 4.9.140-tegra/4.9.253-tegra and the PC is on Big Sur 11.4.
It actually just about mentioning the IPv4 forward which one of the question in the forum asked using a USB WiFi Dongle and might be irrelevant info. Also, in my case it would be using the Intel M.2 WiFi Chipset.
Here are the outputs from Nano.
NOTE: I’m currently just trying to create a bridge network br0 for the eth0 interface. Otherwise, nothing is different.
❯ iwconfig
br0 no wireless extensions.
dummy0 no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11 Mode:Master Tx-Power=22 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
lo no wireless extensions.
docker0 no wireless extensions.
❯ sudo route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.42.0.0 0.0.0.0 255.255.255.0 U 425 0 0 br0
10.42.1.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0
link-local 0.0.0.0 255.255.0.0 U 1000 0 0 br0
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
With the current setup IPv4 forwarding and manually adding Xavier’s subnet to M1 route table with route add -net 10.42.0.0/24 10.42.1.1, I can now ping from M1 to Xavier but not the other way around.
I’ve also noticed that if I unplug/plug the Ethernet cable again between Nano and Xavier, then the opposite happen, Xavier can ping M1 but not the other way around.
When I compared the outputs of route, iptables on both Nano and Xavier before and after unplug/plug the Ethernet cable, nothing has changed and the same situation persist after a reboot of every device.
I see no error in the individual interfaces and route. I couldn’t say for sure where the error is, but it is no doubt in the bridging setup. I tend to make such changes via nm-connection-editor (you can “sudo apt-get install network-manager-gnome” if you don’t have this). Barring that, then I’d look at the bridging tutorials on the internet (this isn’t specific to a Jetson, most any Ubuntu tutorial would be valid).
I’ve alternated between nm-connection-editor and nmtui for the network settings. Thanks for the suggestions.
I too think the bridging is the problem, one suspicion is that it might be the default bridging network came with Xavier Image. I tried to follow the official instruction to safely remove it but it still created on the next boot up.
I’ve tried to put both IPv4 Method to “Shared to other computers” and additionally also with optional IP addresses 10.42.0.xxx/10.42.1.xxx on the Nano (so that other computer see Nano with different than the default addresses), but that also didn’t work.
I lack anything useful to add to this, but there will be bridging setup which is not from NVIDIA when WiFi is installed, plus the USB virtual wired ethernet may have some sort of bridging used. No idea what the effect is for removing any of this, but I would be far less surprised to see issues related to the “standard” WiFi bridging getting in the way of what goes on, while I would far more surprised to see the virtual ethernet device bridging as a problem.