I had everything working great. Perfectly! So I move the servers I'm working on into the computer room, hook them up to the KVM switch, and boot them all up. Things look ok, so I go to a machine on the outside of this net connection, and call up the web site that is now in my bridged / firewalled dmz. Page dies! This had been working fine!
Ping the server and get 58% packet loss!!! WTF?!? So now I go to the actuall bridge firewall machine itself. Ping the web server that is bridged right off this machine. 53% packet loss. the two servers in the DMZ ping eachother with no packet loss. The bridge/firewall can ping any machine on the internet with no loss. So basically anything going through my eth2 gets almost 50% loss every time! Now being worried, I pinged the internal net. I got a 12% loss. This doesn't use bridging at all! Both eth2 and eth1 use the Tulip drivers. Are there problems with these?? I checked with different cables, same problem. Looks like somehow during shutdown/move/reboot eth2 went belly up. 1st time I've run into this at all. So, I figured I'd asked to see if anyone has ever had a packet loss issue with bridging. I doubt it is that. I'm going to try different drivers and or nics tomorrow. frustrated, chris _______________________________________________ Bridge mailing list [EMAIL PROTECTED] http://www.math.leidenuniv.nl/mailman/listinfo/bridge
