Mailinglist Archive: opensuse-security (206 mails)
| < Previous | Next > |
Re: [suse-security] How to NOT log a packet
- From: "S.G. Zijl" <sgzijl@xxxxxx>
- Date: Mon, 5 Jun 2000 16:58:26 +0200 (CEST)
- Message-id: <Pine.LNX.4.21.0006051639450.1001-100000@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
<cut>
Hello Frank,
If you are connected to the internet with a 3com networkcard shipped
with your @Home connection, you are very lucky, because there's a patch
available in the newsgroup athome.nl.linux which cancle broadcast traffic
on your networkcard. Believe it or not: you won't see any broadcast
traffic anymore.
That's the only solution I found so far.
Cable Internet is a shared medium, not a point to point connection like
internet by modem/isdn/etc. @Home won't stop broadcasters.
A solution for your firewall, change
IPCHAINS -F input -l
to
IPCHAINS -F input
It stops logging incoming traffic what means you can turn on your
syslogd again.
Greetz, Siert
Hello Frank,
If you are connected to the internet with a 3com networkcard shipped
with your @Home connection, you are very lucky, because there's a patch
available in the newsgroup athome.nl.linux which cancle broadcast traffic
on your networkcard. Believe it or not: you won't see any broadcast
traffic anymore.
That's the only solution I found so far.
So until @home manages to stop the broadcasts from this individual I
like not to log these packets. I guess it starts something like
Cable Internet is a shared medium, not a point to point connection like
internet by modem/isdn/etc. @Home won't stop broadcasters.
A solution for your firewall, change
IPCHAINS -F input -l
to
IPCHAINS -F input
It stops logging incoming traffic what means you can turn on your
syslogd again.
Greetz, Siert
| < Previous | Next > |