Re: A problem with too many network interfaces

2003-05-27 Thread Garrett Wollman
< said: > A proper BSD port could use something like the trick in Stevens[1] and > keep retrying the call with a larger bufer until the length of the > result is the same as in the previous call. Actually, a proper BSD port would use the net.route.iflist sysctl instead. -GAWollman _

RE: A problem with too many network interfaces

2003-05-27 Thread Don Bowman
> From: Garrett Wollman [mailto:[EMAIL PROTECTED] > < =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= <[EMAIL PROTECTED]> said: > > > A proper BSD port could use something like the trick in > Stevens[1] and > > keep retrying the call with a larger bufer until the length of the > > result is the same as i

RE: A problem with too many network interfaces

2003-05-27 Thread Garrett Wollman
< said: >> Actually, a proper BSD port would use the net.route.iflist sysctl >> instead. > $ uname -sr > FreeBSD 4.6-RC > $ sysctl net.route > sysctl: unknown oid 'net.route' Irrelevant. sysctl(8) is not equipped to handle the contents of this MIB branch. > I think since the ports work agains

RE: A problem with too many network interfaces

2003-05-27 Thread Julian Elischer
On Tue, 27 May 2003, Garrett Wollman wrote: > net.route.iflist has been in FreeBSD since 2.0. I think that it needs more documentation.. by which I mean it should be referenced in more places. I only know it exists by "accident" (saw the commit). ___

Re: A problem with too many network interfaces

2003-05-29 Thread Julian Elischer
On Wed, 28 May 2003, Bruce M Simpson wrote: > On Tue, May 27, 2003 at 11:24:52AM -0700, Julian Elischer wrote: > > On Tue, 27 May 2003, Garrett Wollman wrote: > > > net.route.iflist has been in FreeBSD since 2.0. > > I think that it needs more documentation.. > > by which I mean it should be ref