Re: smurf... still?

[bow]

seems to be hookup.net..

bow[bow]$ host -l hookup.net | grep "165.154.1."
auth1.hookup.net has address 165.154.105.17
smtp1.hookup.net has address 165.154.105.13
smtp1.hookup.net has address 165.154.105.15
ns1.hookup.net has address 165.154.105.1
mail1.hookup.net has address 165.154.105.5
ns2.hookup.net has address 165.154.105.2
loki.tor.hookup.net has address 165.154.1.21
noc.tor.hookup.net has address 165.154.1.1
vertex.tor.hookup.net has address 165.154.1.7
---
bow[bow]$ whois 165.154.1.1
HookUp Communications (NOC9-HST)

   Hostname: NOC.TOR.HOOKUP.NET
   Address: 165.154.1.1
   System: ? running ?

   Coordinator:
      Hookup Communications Registry  (HCR2-ORG)  registry@HOOKUP.NET
      905-847-8000
Fax- 905-847-8420

   Domain Server

   Record last updated on 24-Mar-97.
   Database last updated on 3-Feb-98 04:10:40 EDT.


The InterNIC Registration Services Host contains ONLY Internet Information
(Networks, ASN's, Domains, and POC's).
Please use the whois server at nic.ddn.mil for MILNET Information.
----

-bow

>I was looking through a modified copy of smurf.c I had (it listened on a
>port and when an incoming connection was detected, it asked for a host and
>then smurfed it--or so the documentation says, I just wanted to see how
>the port listening was achieved) and just wanted to check how many of the
>broadcasts in the default bcastaddr[] still were smurfable, and noted that
>the *very first one* was. How would I go about finding out the
>administrative contact for a network given its broadcast address?
>Specifically I'm looking for 165.154.1.255, but there are probably some
>others as well...
>
>
>root@narnia:~# ping -c2 165.154.1.255
>PING 165.154.1.255 (165.154.1.255): 56 data bytes
>64 bytes from 165.154.1.26: icmp_seq=0 ttl=241 time=287.2 ms
>64 bytes from 165.154.1.66: icmp_seq=0 ttl=241 time=309.0 ms (DUP!)
>64 bytes from 165.154.1.7: icmp_seq=0 ttl=241 time=338.9 ms (DUP!)
>64 bytes from 165.154.125.53: icmp_seq=0 ttl=242 time=358.8 ms (DUP!)
>64 bytes from 165.154.1.1: icmp_seq=0 ttl=241 time=388.9 ms (DUP!)
>64 bytes from 127.0.0.2: icmp_seq=0 ttl=241 time=399.1 ms (DUP!)
>64 bytes from 165.154.1.8: icmp_seq=0 ttl=241 time=418.8 ms (DUP!)
>64 bytes from 165.154.1.57: icmp_seq=0 ttl=241 time=439.0 ms (DUP!)
>64 bytes from 165.154.1.4: icmp_seq=0 ttl=241 time=449.0 ms (DUP!)
>64 bytes from 165.154.1.21: icmp_seq=0 ttl=241 time=459.0 ms (DUP!)
>64 bytes from 165.154.125.53: icmp_seq=1 ttl=242 time=219.8 ms
>
>--- 165.154.1.255 ping statistics ---
>2 packets transmitted, 2 packets received, +10 duplicates, 0% packet loss
>round-trip min/avg/max = 219.8/378.0/468.9 ms
>root@narnia:~#
>
>(what the heck is that 127.0.0.2 doing in there...?)
>
>--
>Daniel Reed <n@narnia.n.ml.org> (3CE060DD)
>System administrator of narnia.n.ml.org (narnia.mhv.net [199.0.0.118])
>What does not destroy me, makes me strong. -- Friedrich Nietzsche