* pppd Filtering
@ 2004-09-10 9:10 Neil Wilson
2004-09-10 20:43 ` Clifford Kite
2004-09-14 21:18 ` Gilles Espinasse
0 siblings, 2 replies; 3+ messages in thread
From: Neil Wilson @ 2004-09-10 9:10 UTC (permalink / raw)
To: linux-ppp
Hi Guys,
I have been trying to solve a problem with a server staying online and not
disconnecting, because activity is keeping the link up.
The activity from the /var/log/messages is "IN=ppp0 OUT= MACSRC\x155.239.185.193 DST\x155.239.198.170 LENH TOS=0x00 PREC=0x00 TTL\x123
IDI468 DF PROTO=TCP SPT\x1919 DPTD5 WINDOW‡60 RES=0x00 SYN URGP=0"
As far as I am aware this is activity cause by the Sasser worm trying to get
into my network, and it is getting blocked by the firewall.
I have tried using ppp filtering to stop these,with the line 'active-filter
"not port 445"' in the options.demand file, but this has made no difference.
I have also tried using different syntax's, including adding "inbound" or
"outbound", and I get the following error. "pppd: error in active-filter
expression: inbound/outbound not supported on linktype 0"
Please could someone help me in filtering this activity, so that my server
disconnects when it is supposed to.
I am running slackware 10, with ppp filtering compiled in the kernel by
default, and pppd has the filter option enable also by default.
My idle time is set to 120 in my options.demand file.
Many thanks in advance!
Neil Wilson
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: pppd Filtering
2004-09-10 9:10 pppd Filtering Neil Wilson
@ 2004-09-10 20:43 ` Clifford Kite
2004-09-14 21:18 ` Gilles Espinasse
1 sibling, 0 replies; 3+ messages in thread
From: Clifford Kite @ 2004-09-10 20:43 UTC (permalink / raw)
To: linux-ppp
On Fri, 10 Sep 2004, Neil Wilson wrote:
|I have been trying to solve a problem with a server staying online and not
|disconnecting, because activity is keeping the link up.
My comments don't solve the problem but perhaps will give you some basis
for comparison.
|The activity from the /var/log/messages is "IN=ppp0 OUT= MAC|SRC\x155.239.185.193 DST\x155.239.198.170 LENH TOS=0x00 PREC=0x00 TTL\x123
|IDI468 DF PROTO=TCP SPT\x1919 DPTD5 WINDOW‡60 RES=0x00 SYN URGP=0"
|
|As far as I am aware this is activity cause by the Sasser worm trying to get
|into my network, and it is getting blocked by the firewall.
|
|I have tried using ppp filtering to stop these,with the line 'active-filter
|"not port 445"' in the options.demand file, but this has made no difference.
|
|I have also tried using different syntax's, including adding "inbound" or
|"outbound", and I get the following error. "pppd: error in active-filter
|expression: inbound/outbound not supported on linktype 0"
If this was any distribution except Slackware then I'd say the pppd that
came with it has been modified and broken. This type of error is typical
if you use tcpdump, at least a version cetera Oct 2002:
~# tcpdump -i ppp0 'outbound'
tcpdump: inbound/outbound not supported on linktype 113
(I've no idea what "linktype" means but, IMHO, the maintainer of tcpdump
should fix tcpdump to support inbound/outbound on PPP interface, as the
tcpdump man pages appear to say it does.)
But the active-filter works fine with the 2.4.1 or 2.4.2 pppds that I've
compiled using any 2.4.x kernel complied with the proper options, at least
through 2.4.24 (I also compile my kernels). I use
active-filter '(outbound and not (icmp[0] = 0))'
to reset the idle timer only for outbound traffic that is not a ping echo
reply (I don't care if someone pings me but don't want the reply to reset
the timer). That and a firewall has been very effective. The firewall
allows me to initiate a TCP connection but prevents other hosts from
initiating connections not associated with an existing connection unless
a server port is specifically allowed.
There was a problem with active-filter in kernels 2.6.6 and 2.6.7, but this
one seems to be different and no such message was generated. The problem
is fixed in 2.6.8.1, the latest "stable" kernel I know about.
|Please could someone help me in filtering this activity, so that my server
|disconnects when it is supposed to.
|
|I am running slackware 10, with ppp filtering compiled in the kernel by
|default, and pppd has the filter option enable also by default.
|My idle time is set to 120 in my options.demand file.
It seems to me you have two problems. The active-filter problem and a
firewall problem. I can't imagine what's causing the active-filter
problem, given that pppd and the kernel are both compiled to support it.
My firewall is based this one:
http://iptables-tutorial.frozentux.net/scripts/rc.firewall.txt
Tuning it to suit me wasn't hard, and I'm far from being an iptables
expert.
---
Clifford Kite http://ckite.no-ip.net
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: pppd Filtering
2004-09-10 9:10 pppd Filtering Neil Wilson
2004-09-10 20:43 ` Clifford Kite
@ 2004-09-14 21:18 ` Gilles Espinasse
1 sibling, 0 replies; 3+ messages in thread
From: Gilles Espinasse @ 2004-09-14 21:18 UTC (permalink / raw)
To: linux-ppp
> >I have also tried using different syntax's, including adding "inbound" or
> > "outbound", and I get the following error. "pppd: error in active-filter
> > expression: inbound/outbound not supported on linktype 0"
If your distrib use libpcap0.8.3, you may need to patch libpcap with this
one line patch
http://cvs.sourceforge.net/viewcvs.py/ipcop/ipcop/src/patches/Attic/libpcap-0.8.3-ppp.patch?rev=1.1.2.1&only_with_tag=IPCOP_v1_4_0&view=markup
To set active-filter rules, you could use the rule like in this subject
http://marc.theaimsgroup.com/?l=ipcop-user&m\x105289571806648&w=2
and adjust to 445
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-09-14 21:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-09-10 9:10 pppd Filtering Neil Wilson
2004-09-10 20:43 ` Clifford Kite
2004-09-14 21:18 ` Gilles Espinasse
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).