From: Martijn Lievaart <m@rtij.nl>
To: gene.heskett@verizon.net
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] Warn people that ipchains and ipfwadm are going away.
Date: Thu, 23 Sep 2004 16:56:12 +0200 [thread overview]
Message-ID: <4152E40C.5080705@rtij.nl> (raw)
In-Reply-To: <200409220841.34453.gene.heskett@verizon.net>
Gene Heskett wrote:
>[root@gene root]# grep attackalert /var/log/messages*
>/var/log/messages.1:Sep 16 18:09:16 gene portsentry[1159]:
>attackalert: UDP scan from host: home1.bellatlantic.net/199.45.32.43
>to UDP port: 32771
>/var/log/messages.1:Sep 16 18:09:16 gene portsentry[1159]:
>attackalert: Host 199.45.32.43 has been blocked via wrappers with
>string: "ALL: 199.45.32.43"
>/var/log/messages.1:Sep 16 18:09:17 gene portsentry[1159]:
>attackalert: Host 199.45.32.43 has been blocked via dropped route
>using command: "/sbin/iptables -I INPUT -s 199.45.32.43 -j DROP"
>/var/log/messages.1:Sep 16 18:09:17 gene portsentry[1159]:
>attackalert: UDP scan from host: home1.bellatlantic.net/199.45.32.43
>to UDP port: 32771
>/var/log/messages.1:Sep 16 18:09:17 gene portsentry[1159]:
>attackalert: Host: home1.bellatlantic.net/199.45.32.43 is already
>blocked Ignoring
>
>Time to send another nastygram to verizon since thats one of their
>nameservers, and clear out that address from the hosts.deny file.
>
>FWIW, the last time that happened, in April 2003, the hack attempt
>trashed a siemans router and I had to replace it with that linksys.
>Must be time to change the user and password in it again too...
>
>FWIW, verizon has apparently a problem keeping their nameservers from
>being hacked.
>
>
Isn't this just the replies to legitimate dns queries? Wouldn't be the
first time legitimate traffic is recognised as a portscan.
HTH,
M4
next prev parent reply other threads:[~2004-09-23 14:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 23:09 [PATCH] Warn people that ipchains and ipfwadm are going away Rusty Russell (IBM)
2004-09-21 12:36 ` Marc Ballarin
2004-09-21 21:58 ` Rusty Russell
2004-09-21 21:58 ` Rusty Russell
2004-09-21 22:36 ` Marc Ballarin
2004-09-21 22:36 ` David S. Miller
2004-09-21 22:36 ` David S. Miller
2004-09-21 23:35 ` Marc Ballarin
2004-09-22 0:16 ` Patrick McHardy
2004-09-22 0:16 ` Patrick McHardy
2004-09-22 13:37 ` Marc Ballarin
2004-09-22 13:58 ` Jesper Juhl
2004-09-22 14:13 ` Richard B. Johnson
2004-09-22 11:36 ` Richard B. Johnson
2004-09-22 11:47 ` Martin Josefsson
2004-09-22 11:47 ` Martin Josefsson
2004-09-22 12:05 ` Richard B. Johnson
2004-09-22 12:41 ` Gene Heskett
2004-09-23 14:56 ` Martijn Lievaart [this message]
2004-09-22 14:19 ` Fao, Sean
2004-09-22 15:31 ` William Stearns
2004-09-22 15:31 ` William Stearns
2004-09-22 16:03 ` Richard B. Johnson
2004-09-22 16:27 ` William Stearns
2004-09-22 11:52 ` James Courtier-Dutton
2004-09-22 11:55 ` Marc Ballarin
2004-09-21 17:57 ` Bill Davidsen
[not found] <2GFBZ-61e-11@gated-at.bofh.it>
[not found] ` <2GSfS-6eW-5@gated-at.bofh.it>
[not found] ` <2H0ZO-49v-13@gated-at.bofh.it>
[not found] ` <2HdDL-48z-53@gated-at.bofh.it>
[not found] ` <2HdNp-4eJ-27@gated-at.bofh.it>
2004-09-22 12:15 ` Andi Kleen
2004-09-22 14:04 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2004-09-23 18:07 Albert Cahalan
2004-09-23 19:33 ` Chris Friesen
2004-09-23 19:36 ` Albert Cahalan
2004-09-23 19:57 ` Andy Lutomirski
2004-09-23 19:57 ` David S. Miller
2004-09-23 23:08 ` Matthew Garrett
2004-09-23 23:25 ` David S. Miller
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=4152E40C.5080705@rtij.nl \
--to=m@rtij.nl \
--cc=gene.heskett@verizon.net \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.