Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security FullDisclosure
[Top] [All Lists]

Re: [Full-Disclosure] Odd packet?

Subject: Re: [Full-Disclosure] Odd packet?
Date: Wed, 26 May 2004 17:57:30 +0200
On 26.05.2004 11:28:37 +0000, Valdis.Kletnieks@vt.edu wrote:
On Tue, 25 May 2004 22:35:25 +0200, Steffen Schumacher said:

However, as you said, no ISP, which has to follow rules and regulations in 
the
western world allows spoofing of or even routing of the 127/8 net.

1) There's no law or regulation that *requires* an ISP to not route 127/8.


Right you are.. however in rfc 1700:

Reynolds & Postel                                               [Page 4]
^L
RFC 1700                    Assigned Numbers                October 1994


      (e)   {<Network-number>, <Subnet-number>, -1}

         Directed broadcast to specified subnet.  Can only be used as
         a destination address.

      (f)   {<Network-number>, -1, -1}

         Directed broadcast to all subnets of specified subnetted
         network.  Can only be used as a destination address.

      (g)   {127, <any>}

         Internal host loopback address.  Should never appear outside
         a host.

The way I read this, then an ISP should be disturbed if there were ever reports
of seeing such pakets in their network. Furthermore why should they have routes 
to addressspace which shouldn't be used outside a node?
The ISP are in a sense implementers of an IP network, and they should conform to
RFC1700. But you're right! its no law.. along with IP..
 
2) The *source* of the packet was 127.0.0.1, and routing is done on the 
*destination*.


Really? It's amazing I got this job then!! Just kidding.. 
the 'or even routing' was a mere sidenote, but maybe that didn't shine through 
very well.. Sorry about that..
 
3) An amazing number of ISPs do *not* do proper ingress/egress filtering.


I'm beginning to hear that - I stand corrected!

/Steffen
 



<Prev in Thread] Current Thread [Next in Thread>