1 |
Hi there, |
2 |
|
3 |
I've got one machine here on the LAN which isn't responding to |
4 |
broadcast ping. Any idea why not? |
5 |
|
6 |
$ ping -c 2 192.168.1.255 |
7 |
PING 192.168.1.255 (192.168.1.255): 56 data bytes |
8 |
64 bytes from 192.168.1.71: icmp_seq=0 ttl=64 time=0.221 ms |
9 |
64 bytes from 192.168.1.43: icmp_seq=0 ttl=64 time=0.301 ms (DUP!) |
10 |
64 bytes from 192.168.1.22: icmp_seq=0 ttl=64 time=0.405 ms (DUP!) |
11 |
64 bytes from 192.168.1.255: icmp_seq=0 ttl=255 time=0.649 ms (DUP!) |
12 |
64 bytes from 192.168.1.9: icmp_seq=0 ttl=60 time=1.646 ms (DUP!) |
13 |
64 bytes from 192.168.1.71: icmp_seq=1 ttl=64 time=0.159 ms |
14 |
|
15 |
--- 192.168.1.255 ping statistics --- |
16 |
2 packets transmitted, 2 packets received, +4 duplicates, 0% packet loss |
17 |
round-trip min/avg/max/stddev = 0.159/0.564/1.646/0.509 ms |
18 |
$ ping -c 3 192.168.1.100 |
19 |
PING 192.168.1.100 (192.168.1.100): 56 data bytes |
20 |
64 bytes from 192.168.1.100: icmp_seq=0 ttl=64 time=0.297 ms |
21 |
64 bytes from 192.168.1.100: icmp_seq=1 ttl=64 time=0.270 ms |
22 |
64 bytes from 192.168.1.100: icmp_seq=2 ttl=64 time=0.272 ms |
23 |
|
24 |
--- 192.168.1.100 ping statistics --- |
25 |
3 packets transmitted, 3 packets received, 0% packet loss |
26 |
round-trip min/avg/max/stddev = 0.270/0.280/0.297/0.012 ms |
27 |
$ |
28 |
|
29 |
|
30 |
It's a fairly recent (last 6 months or so) Gentoo build, and is |
31 |
updated fairly regularly (every month or so). |
32 |
|
33 |
I'd list package versions & stuff, but I have no idea which apply - I |
34 |
thought that ping was a part of the basic TCP/IP stack. Would it help |
35 |
if I posted the kernel .config? Is there an option in there to disable |
36 |
broadcast ping responses? |
37 |
|
38 |
This isn't very important, but it does pique my curiosity. There are |
39 |
many on here more knowledgeable than I, so perhaps someone will |
40 |
quickly identify the cause? |
41 |
|
42 |
Stroller. |