From: Athan <netfilter@miggy.org>
To: deff <deff@sadomain.co.za>
Cc: netfilter@lists.netfilter.org
Subject: Re: Spoofed ip's
Date: Tue, 11 Feb 2003 17:09:36 +0000 [thread overview]
Message-ID: <20030211170936.GC6194@miggy.org> (raw)
In-Reply-To: <1044948351.23287.11.camel@filth.sadomain.co.za>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
On Tue, Feb 11, 2003 at 09:25:50AM +0200, deff wrote:
> Could anyone please check the rules below and tell me if the the source
> ip'ss are valid. I'm seeing an incredible amount of these ip's
> attempting to get through .
Check them using whois:
15:34:49 0$ whois 1.0.0.0
OrgName: Internet Assigned Numbers Authority
OrgID: IANA
Address: 4676 Admiralty Way, Suite 330
City: Marina del Rey
StateProv: CA
PostalCode: 90292-6695
Country: US
NetRange: 1.0.0.0 - 1.255.255.255
CIDR: 1.0.0.0/8
NetName: RESERVED-9
NetHandle: NET-1-0-0-0-1
Parent:
NetType: IANA Reserved
Comment:
RegDate:
Updated: 2002-09-12
OrgTechHandle: IANA-ARIN
OrgTechName: Internet Corporation for Assigned Names and Number
OrgTechPhone: +1-310-823-9358
OrgTechEmail: res-ip@iana.org
# ARIN WHOIS database, last updated 2003-02-10 20:00
# Enter ? for additional hints on searching ARIN's WHOIS database.
So, yes, that one shouldn't be getting used at all.
-Ath
--
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
Finger athan(at)fysh.org for PGP key
"And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2003-02-11 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 7:25 Spoofed ip's deff
2003-02-11 15:56 ` uniplex
2003-02-12 1:28 ` Arnt Karlsen
2003-02-12 8:51 ` Adam D. Barratt
2003-02-11 17:09 ` Athan [this message]
2003-02-11 19:22 ` Gastón Franco
2003-02-12 8:56 ` Adam D. Barratt
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=20030211170936.GC6194@miggy.org \
--to=netfilter@miggy.org \
--cc=deff@sadomain.co.za \
--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 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.