Here are my sysctl net settings:
net.inet.ip.forwarding=1
net.inet.ip.redirect=1
net.inet.ip.ttl=64
net.inet.ip.sourceroute=0
net.inet.ip.directed-broadcast=0
net.inet.ip.portfirst=1024
net.inet.ip.portlast=49151
net.inet.ip.porthifirst=49152
net.inet.ip.porthilast=65535
net.inet.ip.maxqueue=300
Looks like I spoke a little too soon. I am still having problems. When I
thought it was fixed the first time turns out to be that I was watching the
upside of a fluctuation. It appears the bandwidth goes from roughly 60% of
its potential capacity to 5%. I took out queuing altogether but I still
I'd try manually changing the interface media type just in case it's
that. I've seen odd things happen if you have it autodetect compared
to manually setting it to 100mbTX full duplex... (and vice versa)
Then I'd look at cables, try switching out the network card for
another, that sort of
Sorry pppoe in that example should have been $pppoe and it should
correspond to the interface you're using for pppoe and declared in the
pf.conf file. It's in the man pages anyway.
On 29 Jan 2009, at 10:06, Nick Ryan wrote:
I'd try manually changing the interface media type just in case
Thanks for the response. I did manually change the media type last night from
half to full. It was set to auto, and the switch port to which it was
connected was set to full, but for some reason it went to half. After I
changed the duplex, I didn't see any improvement. This morning I came in,
and
I've aalso tried the sysctl adjustment listed in the man pages.
net.inet.tcp.sendspace: 65536
net.inet.tcp.recvspace=65536
That seemed to make it worse if anything.
--
View this message in context:
http://www.nabble.com/Firewall-4.3-is-limiting-bandwidth-tp21720950p21721077.html
Sent from the
6 matches
Mail list logo
