Hi, On Mon, Jul 23, 2018 at 04:51:53PM +0200, Adam wrote: > Hoping that clarifies your concern. :)
It leaves me a bit puzzled, to be honest... our buildbots *should*
have caught it (NetBSD 5.1/amd64 and NetBSD 7.0.1/i386), as it runs a
"topology subnet" test and tries to ping the remote IP and something
"behind" it...
If I run the test by hand, it does indeed fail.
...
Mon Jul 23 17:28:43 2018 /sbin/ifconfig tun1 10.194.3.14 10.194.3.14 mtu 1500
netmask 255.255.255.0 up
Mon Jul 23 17:28:43 2018 /sbin/route add -net 10.194.0.0 10.194.3.1 -netmask
255.255.255.0
nbsd70$ netstat -rn |grep 10.194
10.194.0/24 10.194.3.1 UGS - - - tun1
10.194.3.14 10.194.3.14 UH - - - tun1
nbsd70$ ping 10.194.3.1
PING 10.194.3.1 (10.194.3.1): 56 data bytes
^C
----10.194.3.1 PING Statistics----
5 packets transmitted, 0 packets received, 100.0% packet loss
Now, two actions on me...
... figure out why the NetBSD buildslaves did not detect the problem in
the first place (most likely "not running the remote client test suite due
to mistakes in setting up things")
... test your patch and get it in :-)
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany [email protected]
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Openvpn-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-devel
