Wireless Router: The firmware un-fuck-up-ening *NOW WITH HOT JPEGS*

TL DR

I have a Linksys WRT54GS version 6 router that I recently attempted to change the software of as described here.

I eventually succeeded in changing the firmware, but now am unable to connect to the internet via wifi. What are some things I could be doing wrong? What info would be helpful for someone to help me troubleshoot?

Thanks a lot!

Zonkytonkman

are you able to connect to the router and see if it is ticking properly internally?

Lord Yod

You could try emailing/PMing the author of the firmware. 5 minutes of looking brought me to his profile on the forum for that site: http://www.bitsum.com/smf/index.php?action=profile;u=1

DrFrylock

Lord Yod wrote: »

You could try emailing/PMing the author of the firmware. 5 minutes of looking brought me to his profile on the forum for that site: http://www.bitsum.com/smf/index.php?action=profile;u=1

Uh, about a zillion people use DD-WRT and this guy didn't exactly write it, although he seems to maintain the page that describes how to get a micro-fied version of DD-WRT onto 2MB/VxWorks Linksys routers. It's probably a little early to be bugging the poor guy for a user issue.

Yes, connect to the router and check your settings. If it helps, post screenshots of each of the router status pages here and we'll check it out for you.

Lord Yod

Just going from what that page says:

This is a project started by Jeremy Collake (aka db90h) to flash a Vxworks based WRT54G/GS v5-v6 with third party linux firmware without the use of JTAG or serial cables. After considerable research and time, this has been accomplished!

I guess I should have said the guy that wrote that page.

Nibble

You probably need to reconfigure the wireless security settings on your router and/or your computer. Installing new firmware clears any settings you have changed.

TL DR

Here are the pics. I currently have wireless security disabled.

TL DR

BUMP so hard.

A life without wireless internet is a life not worth living!

yurnamehere

Could it possibly be choking on the fact that the SSID is all caps in your Windows configuration, but lower-case in the router setup?

DrFrylock

Why is the gateway on the first page set to 192.168.2.2? That's a little weird...

Ruckus

DrFrylock wrote: »

Why is the gateway on the first page set to 192.168.2.2? That's a little weird...

That is kind of weird.

OP, on the wireless client (notebook or whatever), run "ipconfig /all" from the command line and see what the gateway setting is. If the router's IP is 192.168.1.1 and the gateway on the client is set to 192.168.2.2, that is probably what's screwing you.

TL DR

My ipconfig/all. Thanks for the replies.

Windows IP Configuration

Host Name . . . . . . . . . . . . : toshiba-user
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : cinci.rr.com

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : cinci.rr.com
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Networ
k Connection
Physical Address. . . . . . . . . : 00-13-02-A0-16-04
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.107
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Saturday, December 15, 2007 8:53:42
PM
Lease Expires . . . . . . . . . . : Sunday, December 16, 2007 8:53:42 PM


Ethernet adapter Network Bridge:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : MAC Bridge Miniport
Physical Address. . . . . . . . . : 42-C7-90-41-EC-77
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.99
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1

Edit: What should the IP and gateway look like?

Doubleedit: I am able to get online through the router, just not wirelessly.

Ruckus

try "tracert 64.42.252.254"

TL DR

Wired:

Tracing route to h64-42-252-254.gtcust.grouptelecom.net [64.42.252.254]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 51 ms 10 ms 20 ms 10.52.128.1
3 17 ms 39 ms 20 ms gig2-2.cncnoh1-ybr1.cinci.rr.com [24.29.0.201]
4 76 ms 10 ms 10 ms srp13-0.mtgmoh1-rtr4.cinci.rr.com [24.29.0.175]

5 47 ms 22 ms 31 ms cpe-65-25-137-241.columbus.res.rr.com [65.25.137
.241]
6 207 ms 102 ms 203 ms te-3-2.car1.Cincinnati1.Level3.net [4.78.216.13]

7 39 ms 36 ms 36 ms ae-5-5.ebr2.Chicago1.Level3.net [4.69.132.206]
8 30 ms 42 ms 25 ms ae-21-54.car1.Chicago1.Level3.net [4.68.101.98]

9 31 ms 27 ms 27 ms dcr1-ge-2-0-0.chicago.savvis.net [208.175.10.1]

10 43 ms * 41 ms cr1-tengig-0-0-5-0.chicago.savvis.net [204.70.19
5.113]
11 106 ms 97 ms 108 ms cr2-pos-0-0-0-0.Seattle.savvis.net [204.70.193.5
7]
12 118 ms 117 ms 94 ms bpr4-so-0-0-0.SeattleSwitchDesign.savvis.net [20
8.172.83.65]
13 79 ms 96 ms 104 ms gt-group-telecom-services-corp.SeattleSwitchDesi
gn.savvis.net [208.173.50.74]
14 90 ms 91 ms 82 ms POS5-0.WANB-VANCBC.IP.GROUPTELECOM.NET [66.59.19
0.97]
15 99 ms 113 ms 99 ms POS6-0.WANB-CALGAB.IP.GROUPTELECOM.NET [66.59.19
0.197]
16 104 ms 115 ms 94 ms 216.18.32.6
17 101 ms 99 ms 102 ms GE4-1.WANB-CALGAB.IP.GROUPTELECOM.NET [216.18.32
.5]
18 109 ms 111 ms 110 ms h64-42-252-254.gtcust.grouptelecom.net [64.42.25
2.254]

Trace complete.

Wireless:
Request timed out

Can anyone think of any information I could provide to make problem diagnosis easier?

Ruckus

You can try changing that Gateway IP in the first pic you posted (in the earlier spoiler) to your router IP.

TL DR

Here's a copy of my ipconfig/all from before I switched the firmware.

Windows IP Configuration

Host Name . . . . . . . . . . . . : toshiba-user
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : cinci.rr.com

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : cinci.rr.com
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Connection
Physical Address. . . . . . . . . : 00-13-02-A0-16-04
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.100
Subnet Mask . . . . . . . . . . . : 255.255.255.128
Default Gateway . . . . . . . . . : 192.168.2.2
DHCP Server . . . . . . . . . . . : 192.168.2.2
DNS Servers . . . . . . . . . . . : 65.24.7.3
65.24.7.6
Lease Obtained. . . . . . . . . . : Friday, December 14, 2007 10:56:06 AM
Lease Expires . . . . . . . . . . : Saturday, December 15, 2007 10:56:06 AM

Ethernet adapter Network Bridge:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : MAC Bridge Miniport
Physical Address. . . . . . . . . : 42-C7-90-41-EC-77
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.90.62
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Ruckus

What ip address to you type in to connect to the router post-update?

necroSYS

Your computer's default gateway is 192.168.1.1

Your router's configured to use 192.168.2.2

Your router is handing out IP addresses on the 192.168.1.X network.

Do you not see a problem here?

TL DR

Anyone know a way to just nuke the router back to its old firmware?

I'm such a bigger noob than I realized when it comes to this kind of thing.

Barrakketh

Hurt and Burn wrote: »

Anyone know a way to just nuke the router back to its old firmware?

I'm such a bigger noob than I realized when it comes to this kind of thing.

Here's a hint that might make that unnecessary: The instructions that told you how to flash your router probably told you to manually configure your IP address in Windows. In fact, one of your screenshots from earlier showed that this was still the case. Check your wireless adapter's settings to see if they are still set that way. If so, change them back to automatic and try to connect to the wireless network again.

necroSYS

You can go to the firmware upload page and re-upload the backup you should have made of the original firmware.

If you didn't make a backup, you can probably get the firmware from Linksys' site.

necroSYS

Barrakketh wrote: »

Hurt and Burn wrote: »

Anyone know a way to just nuke the router back to its old firmware?

I'm such a bigger noob than I realized when it comes to this kind of thing.

Here's a hint that might make that unnecessary: The instructions that told you how to flash your router probably told you to manually configure your IP address in Windows. In fact, one of your screenshots from earlier showed that this was still the case. Check your wireless adapter's settings to see if they are still set that way. If so, change them back to automatic and try to connect to the wireless network again.

If they're already set to Automatic, then you can try:

ipconfig /release

ipconfig /renew

to see if it picks up the new settings.

necroSYS

But you need to either change your default gateway on the router to 1.1 or you need to change your assigned-IP range to 192.168.2.X

Or you need to change your subnet mask to 225.255.250.0 and then /release /renew

Barrakketh

See, in his most recent post he linked this image which shows that he doesn't have it set to automatic.

necroSYS

The IPconfig he posted showed DHCP and Autoconfig set to "Yes", so either that TCP/IP properties is to his wired connection (which is what I think), or there's something screwy with his computer.

Barrakketh

necroSYS wrote: »

The IPconfig he posted showed DHCP and Autoconfig set to "Yes", so either that TCP/IP properties is to his wired connection (which is what I think), or there's something screwy with his computer.

Oddly enough that is what the ipconfig output says for his wireless adapter (the description says "Intel(R) PRO/Wireless") and yet the TCP/IP properties page in the same shot shows it as manual. That is why I want him to check the properties page again and set it to automatic. Something is funny either way, and I don't believe it is the router's fault at this point in time.

TL DR

Bump. Been working the last few days with no time to un-destroy my router.

My IP is set to 192.168.2.100 and my default gateway is 192.168.2.2

I really appreciate the help so far, and I'll give my right ball (or cash equivalent) to the person or persons who get my apartment wireless again.

As of right now, I am unable to ping or otherwise access the router via firefox or command prompt, but I can connect to it as far as my "availablewireless networks" screen is concerned.

Lord Yod

necroSYS wrote: »

But you need to either change your default gateway on the router to 1.1 or you need to change your assigned-IP range to 192.168.2.X

Seems like this is the problem to me. Your default gateway IP doesn't match the router's IP.

TL DR

When I enable wireless connections, the list of networks includes both dd-wrt (my new firmware), AND Linksys (the old). Once I've connected to the router, Linksys dissapears. Attempts to connect to Linksys have proven fruitless.

When I am connected to the router, I am unable to access the control panel via 192.168.2.2

Both my IP address and default gateway are set to 192.168.2.2

Ruckus

Hurt and Burn wrote: »

When I enable wireless connections, the list of networks includes both dd-wrt (my new firmware), AND Linksys (the old). Once I've connected to the router, Linksys dissapears. Attempts to connect to Linksys have proven fruitless.

When I am connected to the router, I am unable to access the control panel via 192.168.2.2

Both my IP address and default gateway are set to 192.168.2.2

Uh, this sounds like somebody another network nearby, possibly on the same channel. Change your SSID to something unique, and move off channel 6.