[Bug 227086] Upgraded world - broken OpenVPN second tun - ifconfig: ioctl (SIOCAIFADDR): File exists
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Mar 30 06:19:20 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227086
--- Comment #2 from Marek <zillion1 at o2.pl> ---
Hi Eugene,
I can test old revision only (home server "in production") :)
Some more outputs from working/current configuration:
# ifconfig tun0
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1500
options=80000<LINKSTATE>
inet 10.20.20.1 --> 10.20.20.2 netmask 0xffffff00
groups: tun
Opened by PID 789
# ifconfig tun1
tun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1500
options=80000<LINKSTATE>
inet 10.20.20.10 --> 10.20.20.1 netmask 0xffffff00
groups: tun
Opened by PID 24835
# netstat -rn
Routing tables
Internet:
Destination Gateway Flags Netif Expire
default 11.22.33.44 UGS igb1
10.20.20.0/24 10.20.20.2 UGS tun0
10.20.20.1 link#9 UH tun1
10.20.20.2 link#5 UH tun0
10.20.20.10 link#9 UHS lo0
11.22.33.0/22 link#2 U igb1
11.22.33.44 link#2 UHS lo0
127.0.0.1 link#3 UH lo0
192.168.0.0/24 link#1 U igb0
192.168.0.1 link#1 UHS lo0
192.168.8.0/24 link#4 U ue0
192.168.8.100 link#4 UHS lo0
# ps ax | grep openvpn
789 - Ss 1:01,30 /usr/local/sbin/openvpn --cd /usr/local/etc/openvpn
--daemon openvpn --config /usr/local/etc/openvpn/server.conf --writepid
/var/run/openvpn.pid
24835 - Ss 0:06,92 /usr/local/sbin/openvpn --cd /usr/local/etc/openvpn
--daemon openvpn_client --config /usr/local/etc/openvpn/client.conf --writepid
/var/run/openvpn_client.pid
My home host is "master" OpenVPN server for about 20 other remote family
clients.
They're connecting to the server without any problems (after install world
there was no probem with them too).
The OpenVPN client (tun1) on master host is configured to listen some services
like mail, www, and couple of others.
Additionaly I have failover server in remote localization, so in case
connectivity problems to master host, the failover takes over with 10.20.20.1
IP address. Clients reconnect after some timeout to the failover.
The failover is not FreeBSD based system, and there's no services like mail,
www, and so on, its task is to keep connectivity beetween other clients if main
host is temporarily down.
To aviod unnecessary requests to the failover from clients, I created on master
host the VPN client next to server with 10.20.20.10 IP address.
Regards,
Marek
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-net
mailing list