InterceptRadio.com Forums

Linksys.
Seems to be 'dumping' its memory. By that I mean my netbook sees the router, but cannot bridge the gap to the innerweb. It sits behind a Vonage bridge/voip thing. Phone works while this problem occurs, so no problem with modem.
I end up having to reset router then running the set-up wizard to get back my security settings.
Anyone else have this issue?

_________________
</>

I run a couple of WRT54G's and never had a problem. So it totally loses its config and resets itself to factory defaults ? Or you have to nuke its config to make it work again ?

I reset it to default, then set it up again.
Seems to be working now, but it's happened twice in two weeks.
The first time I thought someone might have hacked it, but now I don't think that's the case.

_________________
</>

Only time I had a problem with my WRT54G was when I tried to use the :bsflag: one-touch set-up feature with my blackberry. It barfed and had to be reset.

_________________
Tim - KD7DEY

Put DD-WRT on it.

I'll have to read up on this.

_________________
</>

It's basically as simple as flashing new firmware. Settings will still be stored in NVRAM, but I've found DD-WRT to be much more reliable. Plus it's got a bunch of cool features.

Most recent WRT54G's lack the memory to run aftermarket firmware. Its usually better to use an older WRT54G (what is now called the WRT54GL). I run a WRT54GL with an aftermarket firmware called 'HyperWRT Thibor'. Its basically the stock firmware with some bugfixes, a few extra features, and the RF output power level setting is uncapped. Some people prefer Tomato over HyperWRT Thibor.

I found an article which discusses the WRT54G versions: http://en.wikipedia.org/wiki/Linksys_WRT54G_series

HyperWRT Thibor info:

http://heifner.blogspot.com/2006/09/10-steps-to-setup-wrt54gl-with-thibors.html

http://www.extremetech.com/article2/0,2845,1934579,00.asp

One more weird thing, I can't bring up 192.168.1.1 to tweak the settings. All I can do is network name, router p/w, & wpa key.
:?:

_________________
</>

You can't get to 192.168.1.1 at all or it just shows a couple of things?

The browser(s) hang. Doesn't load.
No biggie I guess. I might try the suggestions mentioned above.

_________________
</>

Start --> run --> cmd
Type ipconfig
See if your default gateway is still 192.168.1.1

Low and behold... now it comes up.
*Nevermind*
This thing's retarded.
Now I have to get Echolink to work properly.
Another issue altogether.

_________________
</>

So now I'm having an issue getting echolink to ping through UDP. Latest version says this bug was cured, but not for me.
Anyone Port Forward Echolink with this router?
I keep getting 'test failed' with echolinks router test.

_________________
</>

Big problem I see is that you are double natted. What ip is the Voip device giving your router? Double natting can work fine but more steps are involved...

_________________
"A well regulated breakfast, being necessary to the healthy start of the day, the right of the people to keep and eat food shall not be infringed."