oh.. to xaric, that DHCP error issue you receive, everyone does, but openwrt has already acknowledged this bug and says its fixed in the next release.. since they just released 1.0.3 RC2 a couple days ago, i may do a web upgrade later and that should fix it
until then, go to the administration section, network tab, DHCP to adjust DHCP settings until then
i need help ... realy help, and open-wrt isn´t help me at all !!!
i have flash my router with the back fire RC1, every was ok, but my problem is that i aciddental change the normal network to pppoe, and now i can´t connect to the router ! or do anything else ...
i tryed going to use the Failsafe mode, but i don´t kown if i am doing this right or not ...
i need help ... realy help, and open-wrt isn´t help me at all !!!
i have flash my router with the back fire RC1, every was ok, but my problem is that i aciddental change the normal network to pppoe, and now i can´t connect to the router ! or do anything else ...
i tryed going to use the Failsafe mode, but i don´t kown if i am doing this right or not ...
what should i do ?
I'd try a few things:
First step: Power-cycle the router.
If your router was on the default 192.168.11.X network, then try manually setting your IP address on your computer to 192.168.11.2, and try hitting 192.168.11.1 manually.
Worst case ... re-flash it. Every time you power-cycle it, it will allow TFTP connections to 192.168.11.1. Follow instructions earlier on this thread.
i need help ... realy help, and open-wrt isn´t help me at all !!!
i have flash my router with the back fire RC1, every was ok, but my problem is that i aciddental change the normal network to pppoe, and now i can´t connect to the router ! or do anything else ...
i tryed going to use the Failsafe mode, but i don´t kown if i am doing this right or not ...
what should i do ?
I'd try a few things:
First step: Power-cycle the router.
If your router was on the default 192.168.11.X network, then try manually setting your IP address on your computer to 192.168.11.2, and try hitting 192.168.11.1 manually.
Worst case ... re-flash it. Every time you power-cycle it, it will allow TFTP connections to 192.168.11.1. Follow instructions earlier on this thread.
look, i am in open-wrt, and its not 192.168.11.1, its 192.168.33.1 ....
but i am using a recovery metho, and i thing this is not briked LOL
i already use static on 192.168.1.1, and the router in recovery mode, so i think LOL
i ping it and it got respond ... so its alive LOL
the problem is that i change the router to pppoe, and to connect to a pc is dificult and i don´t kown how to do it LOL
i need help ... realy help, and open-wrt isn´t help me at all !!!
i have flash my router with the back fire RC1, every was ok, but my problem is that i aciddental change the normal network to pppoe, and now i can´t connect to the router ! or do anything else ...
i tryed going to use the Failsafe mode, but i don´t kown if i am doing this right or not ...
what should i do ?
I'd try a few things:
First step: Power-cycle the router.
If your router was on the default 192.168.11.X network, then try manually setting your IP address on your computer to 192.168.11.2, and try hitting 192.168.11.1 manually.
Worst case ... re-flash it. Every time you power-cycle it, it will allow TFTP connections to 192.168.11.1. Follow instructions earlier on this thread.
look, i am in open-wrt, and its not 192.168.11.1, its 192.168.33.1 ....
but i am using a recovery metho, and i thing this is not briked LOL
i already use static on 192.168.1.1, and the router in recovery mode, so i think LOL
i ping it and it got respond ... so its alive LOL
the problem is that i change the router to pppoe, and to connect to a pc is dificult and i don´t kown how to do it LOL
Change your static IP to 192.168.33.2 then try connecting to your router at 192.168.33.1 .... you cannot reach a 192.168.33.x address while using a 192.168.1.x IP ( unless you have a device which connects those 2 subnets AND you have the routes configured correctly to do so). When you connect to the router just change it back to DHCP and add any packages that you may wish to add.
My question to you is...if you are unable to connect to your router, how do you know it is currently using the 192.168.33.1 IP? Unless you are SURE of that IP ...you may want to try connecting to 192.168.11.100 and see if your router responds there.
tftp server(receive) go, waiting:4[sec]
Trying eth1
eth1 link down
FAIL
Trying eth0
eth0 is duplex
ag7100_check_link: _100BASET
Load address: 0x81f00000
TftpServer Timeout;
no file was loaded.
Trying eth0
eth0 is duplex
ag7100_check_link: _100BASET
Using eth0 device
TFTP from server 192.168.11.2; our IP address is 192.168.11.1
Filename 'firmware.ram'.
Load address: 0x81f00000
Loading: *
TFTP error: 'File not found' (1)
Starting again
Trying eth1
eth1 link down
FAIL
Trying eth0
eth0 is duplex
ag7100_check_link: _100BASET
Abort
but,I have no idea "how to Flash the origin Firmware"
Ping the router ,Request Timed Out (192.168.11.1)
Ping host(192.168.11.2) from router, Fine reply
These directions are for Win7 but Vista should work exactly the same. The trick is setting your IP static to 192.168.11.2 and adding a static ARP mapping 192.168.11.1 to to the mac address of your router. There is a very small window of time that the router accepts tftp connections so there isn't time to grab an IP via DHCP and do an ARP lookup. So setting all this to static gets you up and running before the router comes online.
I threw Open-WRT backfire 10.03-RC3 on, and it fixed all the menu problems.
OpenWRT is really starting to grow on me ...
The only outstanding problem(s) I have at the moment are:
1. I cannot get true 802.11n working, aka no speeds over 160Mbps. I've set it to run 40 MHz, tried all channels, played with no security, WEP, WPA2-PSK, etc., and nothing works. I have a Macbook with Airport that supports 802.11n. Hmmm ..
2. I periodically lose my wireless connection on my MacBook. Connection strength is fine, and then boom. Disappears for no apparent reason ... I am now monitoring system.log to see if I can find a reason.
The only outstanding annoyance with OpenWRT is anytime I make a change to the Wireless network (turn on WPA2, for example) it resets ALL networks, including the WAN, and I have to wait a minute or two until DHCP gets an IP address.
Since the message from Buffalo says there is no hardware change for WZR-HP-G300NH. I am curios to know what exactly caused this endless reboot problem?
What version of factory firmware do you guys have before flashing?
What version of the dd-wrt do you guys flash that cause the problem?
To me, both of my two wzr-hp-g300nh had no problem. I bought them on Amazon on Apr 2 and Apr 6. I flashed them immediately out-of-box.
What I noticed is the firmware on them is 1.72 and the dd-wrt firmware I am using is r14144 webflash.
I don't have problem to flash to dd-wrt (not like somebody mentioned there is problem to flash from 1.72 factory firmware)
Since the message from Buffalo says there is no hardware change for WZR-HP-G300NH. I am curios to know what exactly caused this endless reboot problem?
What I noticed is the firmware on them is 1.72 and the dd-wrt firmware I am using is r14144 webflash.
I don't have problem to flash to dd-wrt (not like somebody mentioned there is problem to flash from 1.72 factory firmware)
if you look here post #11 the moderator says there may be a hardware revision to accommodate dd-wrt. So what you are saying is you were able to upgrade from the factory 1.72 to dd-wrt using web-flash correct, please advise.
Since the message from Buffalo says there is no hardware change for WZR-HP-G300NH. I am curios to know what exactly caused this endless reboot problem?
What I noticed is the firmware on them is 1.72 and the dd-wrt firmware I am using is r14144 webflash.
I don't have problem to flash to dd-wrt (not like somebody mentioned there is problem to flash from 1.72 factory firmware)
if you look here post #11 the moderator says there may be a hardware revision to accommodate dd-wrt. So what you are saying is you were able to upgrade from the factory 1.72 to dd-wrt using web-flash correct, please advise.
Right, I am using webflash though the buffalo's Web UI. And it is the first thing I did when I turn on the router for the very first time.
If there is a slightly hardware change, I am still confused. If hardware is changed, which means the new hardware should support DD-WRT, and newer hardware will be able to flash to DD-WRT without problem, right? But from the users of dd-wrt forum, the older hardware can flash to DD-WRT without problem. While the ones I got can also flash to DD-WRT without problem. I assume mine are newer version if there is any change in hardware since mine come with 1.72 firmware and should be newly produced, unless I got refurbished product which is not likely from Amazon.
So that's why I suspect the combination of original firmware and destination dd-wrt firmware version could make some differences with this endless reboot issue.
I can confirm OpenWRT Backfire is working on my 'problematic' router. I don't really understand why this will work and DD-WRT will not, no matter what I try. OpenWRT refuses the webgui update version of DDWRT, I tried all the versions available attached to the japanese hardware version thread, not one does anything but give me the diag led for 15 seconds, then reboot. I've never really liked the GUI for OpenWRT. Anybody have any suggestions to get DD-WRT working on these routers that have issues with the initial flashing?
how do you tell which revision we have? the only info on the back is the sn# (left panel) and to the right is the SSID and key. just above the SSID(same label) is an A0 and A3.
The FCC ID is FDI-0910560-0
IC 6102A-021
can you check yours, if yours is the same I'll upgrade to the 1.72 and flash it again
how do you tell which revision we have? the only info on the back is the sn# (left panel) and to the right is the SSID and key. just above the SSID(same label) is an A0 and A3.
The FCC ID is FDI-0910560-0
IC 6102A-021
can you check yours, if yours is the same I'll upgrade to the 1.72 and flash it again
TIA
Although I don't suspect any change on those labels, I will check when I get home. Will post back then.