Uh oh, having trouble with the TFTP flashing procedure for the Buffalo...

[jdc]

ok, well mine works fine, so i wont touch it

[PeterB]

matt, I just tried manually setting that IP. Didn't make any difference...

I just hope I didn't hose this router...

[GGD]

> I just hope I didn't hose this router...

It's very unlikely that you hosed it, since it didn't even acknowledge any of the TFTP packets.

Just try power cycling it and connecting to the Buffalo web configuration page 192.168.11.1, that will confirm that it's alive and that you have TCP/IP setup correctly on your Mac

Once you get that working, try the TFTP again after pressing/releasing the reset button.

BTW: for that buffalo router you don't need to use the "mini" version first, you can go straight to the "standard" version of DD-WRT.

[PeterB]

Uh oh... 192.168.11.1 in a web browser doesn't get me anything...

[mattkime]

>>Uh oh... 192.168.11.1 in a web browser doesn't get me anything...

Do you have your TCP/IP settings set to DHCP

OR

The TCP/IP settings when updating the router. (Necessary!)

IP: 192.168.1.2
Subnet: 255.255.255.0
Router: (blank)

[GGD]

[quote PeterB]Uh oh... 192.168.11.1 in a web browser doesn't get me anything...
Look at your Network settings, are you set to DHCP? Are you disconnected from all other LANs except for that Buffalo Router? Put the Mac to sleep and wake it up to make sure it tries to get an IP address from the router using DHCP.

[PeterB]

Ah, whew, this is a relief... I am able to connect to it via wireless, so there must be some problem with the wired connection either physically or in my setup in the Network control panel... hmmmm, will have to check...

[GGD]

[quote mattkime]>>Uh oh... 192.168.11.1 in a web browser doesn't get me anything...

Do you have your TCP/IP settings set to DHCP

OR

The TCP/IP settings when updating the router. (Necessary!)

IP: 192.168.1.2
Subnet: 255.255.255.0
Router: (blank)
Once again, those setting are incorrect for the Buffalo FW, and if you use those settings you will get the exact behavior that PeterB is seeing.

The Buffalo FW uses 192.168.11.1 as the router address and you should use an IP address in that subnet if you're not using DHCP.

Best bet is to get Ethernet to work with DHCP, that's probably how Airport is configured and why it's working.

[Psurfer]

Try a different browser. Yesterday I found Firefox worked to access a networked printer via its router #, where Safari went nowhere.

[PeterB]

OK, now I feel REALLY stupid...

I just got it all to work. The problem was that I had connected the enet cable to the WAN port rather than one of the regular ones... d'oh!

Revised wrt firmware now installed, now am trying to connect to firmware-updated router via ethernet... so far, no luck... I wonder if it's my hub that's the problem...