Asymmetric links lead to whole network freeze!!

[Montikore]

Hi all,

I just noticed a very strange behavior with zeroshell : my network is mostly on gigabit links, but i have a few links at 100Mb. If i launch a file copy on a computer on the 100Mb link, the files being on the gigabit link side, then the whole network is broken (except for the copy which is working…) and zeroshell doesn’t answer anymore on the web interface…

So i finally understood why sometimes the whole network is broken…. but what the fuck??!!!

[DrmCa]

What is your topology?

[Montikore]

one central zeroshell, 4 subnetworks each on a dedicated gigabit ethernet card

with a 100Mb link, the copy is at 10Mb/s and the whole network is down…
with a Giga link, the copy is at 40Mb/s and everything is smooth

And this is always the same!

[DrmCa]

And what is your ZS hardware, including mobo, CPU, RAM, NICs?

So you have a box with 4 GB NICs running ZS. What are you referring to as ‘100mb/s link’?

[Montikore]

i don’t know about the mobo, but i have the feeling this is a software issue. Anyway here are the details :
proc :Intel Core2 Quad
RAM : 3Gb
NICs : D-Link System Inc DGE-528T

When i speak about 100Mb link, i just mean the computer is behind a 100Mb switch.

For now the only solution (without replacing all switches) i see is to install the x64 kernel (i’m currently running the 32bit version) to have a try when it will be possible…

[DrmCa]

I would look into replacing the Dlink NICs with Intel based NICs first. You can get the Intel NICs off the Ebay very cheap.

[Montikore]

just in case somebody else faces the same issue : after installing the x64 core, the issue is resolved.

So there is a bug in the x32 version… perhaps running the x32 version on a x64 computer is not well supported…

[DrmCa]

Same version 64bit core as 32bit was?
Wow, this is lame then. 32 and 64 should be only different in binary format after compilation as the instruction sets are the same except for memory addressing. Thanks for sharing!

[Author]

Posts