Want a feedback please!!!

[voip123]

What firmware are you running on the WRT54GS?

I know it might be a pain, but did you try hooking things as described in my post? I'd be curious if that resolved your issue.

/c

Firmware version v7.50.2. I couldn't find any higher version anywhere.

[ctaranto]

Firmware version v7.50.2. I couldn't find any higher version anywhere.

Oh. The Linksys's firmware. I was curious if you were running dd-wrt or tomato. Have you considered dd-wrt?

I think someone else is going to hook things up the way I described in another thread. When he reports back (and if successful), maybe you can try the same.

/c

[Russell]

I started frustrating since day 5 after I signed up for the service. At least once per day the adapter doesn't work for around 15 minutes. Sometimes 2 or 3 times per day. It will back on.

I checked everyone's feed back. None of you is using the WRT54GS. Sounds like the router doesn't like its Linksys cousin - RT31P2.

At the moment, I am writing this post. The Line1 light is out.

Have you tried with the router next to your modem? Does that work fine? If yes, then you really can't fault VOIPo.

[ctaranto]

I'm guessing (and purely a guess) that coming in the LAN of the RT is different, either NAT, Firewall, or otherwise, than coming in through the WAN. Once in the LAN of the RT, going out the WAN is transparent. I am knowledgeable about networking, but by no means a pro. A side benefit of doing it this way is one can "manage" the RT through a normal IP address since it's on the same subnet.

My RT is running 1.25.00.

/c

[dteague]

I'm guessing (and purely a guess) that coming in the LAN of the RT is different, either NAT, Firewall, or otherwise, than coming in through the WAN. Once in the LAN of the RT, going out the WAN is transparent. I am knowledgeable about networking, but by no means a pro. A side benefit of doing it this way is one can "manage" the RT through a normal IP address since it's on the same subnet.

My RT is running 1.25.00.

I'll have to check and see what version my RT is running. I know both of the ones VoIPo sent me are running the same version and when I checked there was a later version of the firmware out there.

I'm able to manage my RT that is plugged into my WAN port today. I just go out to http://192.168.15.2:999 (or is it 4 9's?) and it brings up the login popup and then I'm in.

I'll let you know version and if I get it to work.

Since it is not an everyday thing for me, I may not notice if it doesn't fall off. If it works, even tho it is not "clean", I'd be able to live with it.

[ctaranto]

I was referring to being able to manage it without using port numbers. See? You can't even remember what the port was!.

Latest firmware for the RT is 1.30.07, dated (gasp) 12/20/06. The 1.25.00 firmware is from 2004 (December 1 to be exact). I asked VOIPo if I could upgrade. They said that they ship the routers with the support firmware level.

From work, I SSH (using autossh, and not port 22) into my WRT and set up a tunnel (one could also use the very excellent Tunnelier on Windows). I use proxy forwarding, using FoxyProxy to manage my FireFox connections (internal to work or external), and all external traffic is being tunneled to my home router, which then relays back all internet traffic. This way all external traffic, including DNS requests, is fully encrypted from prying eyes in IT (including IM messages). I've use wireshark to verify the traffic, and boy is it encrypted.

This also allows me to directly connect to my home routers/adapters/PC from work. I can monitor the status of the RT (and WRT) from the comfort of my office chair.

/c

[dteague]

From work, I SSH (using autossh, and not port 22) into my WRT and set up a tunnel (one could also use the very excellent Tunnelier on Windows). I use proxy forwarding, using FoxyProxy to manage my FireFox connections (internal to work or external), and all external traffic is being tunneled to my home router, which then relays back all internet traffic. This way all external traffic, including DNS requests, is fully encrypted from prying eyes in IT (including IM messages). I've use wireshark to verify the traffic, and boy is it encrypted.

This also allows me to directly connect to my home routers/adapters/PC from work. I can monitor the status of the RT (and WRT) from the comfort of my office chair.

Well, I can't tunnel back to my home computer from the office. Well, I could, but I would have to fire myself. I don't work in IT, but Security of the network falls under my control, and when I see people connecting to their network at home to bypass filters and such, they get marched to HR. There is too many things that people have access on here that we can't have either walking off, or a unsecured internet point coming in.

BUT, I know what you are saying.

[ctaranto]

There is too many things that people have access on here that we can't have either walking off, or a unsecured internet point coming in.

BUT, I know what you are saying.

I supposed, but it's no different that someone with a 32GB memory stick dumping everything on that and walking out. Nothing's more effective or stealth than sneaker-net.

I don't use it to bypass filtering. I'm tired of reauthing every 30 minutes since I run Linux of my laptop and not on a domain.

Anyways, back to topic. Let me know if you get around to changing the wiring and if it helps.

/c

[dteague]

My RT is running 1.25.00.

Firmware Version: 1.20.01, Oct 20 2004

This is the RT31P2 firmware that is on the box.

[ctaranto]

Firmware Version: 1.20.01, Oct 20 2004

This is the RT31P2 firmware that is on the box.

Interesting. Ask VOIPo to upgrade you to 1.25.00. Maybe that'll help?

/c