dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
19013
share rss forum feed

Mystiky4

join:2006-03-15
New York, NY

1 edit
reply to claibourne

Re: Actiontec MI424WR Router Revision I - bug/problem ?!

said by claibourne:

I think trying this with the Rev E is crazy. You have the 150/35 package, right? You're losing a third of your bandwidth. On the plus side, if the problem doesn't recur, there may be an issue with the second Rev I.

I actually have the 25/25 package, so for now, I am not loosing anything. As far as you making a prediction that it will probably not solve anything, I would not bet against you.

My next step (as I said earlier today) is indeed to try WNDR3800 instead of the WNDR4500. If that fails, I am going back to Actiontec Rev. I, but this time directly hardwired to PC (getting rid of any and all Netgears), I promise

Mystiky4

join:2006-03-15
New York, NY
reply to rhdcheme
said by rhdcheme:

Claibourne,

The only problem is that the WNDR4500 is not the only Netgear router with the connect/disconnect, DNS, etc. problems. I know for a fact that the WNDR3700 suffers from the same and they have issued a beta firmware for that too. Not so sure about the WNDR3800 though.

Agreed. But most of these DNS issues are not when the WNDR4500 (or the WNDR3800) is running in AP Mode. And curiously again, my internet does not go 100% down. It works about 10% of the time. Meaning, pages load 1 time out of 10 retries.

My "hope" is that since Rev E has been out for so long, that Netgear might be more "user-friendly" to it than Rev. I.

claibourne

join:2011-07-04
Garland, TX
reply to rhdcheme
said by rhdcheme:

Claibourne,

The only problem is that the WNDR4500 is not the only Netgear router with the connect/disconnect, DNS, etc. problems. I know for a fact that the WNDR3700 suffers from the same and they have issued a beta firmware for that too. Not so sure about the WNDR3800 though.

True, but he's got the 3800 on hand, and doesn't want to give up his 5ghz capability. There's a chance (remote?) that the problem is 4500-specific, so it's worth a shot. If the problem persists with the 3800, I think he needs to go back to the "standard" VZ-supported config and leave the secondary routers out of the equation.

Or, based on your experience, go buy an E4200 or some other brand with dual-band, and see what happens.

Mystiky4

join:2006-03-15
New York, NY

1 edit
reply to Mystiky4
It looks like I did not have to even wait 24 hours! About 20 hours into my experiment, similiar problems started to happen with setup using Actiontec Rev. E. Interesting enough, after about 15 minutes of it, the issues seemed to have fixed themselves for about another 30 minutes but it did not matter. I had enough.

So, I have now taken down the WNDR4500 and installed the WNDR3800 and put back Actiontec Rev. I.

So, this is now what I have going:

My Actiontec is on 192.168.1.1
My WNDR3800 is on 192.168.1.11

In the Actiontec:
-----------------
Nothing is DMZ'ed
DNS is set to 4.2.2.2 / 4.2.2.3
My Start IP address is from 192.168.1.10
Assigned 192.168.1.11 a "Static" DHCP address
Disabled Wireless completely

In the WNDR3800:
-------------------
Flashed to 1.0.0.25(Beta) firmware
Changed it to "AP Mode"

And my hardwired connection is as follows:

ONT---(WAN)Actiontec(LAN)---(WAN)WNDR3800(LAN)---PC

Additional comment: This is it. If this WNDR3800 doesn't solve the issue, I will indeed go to Actiontec ALONE by itself to see
if that fixes things. And if it does, this means that it is time for me to say goodbye to Netgear. Amazing, I swore 2 years ago that I would never buy another Linksys product after the hell I had with the E3000 and trying to get it to work with WD TV Live HD box. Linksys' tech support is about the worst I have come across in my 25+ years of being around computers. I spent over 3 months killing myself trying to figure it out. Then out of desperation, I bought a Netgear WNDR3700 v1. It worked from the first moment and was solid for 18 months!

You might ask: Why I am not just using my old sturdy WNDR3700 v1 right now? (as they said, if it ain't broke, dont try to fix it). It's because it could not handle the AP Mode correctly. If one looks back at the forum, you will find problems that I was having with that and hence where the idea to try the WNDR4500 started.

Edit: Here is a link to that topic: »WNDR3700 / WNDR4500 with Rev. I

Last point on WNDR3800. I know that I can try a 3rd part firmware in case the firmware I am trying doesn't work. I am open to that, but only after I try the Actiontec alone.

Thanks again all for your patience and help.

Mystiky4

join:2006-03-15
New York, NY
reply to Mystiky4
While I wait to see the results of the latest scenario, I do have a semi-related question.

I noticed that when I had the Netgear WNDR4500 plugged into the Actiontec (LAN port #1), both of the LAN lights on the Actiontect were blinking (the 100 and the 10). This iwas exactly the same as on the Actiontec WAN port, which goes to the ONT.

However since I now have the Netgear WNDR3800 plugged into the Actiontec (same LAN port), I only see the light next to the 100 blinking. However the Actiontect WAN port to the ONT has both of the lights blinking.

No cables were changed at all during all of the swaps.

Any ideas why this is like this?


More Fiber
Premium,MVM
join:2005-09-26
West Chester, PA
kudos:32
That indicates the WNDR4500 is connecting at gigabit speeds, while the WNDR3800 is only connecting at 100Mbps speed.

The WNDR3800 does indeed have gigabit LAN ports, so that would imply it is not correctly negotiating a 1Gbps connection with the Actiontec.
--
There are 10 kinds of people in the world; those who understand binary and those who don't.

aguen
Premium
join:2003-07-16
Grants Pass, OR
kudos:2
said by More Fiber:

That indicates the WNDR4500 is connecting at gigabit speeds, while the WNDR3800 is only connecting at 100Mbps speed.

Or, that the WNDR3800 does not have a GB Wan port.

said by Mystiky4:

ONT---(WAN)Actiontec(LAN)---(WAN)WNDR3800(LAN)---PC


Mystiky4

join:2006-03-15
New York, NY
reply to Mystiky4
Looks to be that the WNDR3800 does have the Gigabit support for both LAN and WAN, based on the Manual"

-----------------
Figure 4. Back panel features
- The four local (LAN) 10/100/1000 Mbps Ethernet ports are for cabling the router to local computers.
- The Internet (WAN) 10/100/1000 Mbps Ethernet port is for cabling the router to a cable or DSL modem.
-----------------

So if the WNDR3800 does end up as the one that works in my setup, how can I make it more friendlier with the Actiontec to support it at 1000Mbps?


More Fiber
Premium,MVM
join:2005-09-26
West Chester, PA
kudos:32
said by Mystiky4:

So if the WNDR3800 does end up as the one that works in my setup, how can I make it more friendlier with the Actiontec to support it at 1000Mbps?

If the only traffic passing over the Actiontec(LAN) to WNDR3800(WAN) port is internet traffic, it won't make any difference since the your speed tier is 35/35.
--
There are 10 kinds of people in the world; those who understand binary and those who don't.

Mystiky4

join:2006-03-15
New York, NY
reply to Mystiky4
UDPATE (after 51 hours).
-------------------------

For now, everything is looking stable. I did have something weird happen about an hour ago, but maybe it was just a bad load of a webpage. I have not been able to replicate it for the last hour, so keeping my fingers crossed.

Questions:

1) I have the the DNS set as 4.2.2.2 and 4.2.2.3 -- why is it showing a dfifferent number in the log below? It referes to: DNS:68.237.161.12

2) Why is the DHCP WAN connection updated every hour (at 9 minutes past each hour). Is that normal?

Does anyone see anything else weird or strange in the log? I have redacted the IP address for privacy concerns.

Thanks and will keep you posted.

Logfile:

Feb 13 14:09:04 2012 System Log LAN Coax LAN Coax Link Up
Feb 13 14:09:49 2012 System Log LAN Coax LAN Coax Link Rate
Feb 13 14:10:29 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.11, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 13 14:10:59 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.14, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 13 14:11:21 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.12, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 13 14:14:04 2012 System Log LAN Coax LAN Coax Link Rate
Feb 13 14:15:54 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.12, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 13 14:16:16 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.14, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 13 14:20:32 2012 System Log CWMP Connection Request Inform initial 401 chanllenge
Feb 13 14:20:33 2012 System Log CWMP Connection Request Inform challege response with 200 OK from server
Feb 13 14:20:44 2012 System Log CWMP Connection Request Inform 204 No Content
Feb 13 15:09:03 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 13 15:20:29 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.10, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 13 16:09:04 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 13 16:15:50 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.101, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 13 16:58:31 2012 System Log CWMP Periodic Inform initial 401 challenge
Feb 13 16:58:32 2012 System Log CWMP Periodic Inform challenge response with 200 OK from server
Feb 13 16:58:32 2012 System Log CWMP Periodic Inform 204 No Content
Feb 13 17:09:04 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 13 17:38:29 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.100, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 13 18:09:04 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 13 23:20:07 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.13, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 14 00:09:05 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 14 02:10:58 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.11, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 14 02:15:53 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.12, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 14 02:45:45 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.14, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 14 03:09:06 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 14 04:15:50 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.101, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 14 05:09:06 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 14 05:38:29 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.100, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 14 06:09:07 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 14 11:20:07 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.13, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 14 12:09:08 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 14 14:09:07 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 14 14:11:00 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.11, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 14 14:15:53 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.12, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 14 15:09:08 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 14 15:09:59 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.14, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 14 16:09:08 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 14 16:15:49 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.101, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 14 16:58:31 2012 System Log CWMP Periodic Inform initial 401 challenge
Feb 14 16:58:33 2012 System Log CWMP Periodic Inform challenge response with 200 OK from server
Feb 14 16:58:33 2012 System Log CWMP Periodic Inform 204 No Content
Feb 14 17:09:08 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 14 17:38:29 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.100, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 14 18:09:08 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 14 19:53:35 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.13, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 14 20:09:09 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 14 20:15:16 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.13, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 14 21:09:09 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 14 23:11:45 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.14, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 14 23:55:15 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.12, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 15 00:09:10 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 15 00:33:50 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.12, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 15 01:09:10 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 15 01:10:21 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.12, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 15 02:09:10 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 15 02:10:49 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.12, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 15 02:11:12 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.11, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 15 02:59:25 2012 System Log CWMP Connection Request Inform initial 401 chanllenge
Feb 15 02:59:26 2012 System Log CWMP Connection Request Inform challege response with 200 OK from server
Feb 15 02:59:27 2012 System Log CWMP Connection Request Inform 204 No Content
Feb 15 03:09:10 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 15 03:16:39 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.12, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 15 04:09:11 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 15 04:15:50 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.101, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 15 05:09:11 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 15 05:26:10 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.12, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 15 05:38:29 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.100, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 15 06:09:11 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 15 08:15:18 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.13, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 15 09:09:12 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 15 11:16:09 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.14, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 15 11:32:51 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.12, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 15 12:09:12 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 15 12:12:02 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.12, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 15 13:09:12 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 15 14:09:12 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 15 14:11:21 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.11, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 15 15:09:12 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 15 16:15:50 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.101, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 15 16:58:31 2012 System Log CWMP Periodic Inform initial 401 challenge
Feb 15 16:58:32 2012 System Log CWMP Periodic Inform challenge response with 200 OK from server
Feb 15 16:58:32 2012 System Log CWMP Periodic Inform 204 No Content
Feb 15 17:09:13 2012 System Log WAN DHCP DHCP WAN connection IP:72.68.x.x,DNS:68.237.161.12 71.250.0.12 ,GTW:72.68.x.1,Subnet:255.255.255.0 (WAN Ethernet)


More Fiber
Premium,MVM
join:2005-09-26
West Chester, PA
kudos:32

1 recommendation

1) THe router has two sets of DNS addresses. a) Those received from VZ when your router does a DHCP lease request, and, b) those issued to a LAN device when the LAN device does a DHCP lease request.

2) VZ's DHCP lease interval is 2 hours. At 1/2 the lease inter, the router renews the WAN DHCP lease for another 2 hours. You apparently booted your router at 9 minutes after the hour. Therefore, you see a DHCP renewal 9 minutes after each hour.
--
There are 10 kinds of people in the world; those who understand binary and those who don't.

Mystiky4

join:2006-03-15
New York, NY
reply to Mystiky4
UPDATE:
--------

My system has been up for 73 hours, 11 minutes.

Knock on wood, but so far so good.

Mystiky4

join:2006-03-15
New York, NY
reply to Mystiky4
ANOTHER UPDATE
-----------------

Active Status (Router Has Been Active For): 94 hours, 0 minutes

Unreal! So it looks like the WNDR4500 was the culprit after all. Just amazing. The WNDR3800 got some flack from many publications calling it a "so-so" router, while the WNDR4500 was called "the messiah".

Well, buyer BEWARE! Stay away from WNDR4500 if you are thinking about putting it together with the Actiontec / FIOS combo.

If this is the end of my drama for real, I want to thank you ALL for trying to help me, and for putting in the many feedbacks, which were very useful.

I will copy this message to another thread so if anyone else ever has a smiliar problem, they will at least know that it's WNDR4500 issue.

Mystiky4

join:2006-03-15
New York, NY
reply to Mystiky4
This looks to be my last UPDATE regarding my drama:

Rev I - Active Status (Router Has Been Active For): 331 hours, 12 minutes

Seems now that the WNDR4500 was the definate culprit for sure. Ugggghhh!


FiOS_NJ

@verizon.net
reply to Mystiky4
Does anyone know if the rear blue USB ports are USB 3.0?


More Fiber
Premium,MVM
join:2005-09-26
West Chester, PA
kudos:32
said by FiOS_NJ :

Does anyone know if the rear blue USB ports are USB 3.0?

It doesn't matter. They're not active.
--
There are 10 kinds of people in the world; those who understand binary and those who don't.


nycdave
Premium,MVM
join:1999-11-16
Melville, NY
kudos:17
reply to FiOS_NJ
No they are not 3.0.....Even if they were currently active.

macworth

join:2009-07-16
Medford, MA
reply to Mystiky4
So did that resolve your problem? You just switched the 4500 for the 3800?

I have a rev I and I am using an ASUS RT-N56U as a wireless access point (it has a special mode for it which turns of DHCP and everything). I am running into the same problem.

Mystiky4

join:2006-03-15
New York, NY

2 edits
Yep - taking away that WNDR4500 and putting the WNDR3800 fixed the problem100%. And check this out, now running without any reboots for:

Active Status (Router Has Been Active For): 2131 hours, 53 minutes

kmss1
Premium
join:2002-04-30
Yucaipa, CA
Nice job of troubleshooting the issue Mysticky4! You have saved me miles of headaches!

Mystiky4

join:2006-03-15
New York, NY
Glad to be of help! Believe me, those 3-4 weeks that I spent banging my head against the wall (or shall we say the WNDR4500), were some of my toughest around computers. And I am one of those who goes back to an Atari 400 with 16K and the Atari 410 Tape Recorder (thats before the floppy!).

kmss1
Premium
join:2002-04-30
Yucaipa, CA
You and I must be in the same age range; I have an old Trash-80 sitting in the garage (protected) that will still boot, and I remember all those old 8086 and 8088 machines, with the tapes and 5¼" ss/sd floppies!