• Posts

  • Joined

  • Last visited

Recent Profile Visitors

1280 profile views

tknx's Achievements


Explorer (4/14)




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?
  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 and the IOT VLAN When i go the client list for my Unifi router, I only see the entry for the VLAN. I don't see the 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 to "Peer allowed IPs:" it kills Unraid's connectivity. Right now I have the default lan on and an IOT lan on 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 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?
  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 ( 56(84) bytes of data. 64 bytes from ( icmp_seq=1 ttl=56 time=2.58 ms 64 bytes from ( icmp_seq=2 ttl=56 time=2.90 ms 64 bytes from ( icmp_seq=3 ttl=56 time=2.77 ms 64 bytes from ( icmp_seq=4 ttl=56 time=2.95 ms 64 bytes from ( icmp_seq=5 ttl=56 time=2.65 ms ^C64 bytes from icmp_seq=6 ttl=56 time=2.64 ms --- 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 PING ( 56(84) bytes of data. From ( icmp_seq=1 Destination Host Unreachable ping: sendmsg: Destination address required ^CFrom icmp_seq=2 Destination Host Unreachable ping: sendmsg: Destination address required --- ping statistics --- 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 5001ms root@Mnemosyne:~#
  12. Ok. I renamed network.cfg and by default I still get errors on ping
  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 from the command line, it fails too. root@Mnemosyne:~# ping ^C root@Mnemosyne:~# ping ^C root@Mnemosyne:~# ping PING ( 56(84) bytes of data. ^C --- ping statistics --- 14 packets transmitted, 0 received, 100% packet loss, time 13319ms root@Mnemosyne:~# ping PING ( 56(84) bytes of data. No idea why this is happening!
  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 main network has two shim-br0 to cover the addressable space: Same for the IOT VLAN which has two shim-br0.20 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: docker0 br-fcb95060594f br-6aaca2bea56c