Dynamic routing table

2001-04-03 Thread Dmitry Samersoff
Dynamic routing table on my server (4.2-RELEASE) grow up infinitely. This is sample line of netstat -nra | grep W3 12.89.146.201 213.24.224.1 UGHW3 0 120 fxp0 => sysctl variables: net.inet.ip.rtexpire: 2 net.inet.ip.rtminexpire: 2 net.inet.ip.rtmaxcache

Re: Recent interface/routing changes breaks on-demand PPP (+sppp)

2001-04-03 Thread Alexander Leidinger
On 2 Apr, Ruslan Ermilov wrote: > OK, we fixed the "ifconfig down" case already. The attached patch alters > inet routing code so that it does not delete routes with the "default" > source address of 0.0.0.0; ip_output() will take care of choosing the > right address. Please let me know if it

Re: Recent interface/routing changes breaks on-demand PPP (+sppp)

2001-04-03 Thread Ruslan Ermilov
On Tue, Apr 03, 2001 at 04:13:27PM +0200, Alexander Leidinger wrote: > On 2 Apr, Ruslan Ermilov wrote: > > > OK, we fixed the "ifconfig down" case already. The attached patch alters > > inet routing code so that it does not delete routes with the "default" > > source address of 0.0.0.0; ip_outp

Re: Recent interface/routing changes breaks on-demand PPP (+sppp)

2001-04-03 Thread Alexander Leidinger
On 3 Apr, Ruslan Ermilov wrote: > On Tue, Apr 03, 2001 at 04:13:27PM +0200, Alexander Leidinger wrote: >> On 2 Apr, Ruslan Ermilov wrote: >> >> > OK, we fixed the "ifconfig down" case already. The attached patch alters >> > inet routing code so that it does not delete routes with the "default"

Re: Linux Vs. FreeBSD Networking Performance

2001-04-03 Thread Michael C . Wu
On Fri, Mar 23, 2001 at 08:55:41AM +0800, David Xu scribbled: | Friday, March 23, 2001, 3:12:19 AM, you wrote: | JG> Interesting topic in the linux kernel mailing list (Linux is "a lot" faster than | JG> FreeBSD): | JG> http://kt.zork.net/kernel-traffic/latest.html#2 | | JG> I came to use FreeBSD

Re: Linux Vs. FreeBSD Networking Performance

2001-04-03 Thread Rik van Riel
On Tue, 3 Apr 2001, Michael C . Wu wrote: > I can confirm the following: > A) You are a troll. > B) The above "confirmation" states nothing. You fail >to state the conditions of the test. You do not qualify >your statements with facts. Neither do you. Does that make you a troll too?

Re: Linux Vs. FreeBSD Networking Performance

2001-04-03 Thread Jeremiah Gowdy
> On Tue, 3 Apr 2001, Michael C . Wu wrote: > > > I can confirm the following: > > A) You are a troll. > > B) The above "confirmation" states nothing. You fail > >to state the conditions of the test. You do not qualify > >your statements with facts. > > Neither do you. Does that make you

Jumbo Frames support for WX driver?

2001-04-03 Thread Geoff Mohler
I know that Network Appliance uses the Intel GigE cards in thier boxes, and they have jumbo frames support... Im just wondering if since I use the same card in my FreeBSD box with a NetApp backend..if the wx driver has JF support as well? Anyone? To Unsubscribe: send mail to [EMAIL PROTECTED]

Slow netstat -r printout

2001-04-03 Thread Daehyun Yoon
Hi all, I'm having some strange problem with netstat. Every once in a while when I type netstat -r, it takes minutes until it displays the entire output. Sometimes it never finishes. Strange thing is if I type netstat -n or netstat -nr, it doesn't take more than a half a second to get the entire

Re: Slow netstat -r printout

2001-04-03 Thread Dan Debertin
It's taking so long because it's trying to do a DNS resolution of every IP address that it prints. My guess is that @Home uses some non-registered RFC1918 address space for its clients, so those addresses will never resolve, and will take forever not doing so. The -n flag disables DNS resolution,

Re: FW: Network lockups on fxp0?

2001-04-03 Thread Vladimir B. Grebenschikov
Jonathan Lemon writes: > >>fxp0: SCB timeout > >>fxp0: DMA timeout > >>(repeating) > > SCB timeout comes about because the chip is refusing to accept > any more commands; in this case, it probably is wedged. Is there > any pattern to this? Do you happen to have hardware flowcontrol > en

Re: Slow netstat -r printout

2001-04-03 Thread Matthew Emmerton
> It's taking so long because it's trying to do a DNS resolution of every IP > address that it prints. My guess is that @Home uses some non-registered > RFC1918 address space for its clients, so those addresses will never > resolve, and will take forever not doing so. The -n flag disables DNS > re