> proxy:~# dmesg | grep -A1 Bridge > NET4: Ethernet Bridge 008 for NET4.0 > device eth1 entered promiscuous mode
When I run the same command (kernel 2.4.22) I get this: # dmesg | grep -A1 Bridge NET4: Ethernet Bridge 008 for NET4.0 Bridge firewalling registered So the lack of "Bridge firewalling" in your kernel would be a plausible explanation. Whatever that means... ;-) I've read somewhere that the "standard" bridge-code in Linux is insufficient for a transparent proxy. The technical details is long and pretty hard to understand, but when I read it I did understand parts of it. Anyway, the bottom-line was a need for patching the kernel. Now, I've not able to verify the output of dmesg with a "standard bridge" in Linux, but my best shot would be to sugest that you'd not patched your kernel with the bridge-nf patch... I may be wrong though... ;-) Bob. _______________________________________________ Bridge mailing list [EMAIL PROTECTED] http://www.math.leidenuniv.nl/mailman/listinfo/bridge
