On Mon, 5 Jun 2000, Frank Hart wrote: <cut>
That's the only solution I found so far.
But this won't work for you cause you don't have a 3com, right ? ;-) (I've seen you're posts about this problem too). But I don't think I want to use a hacked 3com driver. Just change the firewall script.
Exactly, I have to hack the tulip driver to stop _seeing_ broadcasts in, for example: tcpdump. <cut>
Ok, but I don't want to stop logging incoming traffic. I want to stop logging a specific IP on a specifig port.
Alright, some example's: # This will block the entinre remotenet on port 443: $IPCHAINS -A input -p tcp -s $REMOTENET -d $OUTERNET 443 -j DENY # This will block the remotenet on port 443 for 222.222.222.222 $IPCHAINS -A input -p tcp -s 222.222.222.222 -d $OUTERNET 443 -j DENY $IPCHAINS -A input -p udp -s 222.222.222.222 -d $OUTERNET 443 -j DENY There are a lot of more options available. Maybe you should take a look at pointman.org: "PMFirewall is an Ipchains Firewall and Masquerading Configuration Utility for Linux. It was designed to allow a beginner to build a custom firewall with little or no ipchains experience." -- www.pointman.org Pmfirewall supports tcp syncookie protection, source address verification, block non-routable ip's, block icmp attacks, etc. It's a great utility.
O well, just called @home for the 34657 time about this problem. They are getting more serious about this every day now ;-)
Let's hope on a better technology or better network engineers at @home.nl Greetz, Siert