View Full Version : DD-WRT Issues
Ok so I have a Linksys WRT54G Ver.6 at home that I wanted to install DD-WRT on. I did a lot of research and after figuring out that I needed the micro version, I found some instructions online because the upgrade wasn't working.
The instructions told me to do a few different things first. I upgraded to something called vxworks_prep_v03.bin first, then I waited a while, then upgraded to vxworks_killer_g_v06.bin. Finally I waited for my router to reboot and used TFTP to upgrade to dd-wrt.v23_sp2_micro_generic.bin. This works and now I have DD-WRT running on my router fine and I can log into it via the web interface and everything. My problem, however, is that it won't get an IP address from my ISP. After the upgrade, if I reboot my modem and plug it directly into my PC, I can access the internet fine. If I reboot it and plug it into the router running DD-WRT though, I can't access the internet. Does anyone know if I did anything wrong in the process or if there is a fix for this? I really like DD-WRT and want to keep it on my router but if I have to go back to the regular linksys firmware I will.
xeon711
02-03-2008, 11:13 PM
http://www.dd-wrt.com ?
http://www.dd-wrt.com ?
Obviously thats not very helpful. I already got DD-WRT from that site. Could someone with at least half a brain give me a hand?
YeOldeStonecat
02-04-2008, 07:12 AM
Did this wrt54g obtain an IP when running stock Linky firmware? So we know if it's functional with a good WAN port?
munkle
02-04-2008, 08:45 AM
If you have comcast you have to disable stp under the wan connection type. I don't know why all I know is that it causes problems if you have it enable with comcast internet.
Did this wrt54g obtain an IP when running stock Linky firmware? So we know if it's functional with a good WAN port?
Yes, did you make sure the wan port worked before? My wan port died during a power outage. If it is the wan port you can reassign one of the lan ports to be the wan port.
Yeah it worked fine before I tried putting DD-WRT on it. I don't have Comcast i have Time Warner, but I also tried disabling that option just in case, and it still didn't have any effect. Also, I've tried going back to the Linksys firmware, but now I just get upgrade failed when I try to upload the image.
munkle
02-04-2008, 09:58 AM
Yeah it worked fine before I tried putting DD-WRT on it. I don't have Comcast i have Time Warner, but I also tried disabling that option just in case, and it still didn't have any effect. Also, I've tried going back to the Linksys firmware, but now I just get upgrade failed when I try to upload the image.
You want to follow these instructions when flashing to dd-wrt for a version 6 and flashing back to the stock linksys firmware. (http://www.bitsum.com/openwiking/owbase/ow.asp?WRT54G5_CFE) You could also try setting the mac address of the router to the mac of your pc (resetting both the modem and router after you set the mac), also you do have dhcp enable under wan connection type?
You want to follow these instructions when flashing to dd-wrt for a version 6 and flashing back to the stock linksys firmware. (http://www.bitsum.com/openwiking/owbase/ow.asp?WRT54G5_CFE) You could also try setting the mac address of the router to the mac of your pc (resetting both the modem and router after you set the mac), also you do have dhcp enable under wan connection type?
I followed those exact instructions when trying to put DD-WRT on my router in the first place, I will see if I can revert back to the Linksys firmware now. I do have DHCP enabled, because my ISP did not give me a static IP I don't think. What would setting the MAC of the router to the MAC of my PC accomplish? Wouldn't that just cause some kind of error? I may try that but I want to know what it will do first.
YeOldeStonecat
02-04-2008, 10:04 AM
Shouldn't need MAC cloning...proper way to change devices on cable modems is to power off the modem for several minutes, it will "forget" the MAC of the prior device..and learn the MAC of whatever it's powered up to next.
Also...since his Linksys worked with Linky firmware...the modem already knew the MAC of the Linksys....unless he did the bandaid fix of MAC cloning before under the Linky firmware and just forgot he did that.
munkle
02-04-2008, 10:07 AM
I followed those exact instructions when trying to put DD-WRT on my router in the first place, I will see if I can revert back to the Linksys firmware now. I do have DHCP enabled, because my ISP did not give me a static IP I don't think. What would setting the MAC of the router to the MAC of my PC accomplish? Wouldn't that just cause some kind of error? I may try that but I want to know what it will do first.
It just makes the modem think it is connecting to your pc instead of the router. It wont cause any problems (that I have ever seen). I had a problem with comcast for about a week with my dd-wrt router having the generic dd-wrt mac address (setting the mac to my pc mac fixed it), the problem went away when they did maintenance and I could use the generic dd-wrt mac again.
Shouldn't need MAC cloning...proper way to change devices on cable modems is to power off the modem for several minutes, it will "forget" the MAC of the prior device..and learn the MAC of whatever it's powered up to next.
Also...since his Linksys worked with Linky firmware...the modem already knew the MAC of the Linksys....unless he did the bandaid fix of MAC cloning before under the Linky firmware and just forgot he did that.
I didn't do anything with the MAC address before upgrading the firmware, I did however unplug the modem, wait several minutes, then plug it back in so that it recognized the router.
I don't really know if this supplies any more information than what I already have said, but when I plug the modem into the router, I get the 'Recieve' light on the modem flashing, but not the 'Send' light.
munkle
02-04-2008, 10:09 AM
Shouldn't need MAC cloning...proper way to change devices on cable modems is to power off the modem for several minutes, it will "forget" the MAC of the prior device..and learn the MAC of whatever it's powered up to next.
Also...since his Linksys worked with Linky firmware...the modem already knew the MAC of the Linksys....unless he did the bandaid fix of MAC cloning before under the Linky firmware and just forgot he did that.
Sometimes cloning the mac can help, we all know that rebooting the modem clears the mac that it was connected too. But when that still isn't working, cloning the mac may may help. When you flash dd-wrt on the linksys it removes the mac the linksys router had and gives it a generic dd-wrt mac. 00:40:10:10:00:02 is the wan mac dd-wrt gives.
YAY that worked perfectly!! Thanks a lot for all the help guys. Do I have to keep this setting forever? When is it safe to put the generic IP that DD-WRT gave my router back? Are there any safety percausions I should know before I decide to make this my final config on the router?
munkle
02-04-2008, 10:18 AM
YAY that worked perfectly!! Thanks a lot for all the help guys. Do I have to keep this setting forever? When is it safe to put the generic IP that DD-WRT gave my router back? Are there any safety percausions I should know before I decide to make this my final config on the router?
You don't have to keep anything permanently. But if the generic mac still wont connect to the modem even after you reset both then changing back to the generic mac just will cause it not to work again. There are no problems cloning the mac on the router that you should worry about, the only thing it changes is what the modem thinks its connecting to, which would be your pc. The mac address is just a device identification number really.
I think the problem comes from all the people using dd-wrt with the generic mac address it gives. Maybe isp don't like all the routers with the same macs on their system, or it causes problems.
YeOldeStonecat
02-04-2008, 10:19 AM
Sometimes cloning the mac can help, we all know that rebooting the modem clears the mac that it was connected too. But when that still isn't working, cloning the mac may may help. .
Never had to....out of many many cable installs at clients, and replacing routers, and even on days at home when I'd change devices several times a day as I fiddled around with new routers of linux distro routers or ISA or whatever I felt like changing in my home network.
Power off cable modem for several minutes.
Plug new device into it...power up new device...
Power up cable modem..initially it will give the new device a non-legit IP such as 192.168.100.100 such as you get if your cable is down....but once it synchs up..and memorizes the new MAC..it will release a legit public IP upon the next request of the device...so...
Power cycle your new device/router...it will then get a public IP. A lot of people give up just before this step..thus their frustration.
Reboot PCs...or..release/renew..since prior to this step..they dot not have good DNS information yet. A lot of people give up before this easy step too.
Cloning isn't a problem..just such a bandaid fix..why not flush and set things correctly in the first place IMO.
Never had to....out of many many cable installs at clients, and replacing routers, and even on days at home when I'd change devices several times a day as I fiddled around with new routers of linux distro routers or ISA or whatever I felt like changing in my home network.
Power off cable modem for several minutes.
Plug new device into it...power up new device...
Power up cable modem..initially it will give the new device a non-legit IP such as 192.168.100.100 such as you get if your cable is down....but once it synchs up..and memorizes the new MAC..it will release a legit public IP upon the next request of the device...so...
Power cycle your new device/router...it will then get a public IP. A lot of people give up just before this step..thus their frustration.
Reboot PCs...or..release/renew..since prior to this step..they dot not have good DNS information yet. A lot of people give up before this easy step too.
Cloning isn't a problem..just such a bandaid fix..why not flush and set things correctly in the first place IMO.
I've tried doing what you suggest, and it still didn't work, I'll stick with the cloning for now. One problem I am still having though is that I cannot join the wireless network. I can see it from my wireless laptop, it says the correct kind of security I am running on it, but it just won't connect to the network for some reason.
munkle
02-04-2008, 10:25 AM
Never had to....out of many many cable installs at clients, and replacing routers, and even on days at home when I'd change devices several times a day as I fiddled around with new routers of linux distro routers or ISA or whatever I felt like changing in my home network.
Power off cable modem for several minutes.
Plug new device into it...power up new device...
Power up cable modem..initially it will give the new device a non-legit IP such as 192.168.100.100 such as you get if your cable is down....but once it synchs up..and memorizes the new MAC..it will release a legit public IP upon the next request of the device...so...
Power cycle your new device/router...it will then get a public IP. A lot of people give up just before this step..thus their frustration.
Reboot PCs...or..release/renew..since prior to this step..they dot not have good DNS information yet. A lot of people give up before this easy step too.
Cloning isn't a problem..just such a bandaid fix..why not flush and set things correctly in the first place IMO.
You seem to think that will fix all the problems with mac address's as you can see from this thread I posted that I had a problem that this wouldn't fix and the op just said that didn't work for them. When you limit yourself to only one fix for a problem then you limit how successful you are at fixing that problem. It is not a bandaid fix if it works and doing everything else doesn't work.
As I said before I think it is a problem with many routers using the same generic mac. 00:40:10:10:00:02
munkle
02-04-2008, 10:30 AM
I've tried doing what you suggest, and it still didn't work, I'll stick with the cloning for now. One problem I am still having though is that I cannot join the wireless network. I can see it from my wireless laptop, it says the correct kind of security I am running on it, but it just won't connect to the network for some reason.
Try turning off the security to see if you can connect to it then. Then turn on the security, if you can connect to without security but not with, make sure you have all the updates for your system and wireless drivers. The newer wireless securities (wpa, wpa2) often aren't included in older drivers (and windows xp without updates).
Ok I got the wireless working fine now, so everything seems to be up and running great. Still slightly worried about the Mac Address Cloning, I've just never heard anything about it and I am a wuss when it comes to trying things I haven't heard of. Thanks for all the helpful advice guys.
munkle
02-04-2008, 10:33 AM
Ok I got the wireless working fine now, so everything seems to be up and running great. Still slightly worried about the Mac Address Cloning, I've just never heard anything about it and I am a wuss when it comes to trying things I haven't heard of. Thanks for all the helpful advice guys.
There's nothing to worry about. In simple terms it just changes the devices name. So the modem thinks it is talking to joe (who is really bob).
vBulletin® v3.8.2, Copyright ©2000-2010, Jelsoft Enterprises Ltd.