deathbyburk
Occasional Visitor
Latest stock firmware with "WAN issues fix" and almost 24 hours no problems. I could not make more then 3 at any time. I'll keep posted but so far so good
That's interesting. To implicate the Merlin code, you will need to allow a few more renewals and/or force them. Then you need to go back to the Merlin code and see if the problem persists.Latest stock firmware with "WAN issues fix" and almost 24 hours no problems. I could not make more then 3 at any time. I'll keep posted but so far so good
So 2 full days and no issues. Not a merlin issue but was an ASUS until they patched 2 patches ago(assumption). Merlin should be merging that code next/soon.
oh sorry maybe I was not clear. gigabit/fiber is very new and not sure what/if is different then my prior 2 cable internet providers I have been using since I upgraded from my u.s. robotics 56k but could not stay connected. very sinilar "connected to internet but no internet" issues I see posted.
386.2_2
issues
clean reset - issues
386.2_4
same
384_19
clean reset and lost net after few hours and honestly had less patience at this point to mess with settings as I did other
Latest stock (not searching version atm)
3 days ROCK solid
Is there any further updates on this? I am using the latest stock firmware and have this exact problem.
I've been using FiOS for the past 11 years with whatever is the default DHCP setting and never had an issue.
Yes, by Ethernet cable. I don't have TV or phone service through FiOS.Is your Asus router connected directly to the ONT?
thanks will give it a try.The latest firmware allows you to set "DHCP query frequency" to Continuous. The setting can be found from the left side tab WAN and top tab Internet Connection. It is the third from the bottom. I'm on FIOS and rock solid.
Morris
Just installed the latest firmware released today (Version 3.0.0.4.386.45934) and changed the setting to continuous and it still disconnects
I posted this in another thread, but this one appears to be almost identical to my issues. Here's what I've tried over the past few weeks:
EDIT: #10 (15 hours): Another disconnect. Reboot of router was the only way to get back online, same IP address. I did see some upnp error logs so I disabled that for now to see if that helps. I'm currently using the Continuous setting for the DHCP query frequency.
You're still having disconnects after going down to 384.19? Did you do a full nuclear downgrade and not restore your settings (re-input them manually)?
I had this issue on 386 (don't recall which one I tried) and did a clean/nuclear downgrade to 384.19 and it has been fine ever since (other than the GUI becoming unreachable from time to time which was a common bug with that version). I've been waiting until several reports that 386 has fixed this until trying again. I tried continuous mode etc all without avail. Connected directly to ONT using a short CAT5E cable. This is on RT-AC68U.
Someone above mentions 386.2_6 working but not sure if they're just lucky or if it has really been fixed. It seems FIOS has different lease times in different areas. I get 2 hours leases and those seem to be the ones with the most issues. From what I can tell, the router is not properly sending DHCPACK to FIOS server so the IP gets given to someone else and thus you are blocked until you force a new IP. Was just a guess, I wasn't motivated enough to put a sniffer on the WAN to see.
If you've done a clean downgrade and are still having issues (especially if you are seeing speed dropouts) it may be a different issue. Connectivity issues on the WAN will also result in DHCP errors.
Not sure if anyone with 386.3 that was having the issue is now ok. Probably wait for 4 or 5 to come out before trying, honestly 384 is working fine for me other than having to reboot sometimes due to GUI freezing up.
I'm on FIOS, my RT-AX86U is connected to the ONT via CAT 5E and my DHCP lease is 2 hours. I'm Merlin V 385.3.2 and my DHCP query frequency is Continuous Mode. I do not have issues.
I feel you need to investigate why the DHCP handshake is falling during normal operation. I recommend trying:
- Replace jumper cable between ONT and router
- Run a speed test and see if you are getting at least the speed you are contracted for in both directions
- Consider your network load. If your link is heavily loaded with fire transfers, torrent's, or high packet rates from things such as gaming, you need to moderate the load.
- If it's file transfers, try CAKE QOS
- If it's packet rate, your router is under powered and you need an upgrade
Good luck,
Morris
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!