Hi All, 

 

brand spanking new to unraid. come over from Synology so still learning how this all works, so apologies if this has been asked before. 
 

so I have installed a VM on my server (from Mac in a box). However when this is running and I’m doing something like transfers files from my synology to my unraid server it keeps disconnecting. It does this about every 10 minutes and when I say disconnected my router doesn’t even show it being there.  It does eventually come back, but sometimes I have to reboot the server. 
 

I have two network cables going from the unraid to the router, which I have bonded together for Fault Tolerance. The VM ( Mac OS Catalina) uses bridging to achieve an internet connection. 
 

both of the lan ports on my network are gigabit and uses the one built into the motherboard( Intel). 
 

I am not sure where I should start. I have no experience with shell or using any Linux based commands. 
 

Any ideas would be welcomed.
 

 

The best place to start would be to post your diagnostics. In the Web GUI go to Tools -> Diagnostics and attach the resulting zip file to your next post.

51 minutes ago, John_M said:

The best place to start would be to post your diagnostics. In the Web GUI go to Tools -> Diagnostics and attach the resulting zip file to your next post.

Thanks, Here they are. 

 

Also I have noticed today that is not just related to the VM I have had about 15 drops today. I looked at my logs and I am wondering if it is to do something with the IP address leasing, but not 100% sure. 

thanos-server-diagnostics-20191103-1523.zip

On 11/2/2019 at 8:15 PM, mcoliver88 said:

I have two network cables going from the unraid to the router, which I have bonded together for Fault Tolerance.

Not according to your diagnostics. Bonding is not enabled and only eth0 has a working cable plugged in. It has a static IP address of 192.168.1.3/25.

            [BONDING] => no
            ...
            [BRIDGING] => yes
            [BRNAME] => br0
            [BRNICS] => eth0
            ...
            [PROTOCOL:0] => ipv4
            [USE_DHCP:0] => no
            [IPADDR:0] => 192.168.1.3
            [NETMASK:0] => 255.255.255.128
            [GATEWAY:0] => 192.168.1.1

Settings for eth0:
	...
	Link detected: yes

Settings for eth1:
	...
	Link detected: no

From your description this doesn't seem to be how you expect it to be configured.

 

From your syslog there's clearly a discrepancy with the netmask (/24 vs /25):

Nov  3 12:54:19 Thanos-Server rc.inet1: ip -4 addr add 192.168.1.3/255.255.255.0 dev br0

Nov  3 13:00:41 Thanos-Server rc.inet1: ip -4 addr add 192.168.1.3/255.255.255.128 dev br0

So take a close look at your Network configuration (Settings -> Network Settings) and check your router's configuration too, to resolve the discrepancy. Personally, I'd let the DHCP server take charge of allocating IP addresses, reserving fixed addresses for given MAC addresses, as required.

 

On 11/4/2019 at 3:38 PM, John_M said:

Not according to your diagnostics. Bonding is not enabled and only eth0 has a working cable plugged in. It has a static IP address of 192.168.1.3/25.

            [BONDING] => no
            ...
            [BRIDGING] => yes
            [BRNAME] => br0
            [BRNICS] => eth0
            ...
            [PROTOCOL:0] => ipv4
            [USE_DHCP:0] => no
            [IPADDR:0] => 192.168.1.3
            [NETMASK:0] => 255.255.255.128
            [GATEWAY:0] => 192.168.1.1

Settings for eth0:
	...
	Link detected: yes

Settings for eth1:
	...
	Link detected: no

From your description this doesn't seem to be how you expect it to be configured.

 

From your syslog there's clearly a discrepancy with the netmask (/24 vs /25):

Nov  3 12:54:19 Thanos-Server rc.inet1: ip -4 addr add 192.168.1.3/255.255.255.0 dev br0

Nov  3 13:00:41 Thanos-Server rc.inet1: ip -4 addr add 192.168.1.3/255.255.255.128 dev br0

So take a close look at your Network configuration (Settings -> Network Settings) and check your router's configuration too, to resolve the discrepancy. Personally, I'd let the DHCP server take charge of allocating IP addresses, reserving fixed addresses for given MAC addresses, as required.

 

Thanks, so when I sent the logs I removed the second LAN cable just to trouble shoot it. However I have now resolved the problem and I am really angry with myself that I didn't see it sooner. The server was set with a static IP address, however that same IP address was also being issued out to my apple tv by the router via DHCP. So I have turned off static addressing on the server and am using DHCP and its working fine, with no disconnection. 

3 hours ago, mcoliver88 said:

Thanks, so when I sent the logs I removed the second LAN cable just to trouble shoot it. However I have now resolved the problem and I am really angry with myself that I didn't see it sooner. The server was set with a static IP address, however that same IP address was also being issued out to my apple tv by the router via DHCP. So I have turned off static addressing on the server and am using DHCP and its working fine, with no disconnection. 

For unraid I would set a static IP outside of the DHCP range of your router. Once you get into port forwarding static IP's are really helpful/required depending on your router.

On 11/5/2019 at 10:40 PM, bu2d said:

For unraid I would set a static IP outside of the DHCP range of your router. Once you get into port forwarding static IP's are really helpful/required depending on your router.

Thanks for the info. 

On 11/5/2019 at 10:40 PM, bu2d said:

For unraid I would set a static IP outside of the DHCP range of your router. Once you get into port forwarding static IP's are really helpful/required depending on your router.

Static IP addresses are difficult to manage and deploy as it's easy to issue duplicates, get default gateways wrong and make typos when entering netmasks. A much better solution is to make use of the property of a DHCP server to allocate a specific IP address in response to a request from a particular MAC address. The result is functionally equivalent to having a manually allocated static IP address with the benefit that the configuration and management are all done in one place, making duplicates much less likely.