Hi
Bit of a strange one this. I'm having issues where the terminal window closes itself after ~30-40 seconds, and similarly if I have an SSH shell open to the server, that becomes unresponsive after a similar amount of time.
TL;DR - If I'm connected to a VLAN network on my laptop (wired or wireless) where that VLAN is configured in Unraid, then a browser Unraid terminal window or an SSH shell into Unraid either closes or becomes unresponsive respectively after ~30-40 seconds.
Setup:
Protectlii fanless pc with 6x 1Gb NICS (Intel) = pfSense router
- WAN connected to cable modem
- LAN & OPT1-3 bonded as 802.3AD (LAN & 3x VLANS) = 4 ports
- OPT4 not used
- 'Default' LAN network = 192.168.200
- 3x VLANs - 192.168.10 ; 192.168.33 ; 192.168.172
Unifi switches & APs
- no USG - pfSense above used as '3rd party gateway'
- controller = mini PC with self-hosted unifi controller on Ubuntu Server
Dell R730XD with 4x 1Gb daughter board (Intel X350) = Unraid server
- 4x 1GB network interfaces bonded together into a single 802.3ad LACP grouping (eth0-eth3);
- IP set to automatic in Unraid, from 'Default' (untagged) network on eth0 tab (192.168.200. network). Static DHCP setup in pfSense for this MAC address. DNS also set as automatic in Unraid
- 2x additional VLANS created on this interface (192.168.10. and 192.168.172. networks). IPs are static
Please note that all of this works just fine - connection to the internet, plugins show updates where required, dockers show updates where required, access to CA is available too. etc, etc. firewall rules all work as expected. yada yada yada. Note that whilst testing different theories, all interfaces were temporarily set to allow all traffic to anywhere, so I'm confident it's not firewall rule related.
Here's where the issue lies:
When connecting to Unraid via a browser on my laptop (either wireless or wired) when it's connected to either of the 2 VLAN networks setup within the network settings of the Unraid box. If I'm connected to a different network outside of what is setup within Unraid (eg 192.168.33.) then the terminal window stays open and SSH sessions remain responsive.
I've also tried this on a different laptop getting the same outcome, so it's not the laptop. The first laptop is also running Linux Mint, and the second running Windows
Other things I've tried or noticed:
- Prior to setting up bonds (pfSense -> Switch & Switch -> Unraid), all networks were on their own individual network cable. This worked fine, and I don't remember having these issues, however there's no redundancy etc plus it's a little more involved setting up the switch ports correctly
- Where I've been bonding, the unusual behaviour occurs on all modes I've tried
- I've exchanged cables to no avail, and have used contact cleaner on affected ports
- I have a correctly configured Let's Encrypt certificate on pfSense and Unraid so I can use https/host names, the behaviour happens when using either the hostname or IP address
- Problem is irrespective of IP / DNS settings on the eth0 page, as in 'automatic' or 'static' - particularly as in having a static DNS set up for a public DNS provider such as 1.1.1.1 or 8.8.8.8 etc. The problem occurs either way, and in any case having DNS set to automatic to pick up the 1.1.1.1 etc through pfSense has no effect in Unraid not being able to load from the CA Apps tab or update plugins / dockers etc
- 2 different laptops have been used, 1 laptop is Linux Mint, the other Windows
- Wired or wireless, doesn't matter
- Docker service enabled or disabled, doesn't matter
- No VMs used in Unraid (I use a separate unconnected Proxmox server for VMs)
- Different combinations of SMB settings used to no avail
- I've also noticed that Unraid in general goes unresponsive every ~30-40 seconds as well - such as having to F5 to refresh the page quite a lot
After much trial and error, I think it's either DHCP or DNS related, but I'm no expert
Any help would be appreciated, it's driving me nuts
Also, I like tinkering and learning stuff by "having a go" and this type of "server" gear is readily available and pretty cheap on eBay. Whilst probably overkill for my setup, I don't think it's necessarily over-complicated in principal either, so don't really want to prune anything back unless absolutely necessary
Thanks
Dave