Re: more on latency

2001-07-10 Thread Terry Lambert
Jim Bryant wrote: > Terry Lambert wrote: > > Kenneth Wayne Culver wrote: > > > I think I found the reason that my FreeBSD box is performing > > > so poorly as a NATing router. When I do an ipnat -l to see > > > what "active connections" are there on the router, a list > > > about 3 pages long (usi

Re: more on latency

2001-07-10 Thread Stephen McKay
On Monday, 9th July 2001, Terry Lambert wrote: >Kenneth Wayne Culver wrote: >> >> I think I found the reason that my FreeBSD box is performing >> so poorly as a NATing router. When I do an ipnat -l to see >> what "active connections" are there on the router, a list >> about 3 pages long (using i

Re: more on latency

2001-07-09 Thread Jim Bryant
Terry Lambert wrote: > > Kenneth Wayne Culver wrote: > > > > I think I found the reason that my FreeBSD box is performing > > so poorly as a NATing router. When I do an ipnat -l to see > > what "active connections" are there on the router, a list > > about 3 pages long (using ipnat -l | more) app

Re: more on latency

2001-07-09 Thread Terry Lambert
Kenneth Wayne Culver wrote: > > I think I found the reason that my FreeBSD box is performing > so poorly as a NATing router. When I do an ipnat -l to see > what "active connections" are there on the router, a list > about 3 pages long (using ipnat -l | more) appears. I think > maybe it's having t

Re: more on latency

2001-07-09 Thread Julian Elischer
that shouldn't take TOO long.. It's possible however that it takes a while to be scheduled. you might try puting natd in the real-time scheduling queue. On Mon, 9 Jul 2001, Kenneth Wayne Culver wrote: > I think I found the reason that my FreeBSD box is performing so poorly as > a NATing router.