RE: Traffic to our customer's address(126.0.0.0/8) seems blocked by packet filter

Mailman List Mirror (Read Only)
1

Hi

Thank you for your reply.

Makoto san, can you provide an ip-address within your assigned range that people can ping to test?

You can ping to 126.66.0.30/8.

regards,

2

You can ping to 126.66.0.30/8.

and how does one ping a /8?

randy

3

Smurf. 'ping 126.255.255.255'.

How quickly they forget. :slight_smile:

4

Hi

Thank you for your reply.

Makoto san, can you provide an ip-address within your assigned range that people can ping to test?

You can ping to 126.66.0.30/8.

Just out of curiosity... are you going to continue to announce each individual /16 or will you consolidate to a single /8 announcement?

5

Randy Bush wrote:

You can ping to 126.66.0.30/8.
   
and how does one ping a /8?

Most trojans for zombie networks provide this functionality. Connect to your favourite C&C server and issue;
.advscan ping 42 2 64 126.X.X.X
(this will ping the address space with 42 threads, using two second intervals for packets, the X's work as wildcards)

After the scan has completed, issue .scanstats to view your results.

If you need to stop the pinging in the interim, issue .scanstop to cease.

Pete

6

just remember that not all networks use '126.255.255.255' as a broadcast
address. there are non-broadcast networks where that address is a 'host'
one.

[]s,

Marlon, CISSP.

7

just remember that not all networks use '126.255.255.255' as a broadcast
address. there are non-broadcast networks where that address is a 'host'
one.

i suspect not in this one interesting case, as the following ip address is
part of a very special block, 127/8.

randy

8

just remember that not all networks use '126.255.255.255'

    > as a broadcast address. there are non-broadcast networks
    > where that address is a 'host' one.

Surely the only networks on which this can be a host are:

       one using a /7 or shorter netmask
       a /31 (as per RFC3021)

-roy

9

[root@felix]# ifconfig lo0 inet 126.255.255.255 netmask 255.255.255.255 alias
[root@felix]# ping 126.255.255.255
PING 126.255.255.255 (126.255.255.255): 56 data bytes
64 bytes from 126.255.255.255: icmp_seq=0 ttl=64 time=0.088 ms
64 bytes from 126.255.255.255: icmp_seq=1 ttl=64 time=0.062 ms
^C
--- 126.255.255.255 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.062/0.075/0.088/0.013 ms
[root@felix]#

Inserting the host route for 126.255.255.255/32 into an adjacent IGP is similarly straightforward.

Joe

10

%ping 126.255.255.255 works for some mutant stacks.
  plays old-hob w/ your arp cache tho.

  but i suspect that the /8 on the reference was either
  a typo from the original query or a vestigal remainder
  from the emacs buffer.

  pinging the indicated /32 gives me this:

$ ping 126.66.0.30
PING 126.66.0.30 (126.66.0.30): 56 data bytes
64 bytes from 126.66.0.30: icmp_seq=0 ttl=235 time=311.999 ms
64 bytes from 126.66.0.30: icmp_seq=1 ttl=235 time=443.25 ms
^C
--- 126.66.0.30 ping statistics ---
3 packets transmitted, 2 packets received, 33% packet loss
round-trip min/avg/max = 311.999/377.624/443.25 ms

  from the IVTF conference hotel lobby.

--bill