Web server on Jetson Nano

I have been trying to have an owncloud server on my jetson nano. The installation and setup for the server is done and it works. But for some reason the server is not accessible on my LAN.

When I use the browser on my jetson, it allows me to go to the site http://<ip-address> but any other device on the same network is not able to connect to it. This makes me think that it is a firewall issue. I still have been unable to find a solution to this, would love to have some ideas.

I am unable to use ufw due to some issues present in the jetson os. I have already unsuccessfully tried to add a rule using iptables:

iptables -A INPUT -p tcp -s 0/0 --sport 1024:65535 --dport 80 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -A OUTPUT -p tcp --sport 80 -d 0/0 --dport 1024:65535 -m state --state ESTABLISHED -j ACCEPT

But it is all to no avail. I am sure I am missing something small but cannot put a finger on it yet. Do let me know how to debug and/or to solve it this problem.

Additional Detials:
Jetson Nano 2GB with Jetpack 4.6.2

I don’t think there is any firewall rule by default, but possibly there is. The problem now is that if you’ve done something with firewall rules, then perhaps it isn’t the default, but may have saved anyway. The reason I wonder about this is that firewall rules would be tested after regular network setup is tested. FYI, what follows is true for Ubuntu 18.04 without any regard for being a Jetson (the Jetson itself will be unrelated to most of this).

For the Jetson, how is it connected? WiFi or wired? How about the other systems, are they using WiFi or wired? Are they all on the same router?

Next, on the Jetson and on one unit which cannot reach the Jetson (preferably wired since it simplifies some things), give the output of each of these (and make sure we know which unit it is this applies to, Jetson versus “other”):

  • route
  • ifconfig
  • If WiFi is involved, also “iwconfig
  • If firewall might be involved, list the means of this, e.g., is it “ufw”? If “ufw”, then what is the output of:
    • sudo ufw status

I don’t know if this will find the issue, but it is a good start and anyone debugging this would want this same information.

One last question: Is this your own router without other users inside of it? I ask because there is good reason for added security like firewalls if in a dorm with lots of untrusted users on the same router. It is good to know if this is just your router, or if it is “out in the wild”.

My Jetson along with other devices are all connected to the same router. Everything is using WiFi. I am not using ufw since any attempt at using it throws an error mentioned at this link.

The output for the commands are:

route:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         reliance.relian 0.0.0.0         UG    20600  0        0 wlan0
link-local      0.0.0.0         255.255.0.0     U     1000   0        0 docker0
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
192.168.29.0    0.0.0.0         255.255.255.0   U     600    0        0 wlan0

ifconfig:

docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        inet6 fe80::42:6cff:feb4:199e  prefixlen 64  scopeid 0x20<link>
        ether 02:42:6c:b4:19:9e  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 78  bytes 12212 (12.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 48:b0:2d:2e:e8:43  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 149  base 0x2000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 618  bytes 57496 (57.4 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 618  bytes 57496 (57.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

rndis0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 42:0e:04:1b:ce:b1  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 42:0e:04:1b:ce:b3  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth5d809ca: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::5899:b8ff:fe8f:37f6  prefixlen 64  scopeid 0x20<link>
        ether 5a:99:b8:8f:37:f6  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 98  bytes 15668 (15.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.29.100  netmask 255.255.255.0  broadcast 192.168.29.255
        inet6 fe80::b38c:7148:abe:50a9  prefixlen 64  scopeid 0x20<link>
        ether 00:e0:4c:50:65:34  txqueuelen 1000  (Ethernet)
        RX packets 8136  bytes 5843235 (5.8 MB)
        RX errors 0  dropped 64  overruns 0  frame 0
        TX packets 6654  bytes 1673367 (1.6 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

iwconfig:

veth5d809ca  no wireless extensions.

wlan0     IEEE 802.11AC  ESSID:"WifiNameHere"  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency:5.22 GHz  Access Point: A8:DA:0C:8D:18:30   
          Bit Rate:434 Mb/s   Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=67/100  Signal level=62/100  Noise level=0/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

l4tbr0    no wireless extensions.

lo        no wireless extensions.

eth0      no wireless extensions.

docker0   no wireless extensions.

rndis0    no wireless extensions.

usb0      no wireless extensions.

dummy0    no wireless extensions.

A starting note which might be important, but might also be irrelevant: The URL about the UFW issue is related to IPv6, which is the newer IP address scheme. I would not be surprised if something is choking on IPv6 since not everything seems to have implemented this “bug free”. At times it is worthwhile to tell interfaces (such as via nm-connection-editor) to use only IPv4. I do not know if this will matter or not, but your “veth5d809ca” interface uses IPv6. Can you say what the “veth5d809ca” device is?

Also, you showed only one instance of those commands. Are they from the Jetson? What do you see on the system at the other end? The two have to work together, thus I’m looking for whether both (simultaneously) are set up to talk to each other.

@veedata To use you have to apply the kernel patch I shared and build it along with the modules.