cancel
Showing results for 
Search instead for 
Did you mean: 

router loops round after 'connection', fails to get IPaddr

N/A

router loops round after 'connection', fails to get IPaddr

Hi all
I've been seeing an increasingly common problem happening on my ADSL router. It's a Netgeat DG824M wireless router, though I don't think the wireless part can be an issue.

When the router is disconnected (like, because of F9's new policies ;-( ), the router seems often to loop round trying to connect again. I can understand this might take a while, but what I don't understand is that it seems to fail when 'getting IP address'. I assume this is at the DHCP stage.

I can get the WAN status from the router, and this is the sort of thing that happens:

# 1)

Connection Time 00:00:00
Connecting to server ON
PPP LCP negotiation ON
Authentication ON
Getting IP addresses ---
Getting Network Mask ---


# [a minute or so delay]

# 2)

Connection Time 00:00:00
Connecting to server failed
PPP LCP negotiation ---
Authentication ---
Getting IP addresses ---
Getting Network Mask ---

[a short delay]

Connection Time 00:00:00
Connecting to server Waiting for Data
PPP LCP negotiation ---
Authentication ---
Getting IP addresses ---
Getting Network Mask ---

and then I might get back to #1 again, or something similar

When I talk to force 9 they tell me that at (1) I am 'connected', which seems true. Why, in that case, do I often seem to get thrown off again?

I've attached my basic settings to see if this can help identify the problem. I'm running the latest DG824M firmware AFAIK.

FWIW, I'm running a mix of windows and Linux PCs on the local network.
------------


System Name DG824M
Firmware Version Version 1.4 Release 05

WAN Port
MAC Address xx:xx:xx:xx:xx:xx
IP Address yyy.yyy.yyy.yyy
DHCP None
IP Subnet Mask 255.0.0.0
Domain Name Server 212.159.13.49
212.159.13.50

LAN Port
MAC Address xx:xx:xx:xx:xx:xx
IP Address 192.168.0.1
DHCP Server
IP Subnet Mask 255.255.255.0

ADSL Modem
ADSL Firmware Version 53050
Modem Status Connected
Connect Mode VC-BASED
Downstream Speed 2272 Kbps
Upstream Speed 288 Kbps
VPI 0
VCI 38

---

Thanks for any pointers
Jon N
3 REPLIES
N/A

router loops round after 'connection', fails to get IPaddr

what happens when you turn your router off and on again?

If this works, maybe there is something in the arp tables which is causing a problem. I dont know if you have the ability on these routers to flush the arp cache.
N/A

router loops round after 'connection', fails to get IPaddr

Hi there
thanks for your post.

I can get access to the routing table but can't clear it except by rebooting. It currently (ie. when things are working) displays

Destination Mask Gateway Metric Active
192.168.0.0 255.255.255.0 192.168.0.1 1 Yes
192.168.0.1 255.255.255.255 192.168.0.1 1 Yes
84.92.128.135 255.255.255.255 84.92.128.135 1 Yes

(84.92.128.135 is my WAN IP address)

Rebooting the gateway, either remotely or via power-cycle, doesn't seem to help. I have also left the power off for 30mins or so to see if the unit was over-heating, but this didn't seem to have any effect.

I've also been looking at the statistics the router/gateway can give me. When it is connecting, or failing to connect, I get figures like this:

System Up Time 00:12:23
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN ADSL 113 15 0 9 3 00:12:23
LAN 10M/100M 2082 3514 0 1379 1233 00:12:23


System Up Time 00:23:58
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN ADSL 1388 1207 0 2 2 00:23:58
LAN 10M/100M 5726 10428 0 1325 1024 00:23:58

(or even 0 0 for the TX b/s and RX b/s). It this simply reflecting that there is very little traffic, or that there is a speed problem on my line? After I've connected, the figures seem to fluctuate widely (I'm polling every 10 seconds), for example

System Up Time 00:24:28
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN ADSL 1718 1458 0 30106 5760 00:24:28
LAN 10M/100M 6122 11340 0 7430 61956 00:24:28

then:

System Up Time 00:36:00
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN ADSL 3709 3461 0 2 2 00:36:00
LAN 10M/100M 10054 18701 0 1325 1024 00:36:00

I am a bit suspicious that all of this seems to have been happening after F9 changed their traffic policies...

Oh, one more thing (sorry!) According to my connection page on F9 I have a Static IP. This surprises me as I don't think I asked for it, but never mind... I was wondering, since my connection seems to fail when 'getting IP addresses', if I could change the Gateway setting to use this IP address instead of getting it from F9. The support page says not to do this, but I'd like to know why now...

Thanks for any thoughts
Jon N
N/A

router loops round after 'connection', fails to get IPaddr

Not too sure about this. I am not quite sure what force9 do when they issue a disconnect to your IP. You should be able to re-establish the connection easily.

What I would do is try another router (if you have one to hand) and see if that has the same problem. Try connected to your external IP over http for example, see if you can get a response. I am assuming you have spoke to force9 about it. Other than that, it seems strange that this is happening.