Buffalo Router w/ DDWRT wont go out to the internet

McLovin

Golden Member
Jul 8, 2007
1,915
58
91
I have a BUFFALO WHR-HP-G54 with DDWRT installed based on recommendations from these forums and I am having an issue with it. The router seems to be able tos ee all my PCs on the local network and shows that it is resolving a WAN IP address from my modem but doesn't appear to be allowing anyone to get online. I've turned the SPI firewall off and verified Im not doing something st upid like blocking port 80 or anything but still no joy. If I watch the bandwidth monitors, like I said the local area seems to transmit data no problem but absolutely no information seems to be sent out to the WAN. Monitor seems to indicate info is coming in, albeit very little, and I can actually access my modem via its IP address.

If I hook any of my computers directly to my modem, the internet works just fine after modem reboot. Anyone think of anything else I can try? If this router is indeed bad I am assuming that Buffalo won't take it back with DDWRT installed on it so how do I go about putting the original firimware back on it so I can send it back for repair/replacement.
 

dshodson

Senior member
Nov 2, 2001
484
0
71
is your internet cable or dsl. i wouldnt be surprised if you have a modem setting which is the prb. i previously had cable and moved to a place with only dsl and the dsl modem needed to be adjusted to allow the buffalo router to function correctly.
 

McLovin

Golden Member
Jul 8, 2007
1,915
58
91
Modem is a cable modem. D-Link DCM-202 to be precise. Up until yesterday, Router worked just fine for the just around 2 months I've owned it.

I figured attempting a re-flash would also be in order.
 

kevnich2

Platinum Member
Apr 10, 2004
2,465
8
76
What is the WAN IP address it's receiving (not the whole thing just the first few numbers)? Also, have you tried pinging out for general internet troubleshooting? A ping will tell you where the packets aren't being transmitted to. Try pinging first your router, then the WAN IP of the router, then the gateway address that the router is receiving, then something like 4.2.2.1? ALso, when you hook up the router, are you restarting your computer or releasing/renewing the IP to get a new ip from the router rather than the cable modem?
 

dshodson

Senior member
Nov 2, 2001
484
0
71
if the system worked fine prior to flash then id do a hard reset. ill also say the first time i used ddwrt that it took a long time (from my perspective) for the router to actually boot up and start working and i wasnt being patient enough.
 

McLovin

Golden Member
Jul 8, 2007
1,915
58
91
I will let you guys know Iwhen I am at home I have to disconnect the router then hook up my modem, I hate this crap lol.

Anyway this is the info I pulled from the router the last time it was hooked up:

Connection Type
Automatic Configuration - DHCP
Login Status

Connection Uptime
0:01:36
IP Address
24.156.x.x
Subnet Mask
255.255.248.0
Gateway
24.156.x.x
DNS 1
24.121.x.x
DNS 2
24.121.x.x
DNS 3
207.192.x.x

When I pinged the Router IP, Modem IP, and WAN IP all send back packets. Once I ping the Gateway info stops being sent. I'm assuming this has something to do with my ISP then if theya re "giving me" that address?

I will say that I have had issues with the ISP/TV provider over the past few months with their signal being atrocious and dropping out constantly and now having complete outages every few hours. I also wanted to give you guys this extra info in case anyone can make sense of it.

System Event Log
Index Date/Time ID Level Text
2 09/12/09 16:45:37 R02.0 critical No Ranging Response received - T3 time-out
3 09/12/09 17:20:25 R04.0 critical Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
4 09/12/09 17:20:26 T01.0 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
5 09/12/09 17:20:45 R02.0 critical No Ranging Response received - T3 time-out
6 09/12/09 17:43:30 R04.0 critical Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
7 09/12/09 17:43:30 T01.0 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
8 09/13/09 08:29:44 R02.0 critical No Ranging Response received - T3 time-out
9 09/13/09 08:30:14 R04.0 critical Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
10 09/13/09 08:30:14 T01.0 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
11 09/13/09 08:30:32 T05.0 critical SYNC Timing Synchronization failure - Loss of Sync
12 09/13/09 08:30:33 T01.0 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
13 09/13/09 17:30:03 R04.0 critical Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
14 09/13/09 17:30:03 T01.0 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
15 09/13/09 17:36:29 R02.0 critical No Ranging Response received - T3 time-out
16 09/13/09 20:50:05 R04.0 critical Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
17 09/13/09 20:50:06 T01.0 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
18 09/13/09 21:00:53 R04.0 critical Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
19 09/13/09 21:00:53 T01.0 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
20 09/14/09 05:14:01 R02.0 critical No Ranging Response received - T3 time-out
21 09/14/09 06:39:43 E206.0 error Improper Configuration File CVC Format

pulled from my modem's event log and these ar emy signal levels at the time of posting:

Downstream Signal
Favorite Downstream Frequency: Hz
Frequency: 549000000 Hz
QAM Mode: 256 QAM
Channel Power: -7.8 dBmV
SNR: 33.350 dB

Upstream Signal
Channel Id: 3
Frequency: 30000000 Hz
Channel Width: 3200000 Hz
Channel Power: 38.5 dBmV

DOCSIS1.1 Quality of Service Parameters
Direction Upstream Upstream Downstream Downstream
SFID 0x5be4 0xf67 0x5bd7 0x7958
SID 0x1732 0xa90 N/A N/A
Traffic Priority 0 7 0 7
Max Sustained Traffic Rate (bps) 1000000 0 6000000 0
Max Transmit Burst (bytes) 3044 1768 3044 1768
Min Reserved Traffic Rate (bps) 0 0 0 0
Service Flow Scheduling Type Best Effort Best Effort N/A N/A
 

McLovin

Golden Member
Jul 8, 2007
1,915
58
91
Anyone else have any other suggestions? Im assuming since I can ping everything from my router to the modem but not the gateway, means that this is an ISP problem, correct?
 

kevnich2

Platinum Member
Apr 10, 2004
2,465
8
76
When you say you can ping your modem and your router, what exact IP's are you pinging?
 

McLovin

Golden Member
Jul 8, 2007
1,915
58
91
Originally posted by: dshodson
is the IP address of the modem within the range set by your router?

No, its fe default IP Adress that was set form the factory.

Originally posted by: kevnich2
When you say you can ping your modem and your router, what exact IP's are you pinging?

I am pinging the modem's default IP of 192.168.100.1


I was able to find my old crappy D-Link DI-524 router, plugged that bad boy in and voila! I now have interwebs! I am a little peeved that my buffalo router is now bad but oh well.

Anyone have any suggestions as to how I put the original firmware back on the router so I can send it back to buffalo? I really hate getting refurbed products so I am not even sure if sending it back would be worth the time, unless you guys have any other thoughts.

That D-Link DGL-4500 is looking better and better lol.
 

dman

Diamond Member
Nov 2, 1999
9,110
0
76
I had a similar problem with the newer v24 builds of DDWRT. I'm on DSL and using PPPoE though so not sure if it's exactly the same, but, it went away when I flashed back to an older / 'final' version of DDWRT.

Prior to that I had tried clearing out the settings and reflashing the firmware with a current version but that did NOT work.

YMMV.