Hi Tommi,

On 2016-01-13 13:20:11, you wrote to me:

 TK> Well, this is interesting:

 TK> ping 0.0.0.0
 TK> PING 0.0.0.0: 56 data bytes
 TK> 64 bytes from 127.0.0.1: icmp_seq=0. time=0. ms
 TK> 64 bytes from 192.168.1.21: icmp_seq=0. time=10. ms
 TK> 64 bytes from 127.0.0.1: icmp_seq=1. time=0. ms
 TK> 64 bytes from 192.168.1.21: icmp_seq=1. time=10. ms
 TK> 64 bytes from 127.0.0.1: icmp_seq=2. time=0. ms
 TK> 64 bytes from 192.168.1.21: icmp_seq=2. time=0. ms

 TK> My OS/2 computer has only one ip: 192.168.1.2.

 TK> 192.168.1.21 is the address of my switch.
 TK> 192.168.1.12 is the address of the router to the internet.

On 3 different versions of openSUSE I get the same result:

# ping 0.0.0.0
PING 0.0.0.0 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.026 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.017 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.018 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.014 ms
^C
-+- 0.0.0.0 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 0.014/0.018/0.026/0.006 ms

On Windows 7 I get:

C:\>ping 0.0.0.0

Pinging 0.0.0.0 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.

Ping statistics for 0.0.0.0:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

So it doesn't treat it special, and is trying to ping the address...


There is a wiki page for the 0.0.0.0 IPv4 address:

https://en.wikipedia.org/wiki/0.0.0.0

And I think binkd should treat it in the meaning of: "A way to explicitly
specify that the target is unavailable.", when it's occuring for outbound
connections.

Bye, Wilfred.

--- FMail-W32-1.69.12.144-B20160109