I am using a TPLink TD-W9960 as a modem configured in Bridge mode and an ASUS RT-AX86S router. Still trying to digest it and understand it. 5gbps eth, router, that fully supports IPv6 native from ISP..... Changing my password and updating on the router (after testing login on the the plusnet support site). 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... Solved: ASUS RT-AX86S - "Your ISP’s DHCP Does Not Function... - NOW Community. because in Automatic IP, the DHCP should issue a new IPv4 when asked too, not issue the same one... The config I have in the ASUS is using DHCP Option 61 with a working username and password. 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.
Does anyone have any ideas as to what might be wrong? Have a look at: @drFishFlan Plusnet do not use a DHCP type connection on FTTP, so as @markhawkin says you need to set up a PPPoE connection in the router with no VLAN ID configured as that is dealt with in the Openreach ONT. I've unplugged and restarted both the modem and router, checked various cables to see if the specific cable was the issue, as well as verifying with a switch that no connection was happening when connecting the router to the switch. SOLVED] - Router Issue. 37, don't recall what it was during the problem week though. Let me know how it goes. This all starting to make sense. Keep us posted if anyone finds a solution for this. Again, I cannot confirm if a firmware patch was pushed to the modems, or who it was pushed too specifically, or if this was a networked sided change, but it does appear at this moment to be working for myself, no more loss of IPv4 WAN address. Both of these units were fully functioning on Sky Broadband.
Hi and thanks for your response. It happens at random times and certain devices will drop the connection while others will have it. However, if I configure my TP Link as a router with a Sky(MER) profile, it connects immediately. Hello community, I have recently joined NOW Broadband and am struggling to get my ASUS router working. As stated by another user above, IPv4 addresses disappeared to 0. Your isp's dhcp does not function properly according. The options on the TD-W9960 are slightly different as there is no "ISP" option.
It's almost as if I have an issue with the WAN port. Resetting the router. DrFishFlan I don't have Plusnet FTTP but my understanding is that you need PPPoE which doesn't fit with your mention of DHCP. I had been running the latest (3. DHCP Issues in the Past Week - Rogers Community. 19-09-2022 10:46 AM - edited 19-09-2022 10:47 AM. I'm on software version 7. The main part of the issue though, I still believe, is the removal/discontinued use of IPv4 entirely. I'm now double NAT'ing which is less than optimal.
Then I set up my new router again and everything is solved. It seems there is a connection but I am having issues with the DHCP server. I tried forcing IPv4 only but if Rogers is discounting that, no wonder that didn't work. Hardware Version||1A|.
Software Version||7. I have to work tomorrow and this is going to cause me serious problems. I then re-applied the newest firmware and it's kept the connection. It already dropped like 3 times today already since Sunday night. I called the ISP and from ISP, they said modem still connected to "old router", so they reset from their side at your modem. Within the last month or so, Rogers has been pushing firmware updates to begin the removal and discontinuation of IPv4 services. AlphaKilo07 what firmware version is your modem running at the present time? But great summary of what you have found! 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. Edited for spelling, sorry if I missed anymore XD. 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?
Please refer to our Terms of Service for more information. I've never had to deal with this before but it's getting extremely frustrating. 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. Got all hopes up (at least for me) from Thursday to Sunday. I'm surprised you had to make any changes, as coming from Sky I would have expected it to just keep working. As already been stated you need to setup the ASUS for PPPoE connection. None of the above have helped. 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. It looks like the DHCP issue is consistently back. I need to reboot the modem each time to resolve this.
For a week it was showing all zeros except for what looked like an IPv6 address in the IP Address field preceded by 0. Same, I also changed asus router and suffered this error. It's too early to claim the issue is resolved, but it is stable for myself at this time. 386_49599) but downgraded to an older version (3. 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. Multiple Rogers chats and calls didn't solve it as they said its not their end.