Re: Connection stalls until I do ping/traceroute in router

On Fri, 28 Mar 2008 02:16:15 -0700 (PDT), sdaws <sdaws06@xxxxxxxxx>
wrote:

Old version of the firmware. The current version for the v2.2 router
is 4.21.1. See:
<http://www.linksys.com/servlet/Satellite?c=L_CASupport_C2&childpagena...>
Download and install please.

Did you install the latest firmware?

I did try to find out where
the connection was failing but it seems to switch around (either I
can't get to the router, or I can't get past it - maybe diff probs/
reasons) but mostly almost nothing works, or everything works - and
what makes things work changes each time (but usually bringing up the
traceroute/ping panel is one of the more likely things to fix it -

Huh? What "panel"? Are you bringing up the diagnostic page in the
Linksys WRT54G router? If so, that's NOT where you run ping. See my
previous instructions.

note that it never fails somewhere along the trace - either I can't
trace/ping at all, or trace works all the way to the destination -

Please do NOT use traceroute (err... tracert) for troubleshooting at
this time. Just use ping. Keep it simple.

somewhere just before the trace starts or part way during the trace,
everything else starts working again). Sometimes ipconfig /release & /
renew works (either to get to the router if I couldn't before; or to
get to the rest of the 'net).

OK, let's really get down to basics. When it fails, can you ping the
router IP address? If you can't do that, then there's something wrong
with the wireless connection between you and the router. It might be
the ancient router firmware, interference from the neighbors,
defective laptop(s), driver issues on the laptop(s), or aliens from
outer space trying to communicate on the same channels. You *MAY*
have other problems, but solve this one first or it will mask out the
others. Update the firmware. Reset the router to defaults and put
all the settings back manually (to avoid trash saved in the config
file). Try different RF channels (1, 6, or 11). Move the router away
from windows to avoid RF interference from outside. Play with
directional antennas to keep the RF inside the house. Use Netstumbler
to check coverage around the house.

Here's what happened earlier tonight (this time with my newer notebook
which has never previously had these types of issues)...

- notebook was on, (wireless) net connection working fine
- left for a while, came back (only screen was in powersave mode)
- 'net not working, nothing would fix it (couldn't get to router)
- unplugged router and modem; plugged both back in
- now could access router (192.168.1.1) but nothing past that
- went to Status page; tried DHCP release & renew (still broken)
- went to diagnostic page; clicked traceroute button -> as window
comes up, everything starts working again

I have a few guesses but first please update the firmware. I'm not
interested in troubleshooting ancient firmware versions.

Did you turn off the power management on the wireless client (as
someone else suggested)? Having the card power down (to save power)
when it goes into standby will cause a disconnect. That's normally
not a problem, but your ancient firmware is having a bad day trying to
reconnect.

Note that the sequence you itemized above, will also recover if you
just ping the router. Use:
ping -t 192.168.1.1
which will ping once per second until interrupted. All you need is
some traffic, any traffic, to kick start the wireless connection.

Here are the details you requested...

- DSL (AT&T/Yahoo) [I live near you, btw - our cities have the same
first word :)]

Running NSLOOKUP on your IP, I get:
adsl-99-167-102-95.dsl.pltn13.sbcglobal.net
which is Pleasanton. Well, you could be anywhere in the SF or
Monterey Bay area. Santa Rosa? Santa Claus? It's 5AM and I'm too
sleepy to think.

- older notebook (Dell Insp 8200, XP, AirLink+ usb adapter)
- newer notebook (Dell Insp1521, Vista, Dell builtin wireless)
- you have the router details; anything else?

What manner of encryption are you using? WPA-PSK-TKIP, WPA2-PSK-AES,
WEP, or none? Do you have a unique SSID setup so that your clients
don't jump to the neighbors wireless?

What model DSL modem? If 5100 or 4200, do you have it set for NAT or
bridging? If NAT, do you have a timeout setup on the DSL modem? More
specifically, in which box did you setup the PBI/SBC/AT&T/Yahoo login
and password? (DSL modem or WRT54G).

I've been hesitant to do a firmware upgrade because I've heard some
people have had more problems after doing that (and it can't be backed
out?) so only do it if you KNOW that the upgrade fixes a problem you
have. But since I AM having issues w/ the router, I'll go ahead and
do it.

Baloney. There have been problems going to alternative firmware.
However, it's fairly difficult to screw up the stock firmware updates.
Worst case, you get to learn how to use TFTP to recover the router.
Anyway, you can't possibly have more problems than you're currently
experiencing.

My guess(tm) is that you have multiple problems and that this mess
will need to be solved one link at a time. Start with the wireless
connection between you and the wireless router. Then, we'll pound on
the PBI/SBC/AT&T/Yahoo connection.

--
Jeff Liebermann jeffl@xxxxxxxxxx
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
.