Print

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

[DLinkUserDude]

DGL-4500 w/1.02 Official Release Firmware
Ambit Cable Modem Model 60687EU

First problem:  Internet connectivity is lost on client PCs.

All the client PCs are connectied via wired, 2 of the clients PCs also are connected wirelessly (at times) and wireless is enabled (mixed NG mode, 2.4Ghz, Channel 6, WPA2 only, AES, Auto 20/40 bandwidth..)

Most of the time, the 4500 is still accessible, and rebooting via the Tools/System option restores internet connectivity.  Occasionally, the 4500 is not accessible at all, and has to be manually reset via a power plug pull/push.

Today, for example, internet connectivity was lost approximately every 20-60 minutes - it differed in each interval.  But its been happening pretty much all day long.

Also, some PCs lose internet connectivity at times, but not others, yet internet access is restored to all PCs when the 4500 is rebooted.

I've changed pretty much everything in the wireless settings (aside from disabling wireless completely), and the loss of internet connectivity/4500 access still occurs (no set interval or usage pattern that i can detect).

Interestingly, the 4500 worked near flawlessly for the first few weeks in use (I've had it since late February), but, in the last few weeks, its become more and more problematic (losing internet connectivity).

Second Problem:  Cant access Cable Modem configuration pages most of the time.

Having problems accessing the config pages of the cable modem at 192.168.100.1.  95% of the time or so, the pages wont open, and ping'ing the cable modem fails with request time outs.  Every once in a blue moon, the pages will open, and  pinging works fine.  No changes are made to the configuration of the 4500 when access is possible - one minute the pages will open fine, the next minute, no access.

Access worked fine with a DI-624 prior to the DGL-4500.  Access works fine when the 4500 is temporarily removed and the PC is directly connected to the cable modem.

Something is clearly off with the routing code.

And then theres the log entries (heres an example):

[INFO] Thu Apr 17 17:22:22 2008 Blocked incoming TCP packet from 192.168.100.1:80 to 98.24.xx.xx:4975 as RST:ACK received but there is no active connection
[INFO] Thu Apr 17 17:21:56 2008 Blocked incoming TCP packet from 192.168.100.1:80 to 98.24.xx.xx:2061 as SYN:ACK received but there is no active connection
[INFO] Thu Apr 17 17:21:18 2008 Blocked incoming TCP packet from 192.168.100.1:80 to 98.24.xx.xx:4975 as SYN:ACK received but there is no active connection
[INFO] Thu Apr 17 17:20:52 2008 Blocked incoming TCP packet from 192.168.100.1:80 to 98.24.xx.xx:2061 as SYN:ACK received but there is no active connection
[INFO] Thu Apr 17 17:20:35 2008 Blocked incoming TCP packet from 192.168.100.1:80 to 98.24.xx.xx:4287 as RST:ACK received but there is no active connection

Looks like the firewall is blocking the return TCP packets because, to its logic "there is no active connection".  Interesting, considering the connection originated from the PC, and, indeed didnt seem to be completed, because, golly, perhaps the firewall is blocking the return packets for some reason.

The 4500 is configured with minimal settings, most of the Advanced functionality is disabled:

There are 3 Remote Desktop virtual server forwarding entries
No special applications configured
Gaming modeis  disabled
Gamefuel is disabled
No extra routing configured
Access control is disabled
Web filtering is disabled
MAC Address Filtering is disabled
Firewall:  SPI is enabled
             UDP and TCP are configured for Endpoint Independent
             Anti-Spoofing is enabled
             All 4 ALGs are enabled
Inbound Filters disabled
Advanced Wireless has default settings, all checkboxes unchecked
WISH is disabled
WiFi Protected Setup is disabled
Advanced Network:  UPnP enabled all boxes checked
                             WAN Ping is enabled
                             Port speed is Auto
                             Multicast Streams are enabled

Etc etc.

During the composing of this post, access to the cable modem config pages went back and forth from being inaccessible, to being accessible, to being inaccessible by the time i finished it.   Again, there were no problems accessing it with a DI-24 prior to the 4500, and there are no problems accessing it when the PC is directly connected to the cable modem.

I must say, however, that, considering this is a $200 gateway, im not too impressed with its connectivity and reliability so far, especially considering its replacing a DI-624v3 for those very reasons, yet it seems to have an almost identical set of reliability problems and issues (rebooting/loss of internet connectivity).

Additionally, the last official firmware update release for this newer product was over 5 months ago, yet the product has only been on the market for 6 months or so.  This is "stinking" of development abandonment already.  I'd sure like to be convinced otherwise with an immediate release of new beta and/or official firmware.

Any thoughts are appreciated.

[☠]

Second Problem:  Cant access Cable Modem configuration pages most of the time.

Having problems accessing the config pages of the cable modem at 192.168.100.1.  95% of the time or so, the pages wont open, and ping'ing the cable modem fails with request time outs.  Every once in a blue moon, the pages will open, and  pinging works fine.  No changes are made to the configuration of the 4500 when access is possible - one minute the pages will open fine, the next minute, no access.

when you are able to access yoru cable modem at 192.168.100.1 your DGL-4300 must also be in the 192.168.100.0/24 network.  the only time that this happens is when the Cable modem cant find a upstream connection.  the modem then turns on a DHCP server in the 192.168.100.0 netowrk. so the router can pull a DHCP address from the modem and not from the upstream ISP.  this is so you can trouble shoot your modem's signal to the ISP when it fails.

 so that 5% when you were able to access your modem at 192.168.100.1 is when
A: your ISP was down
B: you set a static IP address on the WAN of the DGL-4300 in the 192.168.100.0/24 network.
C: Chickenblood

Are you getting those ACK errors with a static IP address on the WAN?

[DLinkUserDude]

when you are able to access yoru cable modem at 192.168.100.1 your DGL-4300 must also be in the 192.168.100.0/24 network.

You do realize this is the DGL-4500 forum, not the DGL-4300 forum, right? 

Regardless, that simply isnt the case - if it were, the internet (and many LANs) at large "wouldnt work" because different devices/PCs "werent in the same network".  See, this is where the functionality of routers and gateways comes into play, and, in fact, the dysfunctional routing of the 4500.

In fact, as im writing this reply, the modem's configuration pages went from being inaccessible, to being accessible, to being inaccessible again - with zero change to the gateways WAN connectivity status.  If your claim were true, this would be "impossible".

the only time that this happens is when the Cable modem cant find a upstream connection.

Incorrect and misinformed.  Again, look into the concept of "routing".

  the modem then turns on a DHCP server in the 192.168.100.0 netowrk. so the router can pull a DHCP address from the modem and not from the upstream ISP.  this is so you can trouble shoot your modem's signal to the ISP when it fails.

That's great (and mostly accurate), but irrelevant to the issue of accessing the modems configuration pages.  Whether or not a DHCP server is active or not in the modem has absolutely nothing to do with the fact that the modem is always in the 192.168.100.x subnet at 192.168.100.1.  Nor does the existence and activity of a DHCP in the modem in any way effect the accessibility of the configuration pages.

In fact, access to the modems configuration pages is universal, not existential, meaning its accessible always, not just "when the modems signal to the ISP fails" (or when a DHCP server is active or not).

so that 5% when you were able to access your modem at 192.168.100.1 is when
A: your ISP was down
B: you set a static IP address on the WAN of the DGL-4300 in the 192.168.100.0/24 network.
C: Chickenblood

Again, you fail to understand the extant reality of routing etc.  There is no "ISP down" or "static IP on the WAN of the DGL-4300" (again, this is the 4500 forum, not the 4300 forum), or "chickenblood" when the 4500 is occasionally accessible.  Clearly, there is buggy routing code (a real "shocker") in this device, resulting in this inconsistent accessibilty behavior of the cable modem on the WAN interface.

Are you getting those ACK errors with a static IP address on the WAN?

Im pretty sure you dont even understand what it is you are trying to ask here with this question..

Thanks for the reply, hopefully the next one will be more informed (maybe you'll even figure out which product forum you are replying in..)

[Fatman]

Your abusive and inappropriate tone must stop DLinkUserDude.  You have been hounding both staff and guests here and we do not appreciate it.  Most bothering of all is you are only calling out people who know what they are talking about as near as I can tell.

Also of interest is the fact that what Xiuhtecuhtli was trying to say was 100% correct.  As far as hounding on him for typing the wrong model number, I ask who is being immature now.

When the DCM-202 fails to connect to the cable network it assigns DHCP on the 192.168.100.0/24 network.  So your router pulls this new DHCP address and suddenly you have a route (the interface local route if you want to be technical) for the 192.168.100.0/24 network.

When the DCM-202 successfully connects to the cable network you pull DHCP from your ISP on their network.  Your router still has an interface local route, but now it points to whatever public address network your ISP assigns.  You also receive a default gateway through this DHCP, however none of the upstream routers are going to know where to route the 192.168.100.0/24 network so that won't do you much good.

You could add a WAN route on the DGL-4500, however without an IP on the 192.168.100.0/24 network or a gateway with a route to the 192.168.100.0/24 network accessible on it's public network (which is assigned by your ISP) you aren't going to get anywhere.

If you happen to be from Missouri I offer you this physical test.

1) Pull the Coaxial cable out of the back of your DCM-202.  (this way your DCM-202 will always fail to establish a connection)
2) Power cycle your DGL-4500. (it's true you could just Release and Renew the WAN interface but this leaves no room for error)
3) Reboot your computer.  (it's true you could just Release and Renew you PCs IP but this leaves no room for error)

100% of the time your DGL-4500 should pull a WAN IP in the 192.168.100.0/24 network and 192.168.100.1 should be accessible to you.  Tell me if I am wrong.

Do you see the difference here?

One way you do have a IP and route leading to 192.168.100.0/24.

And the other way you don't, you only receive a public IP and routes leading to the rest of the internet.

If you understand half as much as you imply this should never have been a discussion.