Wired Gaming Router to Wireless DD-WRT

[g0dM@n]

I can't take it anymore. My butt hurts from trying this for almost 3 hours and I think it's time to give up.

Here's what I have:
-D-Link Gaming Lounge Router, model DGL-4100
-Buffalo WHR-G125 Wireless Router with DD-WRT v24 firmware

Originally I used the DD-WRT as a stand-alone, but I recently got this D-Link router from the forums several weeks ago and want to take advantage of it since it might do better with hosting Xbox 360 games, and also has built-in gigabit (which I wanted anyway).

D-Link Router Setup:
WAN - Set to Autoconfiguration
LAN -
IP: 192.168.70.1
Subnet Mask: 255.255.255.0
Local Domain Name: <blank> (optional)
DHCP enabled

*I didn't know they could have no gateway field, but for the LAN there seems to be none*

DD-WRT Router Setup:
WAN - Changed from autoconfiguration to disabled
LAN -
IP: 192.168.70.2
Subnet Mask: 255.255.255.0
Gateway: <blank> (but also tried 192.168.70.1, which is primary router)
Local DNS: <blank> (but also tried 192.168.70.1, which is primary router)
DHCP Type: originally tried "disabled", but then tried DHCP Forwarder to 192.168.70.1, which is the primary router
Operating Mode: Originally "gateway", which didn't work, so I then set it to "router"


Physical Connection:
1. Modem ethernet > D-Link WAN port
2. D-Link LAN port > DD-WRT LAN port

Symptoms:
I can connect to the internet without a problem when connected to the D-Link (primary) router
When connected through wire to the DD-WRT (secondary) router I can ping the entire LAN on 192.168.70.x, but I CANNOT get out to the internet. I can ping the primary router and connect to it.


Here's what's REALLY WEIRD!!!
-When connected to the DD-WRT (secondary) router and trying to ping random websites, I get the IP address to the website, but no ping response!! I've never seen this before. I've seen where there's no name resolution but you can get out to the internet, but never get name resolution and no internet. I even tried a website I've NEVER visited before to ensure it wasn't something cached (don't know too much, but remember the term ARP cache).

Additional Info:
The STUPID thing is this... when I connect my laptop to the DD-WRT (secondary) router via cable (I haven't touched wireless yet!!), and use the IPCONFIG command, the default gateway always shows up as 0.0.0.0, and then under it I see the correct default gateway. As such:
IP: 192.168.70.111
Subnet Mask: 255.255.255.0
Gateway: 0.0.0.0
192.168.70.1

Even when I set up my IP static, and set up the default gateway to 192.168.70.1 it still shows up like that when I hit IPCONFIG in CMD.

http://i5.photobucket.com/albums/y176/godman114/gateway0.jpg


P.S. I remember last year using the WAN port and keeping each router on a separate network without problems, but I don't want that. I want everything under one network so that wireless laptops can see my wired file-server.

[g0dM@n]

Forgot to mention, I don't have crossover cables, but truly didn't think I'd need one.

[g0dM@n]

How about this. I'll give a free floppy cable to the person that finds me a solution!! :D

I'm still working on this. I wonder if I have to do something on the D-Link router's end??

[g0dM@n]

NEVERMIND!!! I REBOOTED EVERYTHING, AND MY LAPTOP AND IT'S NOW WORKING.

At this point I don't even care what fixed it. Thank God... I can rest in peace.

[Evilsizer]

well glad it got fixed and BTW since both are routers you wouldnt need a xover cable. since you would use the uplink port from one router to port 2 or 3 or 4, never use port 1. some how port 1 and uplink are tied in, so if you use the uplink port and port 1. at the same time that will cause connections issues for the router and puter on port 1.

[gangaskan]

least you got it taken care of :) good job godm@n :)

[g0dM@n]

well glad it got fixed and BTW since both are routers you wouldnt need a xover cable. since you would use the uplink port from one router to port 2 or 3 or 4, never use port 1. some how port 1 and uplink are tied in, so if you use the uplink port and port 1. at the same time that will cause connections issues for the router and puter on port 1.
These days almost all routers/switches have a built-in autolink feature, as well as NICs. I just wanted ppl to know I used a straight cable since I like to give all info. As far as uplink, it doesn't have to be uplink. You hook up any of the LAN ports from one router to any of the LAN ports on the other router, disable DHCP, disable the WAN on the secondary router (if it has that option), set the secondary router's router mode from "gateway" to "router" (if it has that option), and I think that should do it.

A cool feature that I did figure out was setting the secondary router's WAN port to a LAN port. There's a feature to do that in DD-WRT on the basic setup where it says something like "set WAN port to switch", and then on top of that you have to go to the VLAN section, click on the "W" port and on the right you hit a drop down and set it to LAN.

I'm so happy. I was never able to figure out how to set up 2 routers on the SAME subnet/network. Now all wireless machines can see my network. Usually, 2 routers end up on separate networks and even though both can hit the internet, they can't always see each other.

Lesson learned.

least you got it taken care of :) good job godm@n :)

Thanks, bro. I hate that I spent so much time on it, but when I've got my mind set on something I hate to give up. I did a ton of reading yesterday and learned more than just my lesson. :)