Which wasn't new btw, it was clearly "renewed"/used, clear scratches and light cosmetic damages on the rear of the unit in general, and all around the ethernet outlets. I called the ISP and from ISP, they said modem still connected to "old router", so they reset from their side at your modem. Whenever it tries to connect to the NOW service, I get an error stating "Your ISP's DHCP Does Not Function Properly". I then re-applied the newest firmware and it's kept the connection. Hello community, I have recently joined NOW Broadband and am struggling to get my ASUS router working. Everything is pointing towards the WAN feed, but I'm not sure of what it could be??? Until it's hidden/lost, and everything fails outright). If im going to be forced to one IP type and have static IP, then I'm going to another provider and getting FTTH this week, not with paying Rogers for this anymore. Hi @drFishFlan, I'm really sorry for the problem with your FTTP service. Getting a little frustrated. Do you happen to know the ticket number, and if so, can you post it so that other customers can use that for reference purposes? Also, when I go to the DOCSIS WAN page, the DOCSIS Overview section directly below is fully populated again. However, I myself am still setup for Automatic IPv4 not Static, and have been ok for the last 48hours.... Important if the is an option for VLAN it is not selected.
When logged into my router's setup page, I am seeing a message "Your ISP's DHCP does not function properly" - any insight into what that could be caused by, and if it might be causing my current issues?
Happy to share config screenshots if that helps! Hardware Version||1A|. Now that said, I have my CODA in bridgemode, so I have no access to the login/configuration pages, and cannot verify what firmware version I am on at this point, or if that 4pm event Saturday was a firmware patch or just a drop... But great summary of what you have found! I need to reboot the modem each time to resolve this. The main part of the issue though, I still believe, is the removal/discontinued use of IPv4 entirely. Let me know how it goes.
Just wanted to keep folks in the loop so we can continuously share experience until we know its been resolved. It's almost as if I have an issue with the WAN port. Then I set up my new router again and everything is solved. None of the above have helped. I've identified that your connection is affected by the same issue as Here which we have logged as an incident (for my ref: IMT-8090). Swapped Hilton router out 3 days ago but nothing has really changed. And a technician will be sent onsite. 5gbps eth, router, that fully supports IPv6 native from ISP..... For a week it was showing all zeros except for what looked like an IPv6 address in the IP Address field preceded by 0. And depending on lease time settings, auto reboot settings, and specfic router firmware and models, our routers may be asking for a new IPv4 address, but receiving the same IPv4, and therefore our routers are confused they didn't recieve a new IPv4, and choke out... hence ISP DHCP errors... because in Automatic IP, the DHCP should issue a new IPv4 when asked too, not issue the same one... But when the connection fails, the IPv4 goes to 0.
Were you supplied a Hub Two as part of your FTTP installation? As already been stated you need to setup the ASUS for PPPoE connection. 19-09-2022 10:46 AM - edited 19-09-2022 10:47 AM. So I've had this for the last month or so as well, and I believe I've tracked the issue, but I have no resolutions for it as Rogers refuses to acknowledge its the likely cause, even with my crazy proof. And they REFUSE to roll back the firmware updates, I've requested for it several times. I had been running the latest (3. Them trying to go full IPv6 without warning to ANYONE, is the issue. I've been having the same problem since mid last week.
At this moment I don't consider my issue resolved... When you are setting the TP Link up in modem only mode what options does it give for ISP in step 5 from here: How to setup TD-W9970 Router in Modem Only Mode? Called Rogers and informed them that this not an area issue and should be looking at the modem for firmware and etc. DOES NOT YET support PURE IPv6 internet. I would like to raise a few issues that may need to be considered by bridgemode users and Rogers tech support though... if Rogers has transitioned from "Automatic" or Randomized IPv4, to Static IPv4, then users like myself, may need to adjust our network setups... Same, I also changed asus router and suffered this error. But no amount of factory resetting or rebooting will get a new IPv4 address anymore..... It happens at random times and certain devices will drop the connection while others will have it. Can anyone from Rogers help explain and clarify this here?
I ofund this track on Rogers forum which is related: Thanks. I'm now double NAT'ing which is less than optimal. I'm on software version 7. 0, the IPv6 remains valid, but no connections because all our devices believe the DHCP has simply failed, as NO available 3rd party routers on the markets, support pure IPv6 ISP DHCPs to my understanding. Anyone else into the same situation where it started to drop again today? Otherwise, my set up is as per the step 5 graphic. It already dropped like 3 times today already since Sunday night. My router from time to time, momentarily lost the connection to the Modem (hitron CODA-4582). Looks like I'm in the same boat. I contacted Asus and confirmed this just over 48hours ago.
Keep us posted if anyone finds a solution for this. As I did not experience any DHCP issues from Thursday to Saturday ever just 30 mins ago it just happened again! The options on the TD-W9960 are slightly different as there is no "ISP" option. This goes away if I reboot the modem and everything works fine for the day then by the next morning I have all the issues again. How did it go after the tech visit? I have to power-cycle my CODA-4582 almost every morning since I can't access the admin page to do a reboot, then it's fine for the rest of the day at least until I go to bed. Still trying to digest it and understand it. Simply put, even though my Asus GT AX11000 wifi6, 2. However, if I configure my TP Link as a router with a Sky(MER) profile, it connects immediately. You can choose the modulation type of ADSL or VDSL instead, I have VDSL selected.
You indicated that "You will need the firmware update to be applied manually from Rogers and there is no other recourse as far as we were told". Just to point out, the other potentially offending partner in all of this is the CMTS, which has its own software configuration, which does change. The DHCP is trying to remove/hide our IPv4 addresses and rely strictly on IPv6, and specifically those of us with bridge mode enabled and likely more powerful routers, still require IPv4 valid, visible, addresses for our devices to even communicate with the ISP DHCP. I've never had to deal with this before but it's getting extremely frustrating. Edited for spelling, sorry if I missed anymore XD. I can however confirm, that I have had both a valid IPv4 and IPv6 address this entire time, I havnt been monitoring the IPv6 address itself, but the IPv4 is still definitely static and no longer randomized from Rogers. Mine seems to have sorted itself out as of this past Thursday, I haven't had to reboot it since then. I've been dealing with massive DHCP issues in the past week, using the CODA 4582 router, most new devices I connect have issues where I can't reach certain sites, my xbox gives me a DHCP error, and my router stopped working with a DHCP error. Same type of diagnostic was executed, signal check and etc. I've verified that I have internet when plugging my desktop directly to my modem, but I have no connection when going through the router.
Multiple Rogers chats and calls didn't solve it as they said its not their end. I stopped using the router and still have problems, on my 2nd phone that uses just wifi even tiktok is unreachable because of this issue. As I said previously, without Rogers informing anyone, especially 3rd party Router manufacturers, they were doing this, there is no built in support for most devices to handel the loss of IPv4 while still having IPv6. My router is ASUS AC86U. AlphaKilo07 what firmware version is your modem running at the present time? My router log says: WAN_Connection: ISP's DHCP did not function properly. TP-Link United Kingdom (assuming the setup on the TD-W9960 and TD-W9970 are similar). I've spoken with our suppliers and they've fixed the problem for you but I can see your router is trying to connect using the wrong password. If what you found is true then it needs to be addressed properly as we are still paying for Rogers service and expect it to be reliable. I had started another thread regarding a new setup after waking up to an issue with my Asus router this morning (RT-N66U), but while trying to finalize my game plan, I was hoping for some assistance on possibly getting my current router back up and running to get me by. Sometimes for then once a day. WOW - thanks for the explanation! I have an asus RT-AC86U router hooked up to plusnet over fibre. I did get a CODA replacement modem delivered last week.