tknx

Members
  • Posts

    227
  • Joined

  • Last visited

Recent Profile Visitors

1280 profile views

tknx's Achievements

Explorer

Explorer (4/14)

9

Reputation

2

Community Answers

  1. I found my server wasn't running and the attached screen showed the above message - seems like a kernel panic? Anything I can do to identify the issue? tower-diagnostics-20221107-1037.zip
  2. No - I have noticed that any questions related to networking issues rarely get answered. People just say delete 'network.cfg' as the only solution.
  3. So I have my server setup to be on the default LAN 10.0.0.0/22 and the IOT VLAN 10.0.20.0/24 When i go the client list for my Unifi router, I only see the 10.0.20.86 entry for the VLAN. I don't see the 10.0.0.101 address it should have for the default LAN. Any idea what is going on here?
  4. So I was told elsewhere to enable Wireguard to access VLANs, I needed to add CIDR ranges to the AllowedIPs field. When I added 0.0.0.0/0 to "Peer allowed IPs:" it kills Unraid's connectivity. Right now I have the default lan on 10.0.0.0/22 and an IOT lan on 10.0.20.0/24 as well as a guest lan and a couple of other specialty ones. So what is the best way to enable VLAN access here?
  5. Solved it sort of - it was Wireguard. I think when I added 0.0.0.0/0 to allowed peers, it created problems. I need to experiment more with it since i want VPN clients to be able to access both my VLANs
  6. @JorgeB So it worked fine until I started adding dockers back. I added Jellyfin and then I could not connect or add any other dockers or ping. So either it is that particular config or it is the docker service itself? tower-diagnostics-20221018-1225.zip
  7. Yeah - I will try and copy over the files as you suggest to my install. This is totally weird, right?
  8. @JorgeB Used a fresh install and can ping (although it seems slow). So definitely feels like an Unraid problem, at least partially. PING cnn.com (151.101.131.5) 56(84) bytes of data. 64 bytes from 151.101.131.5 (151.101.131.5): icmp_seq=1 ttl=56 time=2.58 ms 64 bytes from 151.101.131.5 (151.101.131.5): icmp_seq=2 ttl=56 time=2.90 ms 64 bytes from 151.101.131.5 (151.101.131.5): icmp_seq=3 ttl=56 time=2.77 ms 64 bytes from 151.101.131.5 (151.101.131.5): icmp_seq=4 ttl=56 time=2.95 ms 64 bytes from 151.101.131.5 (151.101.131.5): icmp_seq=5 ttl=56 time=2.65 ms ^C64 bytes from 151.101.131.5: icmp_seq=6 ttl=56 time=2.64 ms --- cnn.com ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 25026ms rtt min/avg/max/mdev = 2.580/2.749/2.954/0.139 ms
  9. @JorgeB tried direct connect same problem. My Caddy reverse proxy works fine to get into the services onto the machine from outside. I cannot ssh into the machine remotely either but can use the webUI based terminal.
  10. Well now when I change network settings the UI entirely crashes, what a mess...
  11. No luck there either.... This is pretty frustrating! root@Mnemosyne:~# ping cnn.com PING cnn.com (151.101.3.5) 56(84) bytes of data. From 10.253.0.1 (10.253.0.1) icmp_seq=1 Destination Host Unreachable ping: sendmsg: Destination address required ^CFrom 10.253.0.1 icmp_seq=2 Destination Host Unreachable ping: sendmsg: Destination address required --- cnn.com ping statistics --- 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 5001ms root@Mnemosyne:~# mnemosyne-diagnostics-20221017-1150.zip
  12. Ok. I renamed network.cfg and by default I still get errors on ping mnemosyne-diagnostics-20221017-1107.zip
  13. Hi @Jorge Yes - it does have internet access through eth0. eth1 doesn't have anywhere to clear a gateway from?
  14. Fix Common Problems is having troubles connecting to github, if I try to ping google.com from the command line, it fails too. root@Mnemosyne:~# ping github.com ^C root@Mnemosyne:~# ping cnn.com ^C root@Mnemosyne:~# ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. ^C --- 1.1.1.1 ping statistics --- 14 packets transmitted, 0 received, 100% packet loss, time 13319ms root@Mnemosyne:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. No idea why this is happening! mnemosyne-diagnostics-20221017-0934.zip
  15. When I enable docker, the various lans get split up with shims to cover the addressable space. So in the attached picture you can see that my 10.0.0.0/22 main network has two shim-br0 to cover the addressable space: 10.0.0.0/23 10.0.2.0/23 Same for the IOT VLAN 10.0.20.0/24 which has two shim-br0.20 10.0.20.0/25 10.0.20.128/125 And then there are two entries at the bottom which I have no idea what they are for, but look like they are splitting apart the docker network: 172.17.0.0/16 docker0 172.31.200.0/24 br-fcb95060594f 172.31.201.0/24 br-6aaca2bea56c