On Saturday 14 July 2007 21:21:32 Brian Somers wrote: > On Sun, 22 Apr 2007 13:18:49 +0200 Stefan Ehmann <[EMAIL PROTECTED]> wrote: > > 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. > > It looks like the problem is in the vpnc-script destroy_tun_device() > function, but even if I add FreeBSD to that, it creates the additional > interfaces. Maybe this is because I'm passing it bogus data and the > connection attempt doesn't cleanup properly either. > > Have you tried talking to the port writer or maintainer?
No. I haven't checked if a "ifconfig tunX destroy" works on the commandline. That should reveal the source of the problem. If this works, the problem shouldn't be it if_tun code. Unfortunately, I have no working CURRENT setup ATM, so I can't test it. _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
