Date: Fri, 14 Mar 2003 11:50:40 -0800 (PST) From: Mike Hoskins <mike@adept.org> To: stable@FreeBSD.ORG Subject: Re: ifconfig destroy Message-ID: <20030314114552.W2608-100000@fubar.adept.org> In-Reply-To: <20030313165150.A17024@Odin.AC.HMC.Edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 13 Mar 2003, Brooks Davis wrote: > > The problem was, during my experimentation I ended up exhausting tun* > > pseudo-devs because they never got cleaned up. Nothing in tun(4) seemed > > to help and 'destroy' and 'deletetunnel' from ifconfig(8) aren't right. > tun devices can't be destroyed at this point. I'm fairly sure you > shouldn't need more tun devices then you have open connections so I > don't see how you could be running out of them. I think they are > supposed to be recycled. Right, but I've seen the same thing on RH 6.2 with ppp pseudo-devs. Sometimes when I'm setting up a SSH/PPP tunnel between a 6.2 and 7.2 box, when the tunnel is taken down 7.2 will destroy the ppp0 pseudo-dev but it will stay around forever on the 6.2 box. After the box is up for awhile and a number of tunnels have been started/stopped, ifconfig is really messy. ;) The behavior seems to act the same way with tun0 on my -stable box. I start the tunnel, stop it, then tun0 never gets cleaned up. I figure I must be missing the vital piece of information that actually lets the system know it can do the cleanup. I just wasn't sure where to find it. At first I thought pppd just wasn't letting go or something, but there are no tunnel-related processes lying around, no packets flowing, tun0 is 'down', etc. -mrh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030314114552.W2608-100000>