No internet connection

shaunlipy · June 3, 2019, 10:21pm

I just installed the ubuntu image. But when I connect the ethernet cable, there is no internet connection. Tried different cables and ports. I have also added the following lines to /etc/network/interfaces

auto eth0
iface eth0 inet dhcp

then type: sudo ifup eth0

but still no internet connection.

I have also tested the Edimax 7611ulb wifi+bluetooth adapter, still no luck
Can anyone help?

alanz · June 4, 2019, 3:42am

Hi,

Pls refer to another topic. Try the attached driver first.

https://devtalk.nvidia.com/default/topic/1049303/jetson-nano/jetson-nano-wifi-/1

shaunlipy · June 4, 2019, 4:02am

The thing is my Jetson Nano cannot access to the internet at all. I won’t be able to use: sudo apt update or sudo apt install …

I notice the ethernet port is blinking orange.

And the output of ifconfig eth0 shows:

jetson@jetson-desktop:~$ ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.55.223 netmask 255.255.255.0 broadcast 192.168.55.255
inet6 fe80::c309:fb62:2989:4d41 prefixlen 64 scopeid 0x20
ether 00:e0:4c:68:01:95 txqueuelen 1000 (Ethernet)
RX packets 203 bytes 18662 (18.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 44 bytes 7655 (7.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 148 base 0xe000

alanz · June 5, 2019, 1:51am

Hi， shaunlipy

Could you attach the kernel log after boot up the system?
Which version are your SD-Image?

The latest version is jetson-nano-sd-r32.1-2019-03-18.zip from the followed link.
[url]https://developer.nvidia.com/embedded/jetpack[/url]

alanz · June 5, 2019, 2:04am

From your log I don’t see something abnormal. This the log I captured from my Nano board.
The eth0 node is automatic create after boot up. Also you can check from your router to see if there is a real connection there.

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.172  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::e07:2a7a:ce82:cba  prefixlen 64  scopeid 0x20<link>
        ether 00:04:4b:e3:f8:61  txqueuelen 1000  (Ethernet)
        RX packets 359  bytes 225622 (225.6 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 384  bytes 44844 (44.8 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 148  base 0xe000

shaunlipy · June 13, 2019, 12:37pm

Finally found out the bridge connection is messing up the internet connection. I have to disable and delete it .

alanz · June 14, 2019, 12:46am

Good news.

cxed · August 5, 2019, 11:46am

I had a very similar problem which I post about here.

github.com/NVIDIA-AI-IOT/jetcard

Can't route network traffic to external network on eth0

opened 08:57PM - 02 Aug 19 UTC

closed 04:55PM - 07 Aug 19 UTC

cxeba

Hi, I burned the image to an SD card, powered up, typed the password, Ctl-Alt-…t for a terminal, ping 192.168.1.1 and I can see my router responding. Cool. I can even log in to the nano from other machines in the LAN. Looks good. But from the nano, when I try to ping any outside number, e.g. 8.8.8.8, I get nothing. Obviously this will be a problem for updating packages, etc. I know the network/router is fine (using it now). I feel like there is something amiss with the nano's eth0 network port network setup. I tried doing everything I could think of to the routing tables and firewall. I do not have Docker expertise, but I can see that's not exactly simplifying things. Any hints about why the eth0 would be broken? I have the same problem with the default SD card image too. Here's what the routes look like. I tried getting rid of all the l4tbr0 ones but that doesn't seem to help. `` Kernel IP routing table`` ``Destination Gateway Genmask Flags Metric Ref Use Iface`` ``0.0.0.0 192.168.1.1 0.0.0.0 UG 20100 0 0 eth0`` ``0.0.0.0 192.168.55.100 0.0.0.0 UG 32766 0 0 l4tbr0`` ``169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 l4tbr0`` ``192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 eth0`` ``192.168.55.0 0.0.0.0 255.255.255.0 U 0 0 0 l4tbr0`` I also tried plugging in a USB-wifi adapter and that worked fine (with the same router I'm trying to configure a wired connection to). Thanks

In my case the Nano’s eth0 is up and fully accessible within my LAN (I can SSH to it) but the Nano can not ping outside addresses beyond the router (while all other hosts can).

Like the OP, I also tried to cut down the cruft in the routing table but I was never able to successfully get that to work. Can anyone provide an explicit procedure which will cleanly remove any conflicting routes? Or some other way allow the Nano to work properly with its networking port?

Thanks

linuxdev · August 5, 2019, 3:02pm

What is the output of “ifconfig” and “route”? FYI, if you have more than one default route, then a “sudo route remove default” removes the route with the highest priority first (the lowest metric). If you save a copy of the route and accidentally remove too much, then you can add a default with the one you want. There are various tools for adjusting those in a GUI as well (e.g., if going through NetworkManager, then “sudo nm-connection-editor”).

If your router is not set to respond to DNS queries, then it might be a case of needing to tell the router what your MAC address is (a router will usually default to allowing any device, but security settings can be told to allow only known MAC addresses).

cxed · August 5, 2019, 8:25pm

Thank you for the good suggestions linuxdev. I was sure this had to be a configuration problem because we have a normal Verizon Fios router with about a dozen hosts all working just fine. But when I went to provide a look at the route and ifconfig, I first did a quick ping to confirm it didn’t work – but it did work! I changed nothing. Did nothing. Now attention has shifted to the router. I logged into that and there is a setting under “My Network” that shows hosts and on the host in question I saw there was an option for “unblock host”! Obviously I had not previously logged into the router to (partially) block this host. That’s just incredibly weird. So a heads up to Verizon Fios users that the Verizon router may not like Jetson Nanos (sometimes). Hope nobody else has this problem but if they do, I hope this helps.