March 22, 20179 yr I have just deployed a second unraid machine and have a strange situation going on that I cannot put my finger on just yet. I can ping/access the interface for unraid just fine up until I start the array & mount the shares. As soon as the array is started & mounted ping stops from the VPN link. Locally on the same network the connection is still fine. I can't figure out why the issue only happens when the array is started on UnRAID. System details: Unraid guest on esxi 6.5 (booting from passthrough usb) configured LAN vswitch Pfsense guest on esxi running as openvpn server for this system using WAN and LAN vswitches local network is 192.168.2.0/24, unraid is .108 OpenVPN is 172.network client end of the open vpn is using 192.168.1.0/24 Let me know if further information/clarification is needed. Been fiddling with this for a couple weeks now trying to get it working perfectly. Thanks, Kuz tower2-diagnostics-20170321-2042.zip
March 27, 20179 yr Hi Kuz, We are going to have to rely on the rest of the community to help diagnose this one. We do not officially support running unRAID as a virtual machine, though we do not explicitly prevent it either (we include the necessary drivers, but we are not VMWare experts, so can't diagnose VMWare-specific issues). To be perfectly clear in our understanding of the issue, unRAID itself remains working through all of this. SMB access is still possible, SSH, and even the webGui, but only when done locally on the 192.x.x.x network. If attempting to access the unRAID web interface through the 172.x.x.x OpenVPN network, this works when the array is stopped, but once started, this method fails. This last point is the crux of your issue. To me, this sounds a lot more like a network configuration issue than a problem with unRAID OS itself, though I could be wrong.
March 30, 20179 yr Author On 3/27/2017 at 1:16 PM, jonp said: Hi Kuz, We are going to have to rely on the rest of the community to help diagnose this one. We do not officially support running unRAID as a virtual machine, though we do not explicitly prevent it either (we include the necessary drivers, but we are not VMWare experts, so can't diagnose VMWare-specific issues). To be perfectly clear in our understanding of the issue, unRAID itself remains working through all of this. SMB access is still possible, SSH, and even the webGui, but only when done locally on the 192.x.x.x network. If attempting to access the unRAID web interface through the 172.x.x.x OpenVPN network, this works when the array is stopped, but once started, this method fails. This last point is the crux of your issue. To me, this sounds a lot more like a network configuration issue than a problem with unRAID OS itself, though I could be wrong. Hi Jon, yes you are right on. Trying to dig through logs an monitor the issue myself. Only when the array is brought online does my remote link to unraid fail. Does unraid natively bind to any 172. ranges internally? I copied some log's from the start/stop process of the array where the issue happens and noticed a few lines with my VPN range in it. Mar 29 21:43:03 Tower2 kernel: veth129e470: renamed from eth0 Mar 29 21:43:03 Tower2 kernel: docker0: port 1(veth62a6551) entered disabled state Mar 29 21:43:04 Tower2 kernel: docker0: port 1(veth62a6551) entered disabled state Mar 29 21:43:04 Tower2 kernel: device veth62a6551 left promiscuous mode Mar 29 21:43:04 Tower2 kernel: docker0: port 1(veth62a6551) entered disabled state Mar 29 21:43:05 Tower2 root: a9e204910132 Mar 29 21:43:06 Tower2 ntpd[3272]: Deleting interface #5 docker0, 172.17.0.1#123, interface stats: received=0, sent=0, dropped=0, active_time=306 secs Mar 29 21:43:10 Tower2 root: f69e1c7fcf41 Mar 29 21:43:18 Tower2 root: 3c8325a61b2d Mar 29 21:43:19 Tower2 root: waiting for docker to die... Mar 29 21:43:20 Tower2 avahi-daemon[14080]: Interface docker0.IPv4 no longer relevant for mDNS. Mar 29 21:43:20 Tower2 avahi-daemon[14080]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Mar 29 21:43:20 Tower2 avahi-daemon[14080]: Withdrawing address record for 172.17.0.1 on docker0. Mar 29 21:43:20 Tower2 emhttp: shcmd (432): umount /var/lib/docker |& logger Mar 29 21:43:21 Tower2 emhttp: shcmd (433): /etc/rc.d/rc.samba stop |& logger Mar 29 21:43:21 Tower2 emhttp: shcmd (434): rm -f /etc/avahi/services/smb.service Mar 29 21:43:21 Tower2 avahi-daemon[14080]: Files changed, reloading. Mar 29 21:43:21 Tower2 avahi-daemon[14080]: Service group file /services/smb.service vanished, removing services. Mar 29 21:43:21 Tower2 emhttp: shcmd (437): /etc/rc.d/rc.avahidaemon stop |& logger Mar 29 21:43:21 Tower2 root: Stopping Avahi mDNS/DNS-SD Daemon: stopped Mar 29 21:43:21 Tower2 avahi-daemon[14080]: Got SIGTERM, quitting. Mar 29 21:43:21 Tower2 avahi-dnsconfd[14089]: read(): EOF Mar 29 21:43:21 Tower2 avahi-daemon[14080]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.2.109. Mar 29 21:43:21 Tower2 avahi-daemon[14080]: avahi-daemon 0.6.32 exiting. unraidlog.txt
March 30, 20179 yr Author That seems to have helped solved the problem. I changed my VPN link to 172.18.x.x instead of the 172.17.0.1 it was on. Seems like something by default in unraid uses the 172.17.0.1 and as luck would have it that was the exact address configured for my VPN.
March 30, 20179 yr 8 hours ago, sirkuz said: Seems like something by default in unraid uses the 172.17.0.1 Docker.
Archived
This topic is now archived and is closed to further replies.