Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Briandr]

Hi,

I got two DIR-655's. One is from generation 'B' and the other generation 'C'.  Both have the latest firmware versions. The 'B' router is connected to a Ubee modem via its WAN port. My ISP is Comcast and those guys give me a DHCP WAN IP Address. DHCP is not enabled on the 'B' router. I have about 20 devices and my own preference is to statically assign the IP's. Not the preferred method of most people, but that is how I do it. The 'C' router is essentially a backup (glorified AP) to the 'B' router, but it has its own SSID and provides additional coverage where needed. As you might imagine no DHCP on this router. Just the bare minimum to get it to function as an AP. To connect the two I am going from LAN port 2 on 'B' to LAN port 2 on 'C'. I don't use 192.168.0.x for my home network. As I statically assign devices I got sick of having to type in that for a long IP address. So I use 10.0.0.x instead at my home. The problem is the 'C' router cannot ping (from within the web console) google.com or yahoo.com by IP or by DNS name. The two routers can ping each other and other statically assigned devices on my home network. What tipped me off to a possible problem on the 'C' router is that was not updating its time from the DLink NTP time server. DLink tech support thinks this might have something to do with mixing and matching the 'C' and 'B' routers, but I am not sure if the guy I talked to is reaching for straws. Their tech support people were well quite (insert own comment here). Did I provide enough info or too much info that is not relevant? Please let me know as I would like to fix this annoying issue. Thanks.

[FurryNutz]

Link>Welcome!

If your trying to use the routers ping function in this configuration, it will fail due to the fact that your not using the WAN port on the Rev C router. WAN port features on any router that are tied to the WAN port will not be usable when using these routers in LAN to LAN AP mode. This will included the NTP time feature as well.

[Briandr]

After a marathon call with DLink tech support including one of their advanced engineers I wanted to post here. To directly address your comment. I was plugged into the WAN port on the 'C'  router and the earth globe on the front was blinking orange every few seconds. While in that current configuration it was failing to reach the internet (ping by name/IP or the NTP time server would not update). So WAN or LAN port on the 'C' router = failure in either configuration. Hope you can help me out FurryNutz.  I should mention the ultimate long term end goal is to have 1 ISP on 2 separate subnets/vlans. So the intent right now is to start slow, but if we can kill two birds with one stone I am up for that. Thanks.

[FurryNutz]

If you leave the Rev C router in LAN to LAN AP mode and manually set the time, you'll be find there. Honestly the time isn't really needed on a AP mode router as it's mostly acting as a pass thru for network traffic and most of your filtering and scheduling should be handling by the primary main host router which should be connected to the ISP modem on it's WAN port. The Rev C will just let traffic pass thru on it's open LAN ports and the wifi. All other features should be disabled on the Rev C.

The only problem would be if you have the Rev C connected to the Rev B via its WAN port, then you would need to make sure that the Rev C routers default router IP address should not be the same. Default IP addresses for DIR routers are 192.168.0.1 and if you connect another then this conflicts with the 1st router when connected, change the 2nd router to 192.168.1.1 or 2.1...In your case make sure the 10.0.0.# addresses differ on the Rev C routers IP address and disable DHCP server on it. However I recommend running it as a LAN to LAN AP as you have it configured. Manually set the time if you really need to and do any pings from the main host router, not the AP. Time isn't really needed on the AP unless your scheduling times when the wifi is disabled and enabled.