Print

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

[anuaimi]

Today I switched ISPs and the new ISP gave me a static IP in the range of 172.16.xxx.xxx.  Unfortuately, the DIR-655 would not route packets with this IP.  When I switched a spare Belkin router, things worked properly.  Note, the ISP

Is there a way to have the DIR-655 work with an external IP in the range of 172.16.xxx.xxx?  I love my DIR-655 and would have to go to something else.

Athir
Toronto, Canada

[Clancy]

Athir, my ISP dynamically assigns my IP address but it is in a range similar to yours: 173.74.xxx.xxx. I am a little puzzled when you say "range". To me, a static IP address has no range. It is exactly what they tell you it is. Are you saying that you can pick your address based on the IP address numbers you've given? I'm certain that there must be something missing from this equation. Can you give us more information, such as what kind of connection you have? Cable, DSL, 2800 Baud modem?

EDIT: OK, dumb questions. After reading between the lines I think I understand what you are saying. Could you fill us in on what type of connection you have? My guess would be cable with a Samsung cable modem, perhaps?

EDIT EDIT: Have you copied your Belkin router's connection settings?

[anuaimi]

The issue is that 172.16.xxx.xxx is a non-routable range.  It's the same as 192.168.xxx.xxxx or 10.10.xxx.xxx.  That means that if a packet from the internal interface is sent to the WAN interface, the router should not route that .  The exception is if the WAN interface is set to an IP in this range.  the DIR-655 does not handle this while other routers do.   I believe this is a bug with the Dlink firmware.

AThir

[lizzi555]

The DIR will also route private IP addresses.
Routers in the internet won't.



Consider checking subnet mask and gateway again, most providers are not using class c subnets for this kind of connection, my cable provider is using 255.255.252.0 for example.

[jdrom]

It's also possible that the modem has a built-in "router" of sorts, thus why it's giving a private address to the DIR-655.

If you connect your computer directly to the modem, you should be able to access the web config on it and set the modem into bridging mode so that the DIR655 will make the connection.

[anuaimi]

Interesting to hear that the DIR-655 will route 192.168.xxx.xxx addresses.   Yet, I can't seem to get this to work with 172.16.xxx.xxx.   As mentioned, I replaced with the DLink iwht a belkin and it worked.   So there is clearly an issue with the Dlink.   

Is there anyone from Dlink support on this forum that could find out for sure if the Dlink will allow a WAN address in the 172.16.xxx.xxx range?

[Fatman]

Techs here test against a WAN on the 172.16.0.0/16 every day.  Your issue is going to be most likely with the fact that you have double NAT going on.

[smlunatick]

Interesting to hear that the DIR-655 will route 192.168.xxx.xxx addresses.   Yet, I can't seem to get this to work with 172.16.xxx.xxx.   As mentioned, I replaced with the DLink iwht a belkin and it worked.   So there is clearly an issue with the Dlink.   

Is there anyone from Dlink support on this forum that could find out for sure if the Dlink will allow a WAN address in the 172.16.xxx.xxx range?

The reason why the DIR router "may" route an 192.168.xxx.xxx is that the Internet broadband modem is "also" a router.  I have a SpeadStream 4200 for my service.  I can configure my DIR router to access the modem via 192.168.2.1 or via the PPPoE access.