sunbear Posted June 4 Share Posted June 4 This is the default behavior in Windows if you have more than one network device, e.g. a LAN port + WIFI. Each device gets it's own IP on the local network. My server board has FOUR different NICs and I would like to have them in two bonded groups so I can separate my SMB and local access from by docker network and port forwarded IP address. Yet Unraid forces me to ignore this bright red critical error warning that is typically reserved for things like disk errors: What is this about? Is there actually anything wrong with this setup? Is it going to cause me issues as the warning claims? This is my network config: Quote Link to comment
JonathanM Posted June 4 Share Posted June 4 https://support.microsoft.com/en-us/topic/how-multiple-adapters-on-the-same-network-are-expected-to-behave-e21cb201-2ae1-462a-1f47-1f2307a4d47a excerpt Quote However, by definition, only one adapter may communicate on the network at a time in the Ethernet network topology. Quote Link to comment
sunbear Posted June 4 Author Share Posted June 4 (edited) That doesn't change the fact that it's the default behavior, as far as I'm aware. Unless you go into network adapters and manually bridge them yourself. My question still stands, though. What issues does this cause in Unraid as implied by the error message? If I am manually splitting the traffic by having SMB only access one and docker network on the other, what is the issue? Are you implying that one NIC will not broadcast anytime the other NIC is and vice versa, as windows implies? Edited June 4 by sunbear Quote Link to comment
MAM59 Posted June 5 Share Posted June 5 (edited) (BTW: your screeshots are too small to be read for me... 7 hours ago, sunbear said: This is the default behavior in Windows if you have more than one network device, e.g. a LAN port + WIFI. Each device gets it's own IP on the local network. The default behaviour for windows is to turn off one adapter if it recognizes that they go to the same IP net. Usually "the higher lance wins" and WIFI is ignored then. You may force Windows to use both, but then expect the unexpected. For many reasons "two on the same net" have always be a problem. It starts from ARP entries, goes over to MDNS and DDNS registration and much more. To be short: AVOID, AVOID, AVOID!!! Better consider to get a faster NIC and switch... Edited June 5 by MAM59 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.