Leopard is setting RWIN too large!!!

I really don't know diddly about terminal and when I try to enter the information you have listed, I go no where. I know I'm just not entering this correctly and I was wondering if you can give a computer illiterate older woman some clearer info:
in the first line - is that a space between the cd and the slash?
do you hit enter after each line?
in line 2 - what if it doesn't ask for your password? what password are you referring to?
line 4 - do you hit the CTRL-X or type those letters in?

I know I sound really stupid but I can't learn unless I ask questions - right?
Thank you in advance for your patience and assistance.

1. Yes cd <space> /etc
2. Yes hit enter after every line
3. If it doesn't ask for your password then something is wrong, make sure you typed "sudo" first
4. You hit that key combo so hold down the ctrl key and then x

Stupid people don't ask questions, we all have to learn

Thank you, I was able to do it with your assistance.

What is the relationship of .recvspace to RWIN? I can't get RWIN to the "recommended" value (trying to hit 64240) no matter what recvspace value I set

Some data from some trials: (recvspace as set by me, RWIN report from speedguide.net)

in all cases .sockthreshold is 0 and .sendspace is 64240:

32120, 33304
64240, 65160
63320, 63712
64000, 65160

Clearly below a certain value of .recvspace, RWIN goes to 63712, above that value it goes to 65160 (increment of 1448 which is my maximum useful data value - MSS is 1460). I want to set such that I end up with RWIN of 64240 which is an even multiple of 1460 - seems impossible.

Now that I think about it, these values are already multiples of 1448 - not multiples of 1460. Maybe Leopard is smarter than I am?

Comments? Thanks

I don't have a file named sysctl.conf in my /etc directory! Do I need to create that file, or do I need to change to my administrator login?

*You guys do, indeed, rock.*

I write for a living and am constantly going online to grab a fact or link to a referenced article. The constant dropping connections were driving me crazy and making me question my devotion to Apple. I had actually logged on, in fact, to pound out an "Apple, throw us a bone" email. I found your solution instead, and it looks like it's working. Fingers crossed.

I'm sure the guys over there in Cupertino have been sucking down coffee and staying up nights since the launch, looking for ways to pack solutions into an update. This looks like it will tide some of us over until then. One thing from a neophyte: Maybe you, Scott, or one of the other savvy people on this thread could -- for the rest of us -- type in a reply that says at the top "Okay, so here's where we sum up exactly what you need to do step-by-step." And then list underneath step #1, step #2, etc.

It's really there already, actually. But there seem to be some variations here, clarifications, etc. spread out between different postings. A fast, short summary of them all that's labeled as such would help a lot of us more nervous, terminal-wary folks relax even more easily.

Again, huge thanks.

This forum has been my first go-to stop for virtually every Mac problem I've had over the last 10 years (at least, I think it's been that long). And it rarely disappoints. Hugely appreciated.

JF

Update over here: Still having some problems, though much better after the RWIN settings. Also might be having the DNS issues. Tried the public ones listed in another post, then changed those to ones I found by logging onto our Livebox base station.

I also, in a fit of desperation, turned off our WPA and WEP... the Livebox automatically has MAC filtering. Hope that's enough. But it seems to improve things.

hey scott,
it works really good before but from yesterday each time that it asks me about my password i can write anything inside the terminal window and i could not enter any password

Just a further head's up for anybody still dealing with this... after doing all the stuff recommended above, and still having some slight connectivity problems, I also went ahead and turned off all WEP and WPA security on our wifi base station.

Ill advised? Perhaps.

But I've gotta tell ya', the connection is both stronger and more reliable, with zero dropouts, ever since. We have, now, only "associated device" MAC addressing as our only level of security. Knowing that this leaves the door open, we're opting for this instead of no connectivity at all.

If you're in an area where you're not worried about people tapping into your system or MAC-spoofing to get in, maybe this is something you'll want to try too. At least until any updates come out.

I must have an extremely fast internet connection then. I played around with the websites mentioned and also the settings that are discussed and I was at optimum before I changed anything.

My download speed is 9723kbps and upload is 970 kbps. These numbers were gotten from

http://www.speakeasy.net/speedtest/

What speed internet connect do you have?

Mine are:

Download Speed: 15458 kbps (1932.3 KB/sec transfer rate)
Upload Speed: 1828 kbps (228.5 KB/sec transfer rate)

With Leopard:

Down: 51620 kb/s
Up: 20140 kb/s

Leopard 10.5.1

9.394 Mbps
4.868 Mbps

Leopard 10.5.1 + Broadband Tuner

9.27 Mbps
4.867 Mbps

Leopard 10.5.1 + Broadband Tuner + net.inet.tcp.sockthreshold=0

26.429 Mbps
4.878 Mbps

This still isn't up to spec with Tiger, but it is as close as I can get it at the moment while I pray for an updated broadband tuner. Under Tiger I was getting 29-30 Mbps / 4.9-5.2 Mbps.

Of course running under Windows XP I'm getting over 30+ Down / About 5.5 Mbps Up almost every time.

I hope apple can come out with something that allows for the same performance I'm seeing under Windows XP, or at least on par with what I had in Tiger.

Message was edited by: ch0b1ts2600

Just thought I'd say, one *Nix geek to another, I'd recommend against recommending (as it were).

Over here:

http://www.apple.com/macosx/technology/unix.html

Apple talks about "Self-Tuning TCP". I'm not sure what they're up to but I did my usual tweaking with sysctl that I'd done on Tiger and something went Very Wrong.

I don't think I'd want to advise people to mess with sysctl. Not until somebody figures out what Leopard is up to.