From: ro0ot <ro0ot@phreaker.net>
To: netfilter@lists.netfilter.org
Subject: lots of tcp port 445 traffic
Date: Tue, 07 Dec 2004 00:54:08 +0800 [thread overview]
Message-ID: <41B48EB0.3030307@phreaker.net> (raw)
Hi,
I get lots of tcp port 445 traffic when I do a tcpdump -n port 445,
could it be an attack?
I check on the syslog files at /var/log/syslog, it shows this as below: -
Dec 7 00:36:40 fw01 kernel: Neighbour table overflow.
Dec 7 00:36:46 fw01 kernel: NET: 32 messages suppressed.
Dec 7 00:36:46 fw01 kernel: Neighbour table overflow.
Dec 7 00:36:51 fw01 kernel: NET: 27 messages suppressed.
Dec 7 00:36:51 fw01 kernel: Neighbour table overflow.
Dec 7 00:38:14 fw01 kernel: NET: 6 messages suppressed.
Dec 7 00:38:14 fw01 kernel: Neighbour table overflow.
When I try to ping my router IP address, I get this message below: -
connect: No buffer space available
I did tried running the below command and it seems not helping much: -
iptables -I cus2jarwan -p tcp --dport 445 -j REJECT --reject-with tcp-reset
or
iptables -I cus2jarwan -p tcp --dport 445 -j DROP
How can I stop this tcp port 445 traffic? Or how can I prevent it?
Regards,
ro0ot
next reply other threads:[~2004-12-06 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 16:54 ro0ot [this message]
2004-12-06 22:56 ` lots of tcp port 445 traffic Paul Annesley
2004-12-09 21:17 ` Jose Maria Lopez
2004-12-09 21:37 ` Paul Annesley
2004-12-10 13:52 ` ro0ot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41B48EB0.3030307@phreaker.net \
--to=ro0ot@phreaker.net \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox