tun devices and vpnc in CURRENT
- From: Stefan Ehmann <shoesoft@xxxxxxx>
- Date: Sun, 22 Apr 2007 13:18:49 +0200
On CURRENT, each time I stop/start vpnc a new tun device is created.
Since I restart vpnc every time I re-connect to the network, my ifconfig
output fills up with tun devices.
On 6.2-RELEASE the tun0 device is reused each time I run vpnc.
Reverting to src/sys/net/if_tun.c rev 1.162 shows the old behaviour. (It seems
I'm noticing this a bit late)
Is this a bug in either CURRENT or vpnc?
If I set sysctl net.link.tun.devfs_cloning=0, vpnc doesn't work at all:
# vpnc
vpnc version 0.4.0
kldload: can't load if_tun: File exists
can't initialise tunnel interface: No such file or directory
This is a CURRENT as of today. Please tell me if you need more info.
Stefan
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Prev by Date: Re: rtentry and rtrequest
- Next by Date: Off: vpnc haxx
- Previous by thread: Network interface failover in 6.2?
- Next by thread: Off: vpnc haxx
- Index(es):
Relevant Pages
- Re: tun devices and vpnc in CURRENT
... output fills up with tun devices. ... On 6.2-RELEASE the tun0 device is reused
each time I run vpnc. ... I haven't checked if a "ifconfig tunX destroy" works on
the commandline. ... (freebsd-net) - Re: tun devices and vpnc in CURRENT
... output fills up with tun devices. ... On 6.2-RELEASE the tun0 device is reused
each time I run vpnc. ... can't initialise tunnel interface: ... I haven't
checked if a "ifconfig tunX destroy" works on the commandline. ... (freebsd-net)
