Subj : 0.0.0.0
To   : Tommi Koivula
From : Benny Pedersen
Date : Sat Feb 13 2016 08:37 am

Hello Tommi!

13 Jan 2016 13:20, Tommi Koivula wrote to Wilfred van Velzen:

 TK> *** Answering a msg posted in area 'European sysop's talks. '.
 TK> Wednesday January 13 2016 12:02, Wilfred van Velzen wrote to Benny 
 TK> Pedersen:

 WV>> I don't know why this happens. Maybe it's a problem in binkd, maybe
 WV>> it's a problem in a linux library...

 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.

thanks now its know that binkd should NOT dial broadcast addresses


 Regards Benny

.... there can only be one way of life, and it works :)

--- Msged/LNX 6.2.0 (Linux/4.4.0-gentoo (i686))
 * Origin: openvpn on its way here (2:230/0)

.