I didn’t see any ‘interesting message’ on the console when it happen. However I’ve noticed this when it is booting;
08:18:11 physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.and also this:
08:18:10 ETH00: setting half-duplex.Also note that when I run Zeroshell between a switch and a single PC , it run the whole day without problems. The problem occurs when it is place between the Internet Modem/Router and my server.
BTW, Zeroshell is being run a 1.5GHz P4, 256MB RAM PC.
Any suggestions?
Here is the section of my kernel messages I extracted the above messages from:
08:18:09 BRIDGE00: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
08:18:10 device ETH00 entered promiscuous mode
08:18:10 ETH00: setting half-duplex.
08:18:10 device ETH01 entered promiscuous mode
08:18:10 ETH01: setting full-duplex.
08:18:10 BRIDGE00: port 2(ETH01) entering learning state
08:18:10 BRIDGE00: port 1(ETH00) entering learning state
08:18:11 physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
08:18:11 message repeated 17 times
08:18:11 physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
08:18:11 message repeated 47 times
08:18:25 BRIDGE00: topology change detected, propagating
08:18:25 BRIDGE00: port 2(ETH01) entering forwarding state
08:18:25 BRIDGE00: topology change detected, propagating
08:18:25 BRIDGE00: port 1(ETH00) entering forwarding state