[Bug 207831] r293159 breaks OpenVPN routing

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Jun 3 20:39:02 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207831

--- Comment #11 from Olivier Cochard <olivier at freebsd.org> ---
Because I didn't reach to break my OpenVPN (using the default openvpn
topology), I've tried with your manual way of reproducing the problem.

On a 10.3-RELEASE-p2:

[root at 10.3]~# ifconfig tun0 create
[root at 10.3]~# ifconfig tun0 192.168.170.1 192.168.170.2 mtu 1500 netmask
255.255.255.0 up
[root at 10.3]~# route add -net 192.168.170.0 192.168.170.1 255.255.255.0
add net 192.168.170.0: gateway 192.168.170.1 fib 0
[root at hp]~# ifconfig tun0 inet
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1500
        options=80000<LINKSTATE>
        inet 192.168.170.1 --> 192.168.170.2 netmask 0xffffff00


[root at 10.3]~# netstat -rnf inet | grep -e Destination -e 192.168.170
Destination        Gateway            Flags      Netif Expire
192.168.170.0/24   192.168.170.1      UGS        tun0
192.168.170.1      link#15            UHS         lo0
192.168.170.2      link#15            UH         tun0


On a 11.0-ALPHA1 r301229:

[root at 11-alpha1]~#ifconfig tun0 create
[root at 11-alpha1]~#ifconfig tun0 192.168.170.1 192.168.170.2 mtu 1500 netmask
255.255.255.0 up
[root at 11-alpha1]~#route add -net 192.168.170.0 192.168.170.1 255.255.255.0
[root at 11-alpha1]~# ifconfig tun0 inet
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1500
        options=80000<LINKSTATE>
        inet 192.168.170.1 --> 192.168.170.2  netmask 0xffffff00         

[root at 11-alpha1]~# netstat -rnf inet | grep -e Destination -e 192.168.170
Destination        Gateway            Flags     Netif Expire
192.168.170.0/24   192.168.170.1      UGS         lo0
192.168.170.1      link#9             UHS         lo0
192.168.170.2      link#9             UH         tun0   

Then I confirm there is a "netif" difference between 10.3 and head.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-amd64 mailing list