Hi folks, so I have this setup where all my devices use the regular IP (the one .local uses) to access Unraid but my main machine is linked to Unraid both ways:

 

With the regular IP and another IP address that I use for faster access by plugging the 2nd Ethernet port of the Unraid machine directly to the 2nd Ethernet port of my main machine.

 

That allows me to avoid a lot of overhead and get much better speeds on read and writes at least 3x from everything I tested so I would like things to remain that way.

 

That being said once or twice a week, I may lose connection and I have to reset the adapter in the network settings for it to work again. I would like to solve that as this does not happen on the other default IP of eth0 I am still able to access that when the connection drops.

 

here are my network settings (eth1 being the direct link between the 2 machines):

 

 

here is the log output for the day:

 

```
May 12 03:24:39 Taichi upsd[4708]: User [email protected] logged out from UPS [ups]
May 12 03:24:41 Taichi kernel: r8169 0000:06:00.0 eth1: Link is Down
May 12 03:24:41 Taichi kernel: br1: port 1(eth1) entered disabled state
May 12 03:24:42 Taichi kernel: r8169 0000:06:00.0 eth1: Link is Up - 10Mbps/Full - flow control off
May 12 03:24:42 Taichi kernel: br1: port 1(eth1) entered blocking state
May 12 03:24:42 Taichi kernel: br1: port 1(eth1) entered forwarding state
May 12 03:25:42 Taichi kernel: r8169 0000:06:00.0 eth1: Link is Down
May 12 03:25:42 Taichi kernel: br1: port 1(eth1) entered disabled state
May 12 03:25:45 Taichi kernel: r8169 0000:06:00.0 eth1: Link is Up - 2.5Gbps/Full - flow control rx/tx
May 12 03:25:45 Taichi kernel: br1: port 1(eth1) entered blocking state
May 12 03:25:45 Taichi kernel: br1: port 1(eth1) entered forwarding state
May 12 03:25:46 Taichi kernel: r8169 0000:06:00.0 eth1: Link is Down
May 12 03:25:46 Taichi kernel: br1: port 1(eth1) entered disabled state
May 12 03:25:49 Taichi kernel: r8169 0000:06:00.0 eth1: Link is Up - 2.5Gbps/Full - flow control rx/tx
May 12 03:25:49 Taichi kernel: br1: port 1(eth1) entered blocking state
May 12 03:25:49 Taichi kernel: br1: port 1(eth1) entered forwarding state
May 12 03:25:51 Taichi upsd[4708]: User [email protected] logged into UPS [ups]
May 12 06:26:10 Taichi upsd[4708]: User [email protected] logged out from UPS [ups]
May 12 06:26:11 Taichi kernel: r8169 0000:06:00.0 eth1: Link is Down
May 12 06:26:11 Taichi kernel: br1: port 1(eth1) entered disabled state
May 12 06:26:12 Taichi kernel: r8169 0000:06:00.0 eth1: Link is Up - 10Mbps/Full - flow control off
May 12 06:26:12 Taichi kernel: br1: port 1(eth1) entered blocking state
May 12 06:26:12 Taichi kernel: br1: port 1(eth1) entered forwarding state
May 12 06:27:12 Taichi kernel: r8169 0000:06:00.0 eth1: Link is Down
May 12 06:27:12 Taichi kernel: br1: port 1(eth1) entered disabled state
May 12 06:27:16 Taichi ntpd[2343]: Deleting 5 br1, [169.254.179.14]:123, stats: received=0, sent=0, dropped=0, active_time=827661 secs
May 12 06:27:19 Taichi kernel: r8169 0000:06:00.0 eth1: Link is Up - 2.5Gbps/Full - flow control rx/tx
May 12 06:27:19 Taichi kernel: br1: port 1(eth1) entered blocking state
May 12 06:27:19 Taichi kernel: br1: port 1(eth1) entered forwarding state
May 12 06:27:21 Taichi upsd[4708]: User [email protected] logged into UPS [ups]
May 12 06:27:22 Taichi ntpd[2343]: Listen normally on 6 br1 169.254.179.14:123
May 12 06:27:22 Taichi ntpd[2343]: new interface(s) found: waking up resolver
May 12 09:27:41 Taichi upsd[4708]: User [email protected] logged out from UPS [ups]
May 12 09:27:42 Taichi kernel: r8169 0000:06:00.0 eth1: Link is Down
May 12 09:27:42 Taichi kernel: br1: port 1(eth1) entered disabled state
May 12 09:27:43 Taichi kernel: r8169 0000:06:00.0 eth1: Link is Up - 10Mbps/Full - flow control off
May 12 09:27:43 Taichi kernel: br1: port 1(eth1) entered blocking state
May 12 09:27:43 Taichi kernel: br1: port 1(eth1) entered forwarding state
May 12 09:28:43 Taichi kernel: r8169 0000:06:00.0 eth1: Link is Down
May 12 09:28:43 Taichi kernel: br1: port 1(eth1) entered disabled state
May 12 09:28:47 Taichi ntpd[2343]: Deleting 6 br1, [169.254.179.14]:123, stats: received=0, sent=0, dropped=0, active_time=10885 secs
May 12 09:28:50 Taichi kernel: r8169 0000:06:00.0 eth1: Link is Up - 2.5Gbps/Full - flow control rx/tx
May 12 09:28:50 Taichi kernel: br1: port 1(eth1) entered blocking state
May 12 09:28:50 Taichi kernel: br1: port 1(eth1) entered forwarding state
May 12 09:28:53 Taichi upsd[4708]: User [email protected] logged into UPS [ups]
May 12 09:28:53 Taichi ntpd[2343]: Listen normally on 7 br1 169.254.179.14:123
May 12 09:28:53 Taichi ntpd[2343]: new interface(s) found: waking up resolver
May 12 14:41:57 Taichi webgui: Successful login user root from 169.254.31.117
May 12 14:43:11 Taichi kernel: r8169 0000:06:00.0 eth1: Link is Down
May 12 14:43:11 Taichi kernel: br1: port 1(eth1) entered disabled state
May 12 14:43:15 Taichi ntpd[2343]: Deleting 7 br1, [169.254.179.14]:123, stats: received=0, sent=0, dropped=0, active_time=18862 secs
May 12 14:43:15 Taichi kernel: r8169 0000:06:00.0 eth1: Link is Up - 2.5Gbps/Full - flow control rx/tx
May 12 14:43:15 Taichi kernel: br1: port 1(eth1) entered blocking state
May 12 14:43:15 Taichi kernel: br1: port 1(eth1) entered forwarding state
May 12 14:43:18 Taichi ntpd[2343]: Listen normally on 8 br1 169.254.179.14:123
May 12 14:43:18 Taichi ntpd[2343]: new interface(s) found: waking up resolver

```

 

Let me know if you have any clue thanks again... This happens to me generally when I try to access files big or small docs or videos.

 

 

Edited May 12, 20251 yr by MonadProxy

this souds like cacehed cleint isseus using one ip over the other...

what is your smb settigns?

 

you may need to look more into the setting behind SMB mutichannel...

I would advise this to be off. in your case.

as essetial goin to teh device name in widnwos its host ip thinks its one ip address over the other untill you move adn teh ip of the host changes.
-this casues the disconect and confusion...

go to the unraid machine via its ip as test adn to fix this to watch when moving it no longer at xyz ip address.

also review smb muti channel as windows has changed smb settings and thing break at the client side not server side...

 

https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/manage-smb-multichannel

Thanks for the tips, I will try to enable it when I can turn off the array and let you know the results.

 

You also made me notice that all my exclusive shares reverted to non-exclusive but that's another story for another day...

Ok I just updated to 7.1.2 and took time to set up multichannel, let's see how that goes.