Re: Bad loopback traffic not stopped by ipfw.
From: Gleb Smirnoff (glebius_at_cell.sick.ru)
Date: 02/25/04
- Previous message: Gleb Smirnoff: "Re: rtalloc()/rtfree() problems on CURRENT"
- In reply to: Andrew Riabtsev: "Re[2]: Bad loopback traffic not stopped by ipfw."
- Next in thread: Iasen Kostov: "Re: Bad loopback traffic not stopped by ipfw."
- Reply: Iasen Kostov: "Re: Bad loopback traffic not stopped by ipfw."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 25 Feb 2004 17:16:42 +0300 To: Andrew Riabtsev <resident@b-o.ru>
On Wed, Feb 25, 2004 at 04:47:03PM +0300, Andrew Riabtsev wrote:
A> To me it would be also interesting to know where this traffic comes
A> from. I have same on my local net:
A>
A> # tcpdump -neifxp0 src or dst 127.0.0.1
A> tcpdump: listening on fxp0
A> 16:26:23.280737 0:50:fc:ed:d4:4 0:02:55:b0:90:e4 0800 60: 127.0.0.1.80 > 192.168.141.148.1928: R 0:0(0) ack 1986723841 win 0
> 16:26:23.287642 0:1:2:9>c:cf:e2 0:02:55:b0:90:e4 0800 60: 127.0.0.1.80 > 192.168.118.205.1046: R 0:0(0) ack 1959723009 win 0
This is some kind of Win32 virus. This floods can be easily
stopped by ipfw rule:
deny tcp from any to any tcpflags rst,ack
-- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
- Previous message: Gleb Smirnoff: "Re: rtalloc()/rtfree() problems on CURRENT"
- In reply to: Andrew Riabtsev: "Re[2]: Bad loopback traffic not stopped by ipfw."
- Next in thread: Iasen Kostov: "Re: Bad loopback traffic not stopped by ipfw."
- Reply: Iasen Kostov: "Re: Bad loopback traffic not stopped by ipfw."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]