dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2781
share rss forum feed


Exetubin

@telepacific.net

DLink DGL-4500 Behind 2Wire HGV-3600 (in DMZ) Disconnection

I was a previous ATT DSL customer and now switched to UVerse Internet just 3 days ago.

In my old (ATT DSL) setup, I only had a DSL modem, had my DGL-4500 router's WAN interface connected to the DSL modem and everything worked great.

In my new (UVerse) setup, I'm having difficulty getting solid (no disconnect) connection.

The router/gateway that ATT sent me was the 2Wire HGV-3600 and there are various articles out there on how to setup this router/gateway to work with your existing router.

I used these following articles to help me in the new setup:

1.) »www.dd-wrt.com/phpBB2/viewtopic.php?p=602195
2.) »Bridging a 3600HGV to another Router
3.) others that I have bookmarked in my home PC (I'm at work right now)

I have followed all instructions carefully and am able to get all equipment connected to the DGL-4500 router work and connect to the internet.

My issue is that the connection drops after several hours.

Over the weekend, I had the router online for 14+ hours, but, around 430PM or 5PM, the DGL-4500 rebooted and I'm not sure what's causing this.

I have read an article where a firewall rule needs to be added to open a particular UDP port, but, I think this solution only applies to DDWRT firmware (which my router does not use).

Any help on this is greatly appreciated.

Thank you in advance!



Forosnai

join:2011-09-30
kudos:2

UDP port 68 inbound on the Dlink.
The DMZ+ on the 3600 won't stick if it isn't set up in the proper order. I would read the following topic, factory reset 3600 and the Dlink, and give it one more stab. The order is critical.
»forums.att.com/t5/Residential-Ga···=desktop



bdavenport

join:2004-09-20
Charlotte, NC
reply to Exetubin

said by Exetubin :

Over the weekend, I had the router online for 14+ hours, but, around 430PM or 5PM, the DGL-4500 rebooted and I'm not sure what's causing this.

This sounds like you might know the problem but might be looking at the wrong thing. If your dlink router reboots randomly, then I have to question if the router is actually performing like it should.

I assume you setup your 2wire modem to have the dlink router in DMZ+ mode?

What happens if you were to do the following next time your dlink reboots or has connection issues: plug yourself into the 2wire modem bypassing the dlink. Do you still have connectivity to the internet? If so I would say you might have a hardware issue rather than software. If not then you need to persue a different problem

Also can you get to the dlink router status page and see if it has appropriate IP info from the 2wire modem when you have a issue?


Exetubin

@telepacific.net
reply to Forosnai

I appreciate the reply, Forosnai.

The DGL-4500 has been up for 1 day, 16 hours last time I checked, so, hopefully I don't get a reboot anymore.

If it reboots again, I'll try your suggestion and follow the instructions in order (I'll make sure about this).

I'll keep you posted.



Exetubin

@telepacific.net
reply to bdavenport

bdavenport, thanks for the reply.

Like I mentioned in my original post, prior to switching to UVerse service, I was only using an ATT DSL modem and my DGL-4500 router worked flawelssly.

Since I connected the 2Wire router / gateway last 08/10/2012, I have been getting these reboots.

I honestly don't think the router is broken and I think the reboots are due to the new configuration.

I wish there was a way ATT can send just a UVerse modem (NOT a router / gateway), but, unfortunately, there's nothing I can do about that.

As of this morning (before heading out to work), I checked the DGL-4500 and it says it's been up and running for 1 day and 16 hours, so, it's been up for quite sometime now since last Sunday's reboot.

Hopefully it stays that way.

I'll keep you posted.



Exetubin

@sbcglobal.net
reply to Exetubin

The DGL-4500 router rebooted again at around 150PM today.

Here's a log of the router just about the time it rebooted:

[INFO] Tue Aug 14 14:58:16 2012 Firmware upgrade server wrpd.dlink.com.tw is at IP address NNN.NNN.NN.NNN
[INFO] Tue Aug 14 14:58:13 2012 Above message repeated N times
[INFO] Tue Aug 14 14:56:13 2012 Dropped packet from NNN.NN.NNN.NNN to NNN.NNN.NNN.NNN (IP protocol NN) as unable to create new session
[INFO] Tue Aug 14 14:56:12 2012 Obtained IP Address using DHCP. IP address is NNN.NN.NNN.NNN
[WARN] Tue Aug 14 14:56:03 2012 A network computer (NNNFNAABNNNN) was assigned the IP address of NNN.NNN.N.NNN.
[WARN] Tue Aug 14 14:55:01 2012 Above message repeated N times
[INFO] Tue Aug 14 14:54:54 2012 The DHCP server address NNN.NNN.N.NNN was released by the network device - the network device no longer wants to use it.
[WARN] Tue Aug 14 14:54:07 2012 A network computer (NNNFNAABNNNN) was assigned the IP address of NNN.NNN.N.NNN.
[INFO] Tue Aug 14 14:53:54 2012 The DHCP server address NNN.NNN.N.NNN was released by the network device - the network device no longer wants to use it.
[WARN] Tue Aug 14 14:53:08 2012 A network computer (NNNFNAABNNNN) was assigned the IP address of NNN.NNN.N.NNN.
[INFO] Tue Aug 14 14:52:55 2012 The DHCP server address NNN.NNN.N.NNN was released by the network device - the network device no longer wants to use it.
[WARN] Tue Aug 14 14:52:11 2012 A network computer (NNNFNAABNNNN) was assigned the IP address of NNN.NNN.N.NNN.
[INFO] Tue Aug 14 14:52:02 2012 The DHCP server address NNN.NNN.N.NNN was released by the network device - the network device no longer wants to use it.
[WARN] Tue Aug 14 14:51:17 2012 A network computer (NNNFNAABNNNN) was assigned the IP address of NNN.NNN.N.NNN.
[INFO] Tue Aug 14 14:51:03 2012 The DHCP server address NNN.NNN.N.NNN was released by the network device - the network device no longer wants to use it.
[INFO] Tue Aug 14 14:50:54 2012 Lost lease on IP Address
[INFO] Tue Aug 14 14:50:10 2012 Dropped packet from NNN.NNN.N.NN to NNN.NNN.NNN.NNN (IP protocol NN) as unable to create new session
[INFO] Tue Aug 14 14:50:09 2012 Obtained IP Address using DHCP. IP address is NNN.NNN.N.NN
[INFO] Tue Aug 14 14:50:07 2012 Lost lease on IP Address
[WARN] Tue Aug 14 14:46:34 2012 A network computer (NNNFNAABNNNN) was assigned the IP address of NNN.NNN.N.NNN.
[INFO] Tue Aug 14 14:46:20 2012 The DHCP server address NNN.NNN.N.NNN was released by the network device - the network device no longer wants to use it.
[INFO] Tue Aug 14 14:46:10 2012 Dropped packet from NNN.NNN.N.NNN to NNN.NNN.NN.NNN (IP protocol N) as unable to create new session
[INFO] Tue Aug 14 14:46:08 2012 Above message repeated N times
[WARN] Tue Aug 14 14:45:35 2012 A network computer (NNNFNAABNNNN) was assigned the IP address of NNN.NNN.N.NNN.
[INFO] Tue Aug 14 14:45:25 2012 The DHCP server address NNN.NNN.N.NNN was released by the network device - the network device no longer wants to use it.
[INFO] Tue Aug 14 14:33:46 2012 Blocked incoming TCP connection request from NN.NN.NNN.NNN:NNNNN to NNN.NN.NNN.NNN:NNN
[INFO] Tue Aug 14 14:33:43 2012 Above message repeated N times
[INFO] Tue Aug 14 14:31:52 2012 Blocked incoming TCP connection request from N.NN.NN.NNN:NNNN to NNN.NN.NNN.NNN:NNNN
[INFO] Tue Aug 14 14:26:57 2012 Blocked incoming TCP connection request from NNN.NN.NNN.NN:NNNNN to NNN.NN.NNN.NNN:NN
[INFO] Tue Aug 14 14:26:54 2012 Above message repeated N times
[INFO] Tue Aug 14 14:05:48 2012 Blocked incoming UDP packet from NN.NNN.NN.NNN:NNNN to NNN.NN.NNN.NNN:NNNN
[INFO] Tue Aug 14 13:36:59 2012 Blocked incoming TCP connection request from NN.NN.NN.NNN:NNNNN to NNN.NN.NNN.NNN:NNN
[INFO] Tue Aug 14 13:36:56 2012 Above message repeated N times
[INFO] Tue Aug 14 13:29:43 2012 Blocked incoming TCP connection request from NNN.NNN.NNN.N:NNNN to NNN.NN.NNN.NNN:NNNN
[INFO] Tue Aug 14 13:29:34 2012 Above message repeated N times
[INFO] Tue Aug 14 13:23:35 2012 Blocked incoming TCP connection request from NNN.NNN.NNN.NNN:NNNNN to NNN.NN.NNN.NNN:NN
[INFO] Tue Aug 14 13:20:43 2012 Blocked incoming TCP connection request from NNN.NNN.NN.NN:NNNN to NNN.NN.NNN.NNN:NNNN
[INFO] Tue Aug 14 13:18:22 2012 Blocked incoming TCP connection request from NNN.NN.NN.NNN:NNNN to NNN.NN.NNN.NNN:NNNN
[INFO] Tue Aug 14 13:18:13 2012 Above message repeated N times
[INFO] Tue Aug 14 13:04:46 2012 Blocked incoming TCP packet from NN.NNN.NNN.NN:NNNN to NNN.NN.NNN.NNN:NNNNN as SYN:ACK received but there is no active connection
[INFO] Tue Aug 14 12:38:59 2012 Blocked incoming TCP connection request from NN.NN.NNN.NNN:NNNN to NNN.NN.NNN.NNN:NNNN
[INFO] Tue Aug 14 12:38:56 2012 Above message repeated N times
[INFO] Tue Aug 14 12:38:35 2012 Blocked incoming UDP packet from NNN.NN.NNN.NN:NNNNN to NNN.NN.NNN.NNN:NNNNN
[INFO] Tue Aug 14 12:37:50 2012 Blocked incoming TCP connection request from NN.NNN.NNN.NN:NNNNN to NNN.NN.NNN.NNN:NNNN
[INFO] Tue Aug 14 12:37:47 2012 Above message repeated N times
[INFO] Tue Aug 14 12:37:41 2012 Blocked incoming UDP packet from NNN.NN.NNN.NN:NNNNN to NNN.NN.NNN.NNN:NNNNN
[INFO] Tue Aug 14 12:37:20 2012 Above message repeated N times
[INFO] Tue Aug 14 12:29:43 2012 Blocked incoming TCP connection request from NNN.NNN.NN.NNN:NNNNN to NNN.NN.NNN.NNN:NN
[INFO] Tue Aug 14 12:29:40 2012 Above message repeated N times
[INFO] Tue Aug 14 12:22:07 2012 Blocked incoming TCP connection request from NN.NN.NNN.NNN:NNNNN to NNN.NN.NNN.NNN:NNNN
[INFO] Tue Aug 14 12:22:04 2012 Above message repeated N times
[INFO] Tue Aug 14 12:16:08 2012 Blocked incoming TCP connection request from NNN.NNN.NN.NN:NNNNN to NNN.NN.NNN.NNN:NNNNN
[INFO] Tue Aug 14 12:16:05 2012 Above message repeated N times
[INFO] Tue Aug 14 12:02:54 2012 Blocked incoming TCP connection request from NNN.NN.NN.NNNN:NNNN to NNN.NN.NNN.NNN:NNNN

The reason for the reboot, I think is the 16th line where it says:
[INFO] Tue Aug 14 14:50:54 2012 Lost lease on IP Address

I'm not sure about this, however, so, it'll be a great help if someone can pitch in to help me resolve the issue.

I wonder if opening UDP port 68 inbound on the DLink DGL-4500 would fix the issue (I'm not sure how to set this up, however, so, any assistance on how to do this is greatly appreciated as well).

Thank you in advance for the assistance.



Red Hazard
Premium
join:2012-07-21
O Fallon, IL
Reviews:
·VOIPO
reply to Exetubin

Though I have not switched to Uverse yet, this setup sounds the most promising from somejoe7777 for getting close to a bridge mode:
»forums.att.com/t5/Residential-Ga···/2707013



Exetubin

@sbcglobal.net
reply to Exetubin

Click for full size
I was able to RESOLVE this issue by following a tell-tale clue exposed in this article about the 2Wire HGV-360 NOT SENDING the WAN IP DNS address:

»www.jaynath.com/2011/01/setting-···nt-15528

Essentially, the solution was to LOG ON to the DGL-4500, GO TO Basic > Internet > CLICK Manual Configure Button, and then plugging in the "Primary DNS Server" and "Secondary DNS Server" values provided by your ISP (you need to search on Google --OR-- contact your ISP and ask for these values).

My connection has been continous with no disconnects or reboots for 4 days now.


mackey
Premium
join:2007-08-20
kudos:12
reply to Exetubin

said by Exetubin :

[INFO] Tue Aug 14 14:58:13 2012 Above message repeated N times
[INFO] Tue Aug 14 14:56:13 2012 Dropped packet from NNN.NN.NNN.NNN to NNN.NNN.NNN.NNN (IP protocol NN) as unable to create new session

Looks like the router ran out of memory and soft rebooted. This might be caused by that DNS issue if it's trying to look something up and failing and isn't handling the failure properly.

/M