Planet____9 Posted August 11, 2021 Share Posted August 11, 2021 recently switched to Unifi and since then my server has no internet access. The server functions perfectly for local access. I've tried to set the dns servers as 1.1.1.1 8.8.8.8 or use the built in ethernet vs the 2.5gig. I'm wondering if Unifi doesn't work perfectly with Unraid and how to tell that that's the case when all other devices work properly. Here is the diagnostics atkinson-diagnostics-20210811-1153.zip Quote Link to comment
Planet____9 Posted August 12, 2021 Author Share Posted August 12, 2021 I'm gonna try and bump this at midnight like an idiot because I'm tired of just living with this problem. I tried following this (https://www.redhat.com/sysadmin/beginners-guide-network-troubleshooting-linux) guide I found but honestly I have no reference on what I'm looking at. Here is my command terminal at the end. Linux 4.19.107-Unraid. Last login: Wed Aug 11 23:00:02 -0700 2021 on /dev/pts/0. root@Atkinson:~# ip link show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/gre 0.0.0.0 brd 0.0.0.0 4: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 5: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 6: ip_vti0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 7: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 10: eth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:8e:25:70:01:72 brd ff:ff:ff:ff:ff:ff 11: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 34:97:f6:85:aa:23 brd ff:ff:ff:ff:ff:ff 12: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:8e:25:70:01:72 brd ff:ff:ff:ff:ff:ff 13: wg1: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/none 14: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/none 15: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default link/ether 02:42:b5:f9:08:b6 brd ff:ff:ff:ff:ff:ff root@Atkinson:~# ip -s link show br0 12: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:8e:25:70:01:72 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 16550479 96181 0 4 0 0 TX: bytes packets errors dropped carrier collsns 15767237 46282 0 0 0 0 root@Atkinson:~# ip neighbor show 192.168.1.48 dev br0 lladdr 00:04:4b:fb:39:d5 REACHABLE 192.168.1.237 dev br0 lladdr 38:8b:59:04:21:dc STALE 192.168.1.21 dev br0 lladdr 70:85:c2:97:6b:47 REACHABLE 192.168.1.112 dev br0 lladdr 98:84:e3:cc:52:f0 DELAY 192.168.1.20 dev br0 lladdr 70:48:f7:d8:62:46 STALE 192.168.1.38 dev br0 lladdr 00:04:4b:fd:41:ba STALE 192.168.1.16 dev br0 lladdr e0:4f:43:13:75:ab STALE 192.168.1.59 dev br0 lladdr 7c:2e:bd:2e:f1:b4 STALE 192.168.1.201 dev br0 lladdr 1c:69:7a:17:97:60 STALE 192.168.1.113 dev br0 lladdr 26:d7:98:2a:2d:cc STALE 192.168.1.134 dev br0 lladdr c8:d9:d2:e6:72:c5 STALE 192.168.1.1 dev br0 lladdr 26:5a:4c:5e:1e:59 REACHABLE 192.168.1.209 dev br0 lladdr 46:c9:a2:82:f3:27 STALE 192.168.1.140 dev br0 lladdr 1c:30:08:21:3c:ad DELAY 192.168.1.15 dev br0 lladdr 66:3d:36:9f:21:b0 STALE root@Atkinson:~# ip neighbor delete 192.168.1.1 dev br0 root@Atkinson:~# ip neighbor show 192.168.1.48 dev br0 lladdr 00:04:4b:fb:39:d5 REACHABLE 192.168.1.237 dev br0 lladdr 38:8b:59:04:21:dc STALE 192.168.1.21 dev br0 lladdr 70:85:c2:97:6b:47 REACHABLE 192.168.1.112 dev br0 lladdr 98:84:e3:cc:52:f0 REACHABLE 192.168.1.20 dev br0 lladdr 70:48:f7:d8:62:46 STALE 192.168.1.38 dev br0 lladdr 00:04:4b:fd:41:ba STALE 192.168.1.16 dev br0 lladdr e0:4f:43:13:75:ab STALE 192.168.1.59 dev br0 lladdr 7c:2e:bd:2e:f1:b4 STALE 192.168.1.201 dev br0 lladdr 1c:69:7a:17:97:60 STALE 192.168.1.113 dev br0 lladdr 26:d7:98:2a:2d:cc STALE 192.168.1.134 dev br0 lladdr c8:d9:d2:e6:72:c5 STALE 192.168.1.1 dev br0 lladdr 26:5a:4c:5e:1e:59 REACHABLE 192.168.1.209 dev br0 lladdr 46:c9:a2:82:f3:27 STALE 192.168.1.140 dev br0 lladdr 1c:30:08:21:3c:ad STALE 192.168.1.15 dev br0 lladdr 66:3d:36:9f:21:b0 STALE root@Atkinson:~# ip -br address show lo UNKNOWN 127.0.0.1/8 ::1/128 tunl0@NONE DOWN gre0@NONE DOWN gretap0@NONE DOWN erspan0@NONE DOWN ip_vti0@NONE DOWN sit0@NONE DOWN eth0 UP eth1 DOWN br0 UP 192.168.1.17/24 wg1 UNKNOWN 10.253.1.1/32 wg0 UNKNOWN 192.168.1.1/32 docker0 DOWN 172.17.0.1/16 root@Atkinson:~# ping www.google.com ping: www.google.com: Name or service not known root@Atkinson:~# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.011 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.011 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.010 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.009 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.010 ms 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.008 ms ^C --- 192.168.1.1 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5115ms rtt min/avg/max/mdev = 0.008/0.009/0.011/0.001 ms root@Atkinson:~# traceroute 192.168.1.1 traceroute to 192.168.1.1 (192.168.1.1), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 0.014 ms 0.005 ms 0.004 ms root@Atkinson:~# traceroute www.google.com www.google.com: Name or service not known Cannot handle "host" cmdline arg `www.google.com' on position 1 (argc 1) root@Atkinson:~# ip route show default via 192.168.1.1 dev br0 proto dhcp src 192.168.1.17 metric 212 10.253.1.2 dev wg1 scope link 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev br0 proto dhcp scope link src 192.168.1.17 metric 212 192.168.1.20 dev wg0 scope link root@Atkinson:~# nslookup www.google.com -bash: nslookup: command not found root@Atkinson:~# ss -tunlp4 Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process udp UNCONN 0 0 127.0.0.1:743 0.0.0.0:* users:(("rpc.statd",pid=1838,fd=7)) udp UNCONN 0 0 192.168.1.17:58356 0.0.0.0:* users:(("Plex Media Serv",pid=3897,fd=91)) udp UNCONN 0 0 0.0.0.0:50279 0.0.0.0:* users:(("rpcbind",pid=1833,fd=7)) udp UNCONN 0 0 127.0.0.1:34138 0.0.0.0:* users:(("Plex Media Serv",pid=3897,fd=90)) udp UNCONN 0 0 0.0.0.0:1900 0.0.0.0:* users:(("Plex DLNA Serve",pid=4014,fd=10)) udp UNCONN 0 0 0.0.0.0:1901 0.0.0.0:* users:(("Plex Media Serv",pid=3897,fd=94)) udp UNCONN 0 0 0.0.0.0:1956 0.0.0.0:* users:(("Plex DLNA Serve",pid=4014,fd=19)) udp UNCONN 0 0 0.0.0.0:51820 0.0.0.0:* udp UNCONN 0 0 0.0.0.0:51821 0.0.0.0:* udp UNCONN 0 0 127.0.0.1:35968 0.0.0.0:* users:(("Plex Media Serv",pid=3897,fd=92)) udp UNCONN 0 0 0.0.0.0:60674 0.0.0.0:* users:(("Plex DLNA Serve",pid=4014,fd=25)) udp UNCONN 0 0 0.0.0.0:44407 0.0.0.0:* users:(("rpc.statd",pid=1838,fd=8)) udp UNCONN 0 0 0.0.0.0:3667 0.0.0.0:* users:(("Plex DLNA Serve",pid=4014,fd=16)) udp UNCONN 0 0 192.168.1.17:54119 0.0.0.0:* users:(("Plex Media Serv",pid=3897,fd=93)) udp UNCONN 0 0 192.168.1.17:46072 0.0.0.0:* users:(("Plex Media Serv",pid=3897,fd=95)) udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:* users:(("avahi-daemon",pid=2467,fd=14)) udp UNCONN 0 0 0.0.0.0:55827 0.0.0.0:* users:(("avahi-daemon",pid=2467,fd=16)) udp UNCONN 0 0 0.0.0.0:56572 0.0.0.0:* users:(("Plex DLNA Serve",pid=4014,fd=28)) udp UNCONN 0 0 0.0.0.0:32410 0.0.0.0:* users:(("Plex Media Serv",pid=3897,fd=87)) udp UNCONN 0 0 0.0.0.0:32412 0.0.0.0:* users:(("Plex Media Serv",pid=3897,fd=88)) udp UNCONN 0 0 0.0.0.0:32413 0.0.0.0:* users:(("Plex Media Serv",pid=3897,fd=89)) udp UNCONN 0 0 0.0.0.0:32414 0.0.0.0:* users:(("Plex Media Serv",pid=3897,fd=86)) udp UNCONN 0 0 192.168.1.17:68 0.0.0.0:* users:(("dhcpcd",pid=1735,fd=9)) udp UNCONN 0 0 0.0.0.0:111 0.0.0.0:* users:(("rpcbind",pid=1833,fd=6)) udp UNCONN 0 0 192.168.1.17:123 0.0.0.0:* users:(("ntpd",pid=1868,fd=17)) udp UNCONN 0 0 127.0.0.1:123 0.0.0.0:* users:(("ntpd",pid=1868,fd=16)) udp UNCONN 0 0 172.17.255.255:137 0.0.0.0:* users:(("nmbd",pid=2670,fd=25)) udp UNCONN 0 0 172.17.0.1:137 0.0.0.0:* users:(("nmbd",pid=2670,fd=24)) udp UNCONN 0 0 192.168.1.255:137 0.0.0.0:* users:(("nmbd",pid=2670,fd=20)) udp UNCONN 0 0 192.168.1.17:137 0.0.0.0:* users:(("nmbd",pid=2670,fd=19)) udp UNCONN 0 0 0.0.0.0:137 0.0.0.0:* users:(("nmbd",pid=2670,fd=17)) udp UNCONN 0 0 172.17.255.255:138 0.0.0.0:* users:(("nmbd",pid=2670,fd=27)) udp UNCONN 0 0 172.17.0.1:138 0.0.0.0:* users:(("nmbd",pid=2670,fd=26)) udp UNCONN 0 0 192.168.1.255:138 0.0.0.0:* users:(("nmbd",pid=2670,fd=22)) udp UNCONN 0 0 192.168.1.17:138 0.0.0.0:* users:(("nmbd",pid=2670,fd=21)) udp UNCONN 0 0 0.0.0.0:138 0.0.0.0:* users:(("nmbd",pid=2670,fd=18)) tcp LISTEN 0 50 0.0.0.0:139 0.0.0.0:* users:(("smbd",pid=2665,fd=33)) tcp LISTEN 0 128 0.0.0.0:111 0.0.0.0:* users:(("rpcbind",pid=1833,fd=8)) tcp LISTEN 0 128 0.0.0.0:80 0.0.0.0:* users:(("nginx",pid=3278,fd=9),("nginx",pid=3277,fd=9)) tcp LISTEN 0 128 127.0.0.1:32401 0.0.0.0:* users:(("Plex Media Serv",pid=3897,fd=57)) tcp LISTEN 0 100 0.0.0.0:32469 0.0.0.0:* users:(("Plex DLNA Serve",pid=4014,fd=22)) tcp LISTEN 0 128 0.0.0.0:21 0.0.0.0:* users:(("inetd",pid=2396,fd=5)) tcp LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=2388,fd=3)) tcp LISTEN 0 50 0.0.0.0:1815 0.0.0.0:* users:(("Plex DLNA Serve",pid=4014,fd=13)) tcp LISTEN 0 128 0.0.0.0:23 0.0.0.0:* users:(("inetd",pid=2396,fd=6)) tcp LISTEN 0 128 0.0.0.0:45303 0.0.0.0:* users:(("rpc.statd",pid=1838,fd=9)) tcp LISTEN 0 128 127.0.0.1:32600 0.0.0.0:* users:(("Plex Tuner Serv",pid=4017,fd=10)) tcp LISTEN 0 50 0.0.0.0:445 0.0.0.0:* users:(("smbd",pid=2665,fd=32)) tcp LISTEN 0 128 127.0.0.1:44767 0.0.0.0:* users:(("Plex Script Hos",pid=3933,fd=8)) root@Atkinson:~# Quote Link to comment
itimpi Posted August 12, 2021 Share Posted August 12, 2021 Have you tried using the 'ifconfig' command to check that you have a gateway assigned on the 192.168.1.x subnet (it probably should be the address of the unify router)? Without that you will not be able to access anything outside that subnet. Quote Link to comment
Planet____9 Posted August 12, 2021 Author Share Posted August 12, 2021 What am I looking for here? Linux 4.19.107-Unraid. Last login: Wed Aug 11 23:40:03 -0700 2021 on /dev/pts/0. root@Atkinson:~# ifconfig br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.17 netmask 255.255.255.0 broadcast 192.168.1.255 ether 00:8e:25:70:01:72 txqueuelen 1000 (Ethernet) RX packets 199312 bytes 31603970 (30.1 MiB) RX errors 0 dropped 11 overruns 0 frame 0 TX packets 95281 bytes 325782537 (310.6 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 ether 02:42:b5:f9:08:b6 txqueuelen 0 (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 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether 00:8e:25:70:01:72 txqueuelen 1000 (Ethernet) RX packets 203385 bytes 35426927 (33.7 MiB) RX errors 0 dropped 369 overruns 0 frame 0 TX packets 124977 bytes 325782057 (310.6 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 129 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 1000 (Local Loopback) RX packets 54693 bytes 8380941 (7.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 54693 bytes 8380941 (7.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wg0: flags=209<UP,POINTOPOINT,RUNNING,NOARP> mtu 1420 inet 192.168.1.1 netmask 255.255.255.255 destination 192.168.1.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) 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 16 dropped 0 overruns 0 carrier 0 collisions 0 wg1: flags=209<UP,POINTOPOINT,RUNNING,NOARP> mtu 1420 inet 10.253.1.1 netmask 255.255.255.255 destination 10.253.1.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) 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 5 dropped 0 overruns 0 carrier 0 collisions 0 Quote Link to comment
Turnspit Posted August 12, 2021 Share Posted August 12, 2021 This could maybe be a faulty config of the DNS or Gateway address on your UnRAID machine. From terminal on UnRAID: cat /etc/resolv.conf (show currently used DNS servers) route -n (show Gatway address) If you have set a static IP address inside UnRAID, you could also try switching to automatic assignment and see if it works. Quote Link to comment
Planet____9 Posted August 12, 2021 Author Share Posted August 12, 2021 i know it isn't a static ip problem because i already had tried that. plus all of this was done via my windows machine remotely on the same lan . but I also got this fun oddity 2021-08-12 01-43-00.mp4 Quote Link to comment
Planet____9 Posted August 13, 2021 Author Share Posted August 13, 2021 15 hours ago, Turnspit said: cat /etc/resolv.conf (show currently used DNS servers) route -n (show Gatway address) had some time, rebooted the server to fix the stuttering terminal and here Linux 4.19.107-Unraid. Last login: Thu Aug 12 11:20:23 -0700 2021 on /dev/pts/0. root@Atkinson:~# cat /etc/resolv.conf # Generated by dhcpcd from br0.dhcp # /etc/resolv.conf.head can replace this line domain localdomain nameserver 192.168.1.1 # /etc/resolv.conf.tail can replace this line root@Atkinson:~# route -n 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 212 0 0 br0 10.253.1.2 0.0.0.0 255.255.255.255 UH 0 0 0 wg1 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 192.168.1.0 0.0.0.0 255.255.255.0 U 212 0 0 br0 192.168.1.20 0.0.0.0 255.255.255.255 UH 0 0 0 wg0 root@Atkinson:~# Quote Link to comment
Vr2Io Posted August 13, 2021 Share Posted August 13, 2021 (edited) You use wg0 for routing to internet, I believe it relate wireguard, did you try disable wireguard then trouble shoot. Edited August 13, 2021 by Vr2Io Quote Link to comment
Planet____9 Posted August 13, 2021 Author Share Posted August 13, 2021 I've disabled it... i think. If you would rather have me uninstall it and reinstall wire guard once I fix the problem that's an option Quote Link to comment
Vr2Io Posted August 13, 2021 Share Posted August 13, 2021 I haven't use Wireguard, but I would suggest you uninstall it for troubleshoot first. If cause confirm on Wireguard then ask in Wireguard thrrad to get help. Quote Link to comment
Planet____9 Posted August 13, 2021 Author Share Posted August 13, 2021 I'm not taking this as a victory, it might ,will break... as this was originally an intermittent issue during the weeks leading up to the OP will continue to update. if there is any diagnostic command I should run while it seemingly works TELL ME. Quote Link to comment
Frank1940 Posted August 13, 2021 Share Posted August 13, 2021 First thing, Ubiquiti routers usually shut off DNS redirection. Start by going to Settings >>> Management Access Go down to the "Use SSL/TLS:" setting. Now turn on the help by clicking on 'Help'--- The (?) icon on the toolbar. Read that Help section for this setting. I also wrote up a section on a way to do this on the Edge Router family--- a link to that is below: https://forums.unraid.net/topic/61265-what-router-are-you-running/page/3/?tab=comments#comment-637221 I am not sure how to do that with UniFi family. (I have become very disillusioned with Ubiquiti in the past year of so...) You might try googling it or ask in the UniFi forums... Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.