Quick, maybe OT, question: after getting the bridging stuff and new kernel going, a netstat-na reveals a tcp listening on 31338... Know what that is? Only thing I can find is a trojan port. With no ip address on the box, it probably isn't a problem but could tcp port 31338 be related to a legit use of bridging + iptables?
>>> "Lund, Kjetil" <[EMAIL PROTECTED]> 10/08/02 10:32AM >>> Do you have an example of such output? It could be netfilter debug information. Try switching off Network packet filtering debugging and recompile your kernel. There are possibly other ways to do this too, but I know this method is a safe one.. Regards Kjetil Lund Technical Weekletter, Norway > -----Original Message----- > From: Pete Davis [mailto:[EMAIL PROTECTED]] > Sent: 8. oktober 2002 17:12 > To: [EMAIL PROTECTED] > Subject: [Bridge] IPtables with bridging > > > I've been working on getting a bridging firewall to work with RH7.3 > (2.4.19) and bridge-nf-0.0.7-against-2.4.19.diff. I think I > finally got > it working when I put in the command, 'ifconfig mybridge up'. > > The problem is the promiscuous mode has taken over my console. It is > constantly spitting out information about the 'mybridge' interface on > the screen and I cannot interact with the computer anymore. The only > thing I can do is hit ctrl+c repeatedly then type in > 'ifconfig mybridge > down', which shuts down the bridging (and the output to the screen). > Any help? > > Thanks for any help. > _______________________________________________ > Bridge mailing list > [EMAIL PROTECTED] > http://www.math.leidenuniv.nl/mailman/listinfo/bridge > _______________________________________________ Bridge mailing list [EMAIL PROTECTED] http://www.math.leidenuniv.nl/mailman/listinfo/bridge
