Bug #3401
closed
Openvpn Server IPV4 generating attribute TUN-IPV6 this right?
100%
Description
I think using ipv4 in the openvpn conf should not generate the attribute tun-ipv6 attribute and not load the ipv6 module for the virtual tunnel of openvpn
dev ovpns1 dev-type tun tun-ipv6 dev-node /dev/tun1 writepid /var/run/openvpn_server1.pid #user nobody #group nobody script-security 3 daemon keepalive 10 60 ping-timer-rem persist-tun persist-key proto udp cipher AES-128-CBC up /usr/local/sbin/ovpn-linkup down /usr/local/sbin/ovpn-linkdown local 10.10.10.12 ifconfig 10.0.8.1 10.0.8.2 lport 1194 management /var/etc/openvpn/server1.sock unix max-clients 1 route 192.168.3.0 255.255.255.0 secret /var/etc/openvpn/server1.secret comp-lzo
Updated by Chris Buechler about 10 years ago
- Category set to OpenVPN
- Priority changed from Normal to Low
- Target version set to 2.2
- Affected Version set to 2.1-IPv6
it doesn't hurt anything, but yeah that should likely only be there if the VPN is using IPv6.
Updated by Gilmar Cabral about 10 years ago
Parameter ends up being weird because openvpn is running with IPV4 and IPV6 not. I think this parameter tun-ipv6 can influence the problem of Tick 3402 which was rejected again.
Updated by Anonymous almost 10 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset b9e9903ddb21665023c9fcc241099476a42a9dbd.
Updated by Chris Buechler over 9 years ago
- Status changed from Feedback to Resolved