🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.protocols.tcp-ip
Article #15462

Re: Where should I report port scans?

#15462
From: Walter Dnes
Date: Fri, 13 Apr 2001 07:28
49 lines
3979 bytes
On Tue, 10 Apr 2001 19:33:10 -0400, Lawrence Baldwin, <baldwinl@mynetwatchman.com> wrote:

> The other solution is getting more agents reporting the attacks,
> so it's a lot easier to have 3,4,5++ victims reporting the
> same attacker...but I'm workin on that....should have >format-
> independent< log uploader done in about a week...this will add
> the much awaited Zone Alarm support (currently  myNetWatchman
> Agent for Windows  only supports BlackICE) AND all uploads will
> be real- time via HTTP (vs. delayed FTP).

  How about syslogd format ?  The Netgear RT314 has powerful firewalling
rules, but the telnet interface is somewhat klunky.  I have it log
dropped packets, and my linux machine picks up the log data.  Here is
sample output.  Note that each line starts with Date+Time.  It probably
wraps horribly on your display.

Apr 10 22:21:22 192.168.1.1 NetgearRT314: IP[Src=64.250.146.56 Dst=64.231.8.153 UDP spo=00137  dpo=00137]}S01>R02mD
Apr 10 22:23:56 192.168.1.1 last message repeated 3 times
Apr 10 22:23:59 192.168.1.1 last message repeated 2 times
Apr 11 01:26:00 192.168.1.1 NetgearRT314: IP[Src=63.238.218.124 Dst=64.231.1.208 TCP spo=03379  dpo=00111]}S01>R01mD
Apr 11 01:26:03 192.168.1.1 NetgearRT314: IP[Src=63.238.218.124 Dst=64.231.1.208 TCP spo=03379  dpo=00111]}S01>R01mD
Apr 11 01:53:57 192.168.1.1 NetgearRT314: IP[Src=64.230.181.205 Dst=64.231.1.208 TCP spo=01944  dpo=00021]}S01>R01mD
Apr 11 01:54:00 192.168.1.1 NetgearRT314: IP[Src=64.230.181.205 Dst=64.231.1.208 TCP spo=01944  dpo=00021]}S01>R01mD
Apr 11 20:33:39 192.168.1.1 NetgearRT314: IP[Src=211.78.243.11 Dst=64.231.17.158 TCP spo=02343  dpo=00111]}S01>R01mD
Apr 11 21:04:42 192.168.1.1 NetgearRT314: IP[Src=202.106.67.108 Dst=64.231.17.158 TCP spo=04401  dpo=00111]}S01>R01mD

  The interesting stuff is...
  - "IP[Src=" the (alleged) source
  - "Dst=" destination (my IP address at that time)
  - UDP/TCP (protocol type)
  - "spo="/"dpo=" source/destination port respectively

  My rule descriptor obviously depends on the exact rules I have defined.
See http://www.waltdnes.org/security/netgear.html for my "paranoia plus"
Netgear ruleset.

  }S01>R02mD
     \   \ \\_Drop packet
      \   \ \_take action (in this case, Drop) when condition is matched
       \   \__Rule 2 within the Set
        \_____Set 1 (Each Set can contain up to 6 Rules)

  This may not be standard ipchains output, but it's close.  I seem to
occasionally inherit a dynamic IP that recently belonged to a Napster
server, and I get a storm of attempted connections.

-- 
Walter Dnes
<waltdnes@waltdnes.org>
Technical Details
Message-ID: <9b69qs$24sc$1@news.tht.net>
Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!news.gv.tsc.tdk.com!hub.org!hub.org!waltdnes
References: <3A9C3710.7F2E86F8@mynetwatchman.com> <96gk79.khf.ln@linux.abbitt.org> <wJOy6.3081$Rv.131064@news1.atl> <MPG.15369849667cdc0c989685@news2.mia.bellsouth.net> <xF6z6.315$U4.11027@burlma1-snr2> <MPG.153b74cbe7ab82a8989695@news2.mia.bellsouth.net> <9asm06$pvu$1@new-usenet.uk.sun.com> <B6F8472D.B0F7%nan-ae@nospam.nospam.porterfield.net.foo> <MPG.153d623dfe50249b9896a1@news2.mia.bellsouth.net>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10090f,64b87d735e5bf97e
X-Google-Attributes: gid10090f,public
X-Google-Thread: f9325,5fddf9b17d575149
X-Google-Attributes: gidf9325,public
X-Google-Thread: 104f05,64b87d735e5bf97e
X-Google-Attributes: gid104f05,public
X-Google-ArrivalTime: 2001-04-13 00:30:50 PST
Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!news.gv.tsc.tdk.com!hub.org!hub.org!waltdnes
From: waltdnes@waltdnes.org (Walter Dnes)
Newsgroups: comp.protocols.tcp-ip,bellsouth.net.security,news.admin.net-abuse.email
Subject: Re: Where should I report port scans?
Date: Fri, 13 Apr 2001 07:28:29 +0000 (UTC)
Organization: Hub.Org Networking Services (http://www.hub.org)
Lines: 49
Message-ID: <9b69qs$24sc$1@news.tht.net>
References: <3A9C3710.7F2E86F8@mynetwatchman.com> <96gk79.khf.ln@linux.abbitt.org> <wJOy6.3081$Rv.131064@news1.atl> <MPG.15369849667cdc0c989685@news2.mia.bellsouth.net> <xF6z6.315$U4.11027@burlma1-snr2> <MPG.153b74cbe7ab82a8989695@news2.mia.bellsouth.net> <9asm06$pvu$1@new-usenet.uk.sun.com> <B6F8472D.B0F7%nan-ae@nospam.nospam.porterfield.net.foo> <MPG.153d623dfe50249b9896a1@news2.mia.bellsouth.net>
Reply-To: waltdnes@waltdnes.org
X-Trace: news.tht.net 987146909 70540 216.126.72.2 (13 Apr 2001 07:28:29 GMT)
X-Complaints-To: scrappy@hub.org
User-Agent: slrn/0.9.6.2 (Linux)