Western Branch Diesel Charleston Wv
This should sort it for you, but probably worth trying the Plusnet Hub just to check that the connection is working. 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 did not personally ask for any NEW patch to be pushed to my modem manually, I did ask several times before my replacement modem to have the firmware rolled back to a previous verison, but they declined and insisted I try a new CODA device instead. Whenever it tries to connect to the NOW service, I get an error stating "Your ISP's DHCP Does Not Function Properly". For a week it was showing all zeros except for what looked like an IPv6 address in the IP Address field preceded by 0. Then I set up my new router again and everything is solved. Can anyone from Rogers help explain and clarify this here? And a technician will be sent onsite. Getting a little frustrated. 386_41535) and it connected immediately.
I've been having the same problem since mid last week. As already been stated you need to setup the ASUS for PPPoE connection. 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. This all starting to make sense. Re: FTTP - "Your ISP's DHCP does not function properly". Anyone else into the same situation where it started to drop again today? At this moment I don't consider my issue resolved... 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.
Got all hopes up (at least for me) from Thursday to Sunday. I ofund this track on Rogers forum which is related: Thanks. 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. Changing my password and updating on the router (after testing login on the the plusnet support site). I got my modem swapped already (CODA-4582) to another one but no difference so that rules out modem itself. But no amount of factory resetting or rebooting will get a new IPv4 address anymore.....
Does anyone have any ideas as to what might be wrong? Looks like I'm in the same boat. Multiple Rogers chats and calls didn't solve it as they said its not their end. I did get a CODA replacement modem delivered last week. However, if I configure my TP Link as a router with a Sky(MER) profile, it connects immediately. The main part of the issue though, I still believe, is the removal/discontinued use of IPv4 entirely. The config I have in the ASUS is using DHCP Option 61 with a working username and password. After much playing around, it turned out to be an issue with the ASUS firmware. 37, don't recall what it was during the problem week though. Any idea or is/are there any setting you I try. This works for me, not sure if works for you but you can try.
However, I myself am still setup for Automatic IPv4 not Static, and have been ok for the last 48hours.... I'm positive nearly all Rogers Bridgemode users, have their WAN setup for 'Automatic' IPv4, and not for Static IPv4. Hello community, I have recently joined NOW Broadband and am struggling to get my ASUS router working. I'm ready to switch to Bell at this point.
Same, I also changed asus router and suffered this error. 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... I First had the issue with my Xbox not connecting like the first post. I should say I have a tech coming by tomorrow but most of the time they just add a thing to my cable and leave, I hope they take this problem seriously, most of the time it feels like they do a band aid fix and are eager to leave. 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. I've replaced my modem once after noticing it was dropping the IPv4 clients. 19-09-2022 10:46 AM - edited 19-09-2022 10:47 AM. The non-static IPv4 and dual stack IPv6, were the only 2 reasons to stay with Rogers. 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? My router log says: WAN_Connection: ISP's DHCP did not function properly. Were you supplied a Hub Two as part of your FTTP installation? 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. It's almost as if I have an issue with the WAN port.
Simply put, even though my Asus GT AX11000 wifi6, 2. 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. After that I thought I was in the clear (Rogers was pushing something to my modem? ) As long the Internet services is being offered (with CODA-4582) we shouldn't expect this to be normal. Can you log into your router and make sure it's using the account password? 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. Within the last month or so, Rogers has been pushing firmware updates to begin the removal and discontinuation of IPv4 services. You can choose the modulation type of ADSL or VDSL instead, I have VDSL selected. 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. Hardware Version||1A|. 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.
Edited for spelling, sorry if I missed anymore XD. This COULD be one possible part of the issue leading to this problem happening over time, and not always repeating exactly the same way for everyone.... Keep us posted if anyone finds a solution for this. Please refer to our Terms of Service for more information. 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. 5gbps eth, router, that fully supports IPv6 native from ISP..... Resetting the router.
I then re-applied the newest firmware and it's kept the connection. The support team cannot do anything more than look at the problem and see that it's an issue. Switching from Aggresive DHCP to normal mode. I tried forcing IPv4 only but if Rogers is discounting that, no wonder that didn't work.