Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › Issues with 2D Fibre
mAYH3M

163 posts

Master Geek
+1 received by user: 24


#310647 8-Nov-2023 23:08
Send private message

So my fibre connection had been solid for the last 5-6 months. It suddenly stopped working day before yesterday, apparently there was an issue with Enable.2D rectified the issue but they also moved me to DHCP, I was using PPPoE previously.

 

It's been more than a day on the "upgraded" network but the link feels sluggish with heaps of timeouts. Just checked the log on the router and it constantly renewing WAN dhcp address. Is this normal behaviour?

 

Log from my TP-Link ER7206 Router

 

WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 23:04:10    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 23:04:07    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 23:01:40    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 23:01:37    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:59:10    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:59:07    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:56:41    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:56:37    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:54:10    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:54:07    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:51:40    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:51:37    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:49:10    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:49:07    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:46:39    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:46:36    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:44:09    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:44:06    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:41:39    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:41:35    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:39:08    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:39:05    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:36:38    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:36:35    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:34:08    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:34:05    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:31:39    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:31:35    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:29:08    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:29:05    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:26:37    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:26:34    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:24:07    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:24:04    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:21:37    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:21:34    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:19:08    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:19:04    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:16:37    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:16:34    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:14:07    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:14:04    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:11:37    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:11:34    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:09:08    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:09:04    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:06:37    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:06:34    
WAN: DHCP client renewing IP succeeded. (IP-Address=119.224.59.144, Mask=255.255.255.224, Gateway=119.224.59.129)
Nov 08, 2023 22:04:08    
WAN: DHCP client lease expired. Began renewing the lease.
Nov 08, 2023 22:04:04 

 

 

Create new topic
fe31nz
1294 posts

Uber Geek
+1 received by user: 423


  #3157825 9-Nov-2023 23:37
Send private message

I am still on PPPoE myself, but that log does not look good.  In general, DHCP renewals are done about half way through the lease time, not on expiry.  That is to make sure that the connection is never lost if the renewal fails a few times (for example, if the DHCP server is offline for a while, when it is getting a firmware upgrade).  If that log message is correct, the lease is actually expiring, which means that data will not flow over the connection until the lease is renewed.  And it is expiring at random, very short intervals - DHCP settings are not normally changed between renewals, so the expiry time ought to be exactly the same each time.  I have no idea what 2degrees would be setting for a lease time, but it is extremely unlikely to be less than a minute.  Hours or days would be more normal.  So there is clearly something really bad going on there.

 

To find out exactly where the problem is (at the 2degrees end or your router), you would need to be able to capture the DHCP traffic on the router WAN port and analyse it.  A very quick search did not find any way to do that on the TP-Link ER7206 router, but I might have missed it.  If it is not possible, the other way to do it requires that you have an Ethernet switch with VLAN capability and three spare ports and the ability to mirror traffic from one port to another.  You would set up a new VLAN on the switch used on two of the ports and plug one of those ports into the ONT and the other into the router WAN port.  Then have the one going into the router WAN port mirrored to the remaining spare port, and use a PC (laptop?) connected to that port to run Wireshark (or tcpdump or tshark) and set Wireshark to capture all the DHCP traffic.

 

Another thing to try is to just directly connect a computer to the ONT port and get it to connect directly (with the right settings on it Ethernet port).  If it has the same problems as the router, then it is a 2degrees problem.  And you can use Wireshark to capture the DHCP traffic to prove to 2degrees that is their problem.



mAYH3M

163 posts

Master Geek
+1 received by user: 24


  #3158621 12-Nov-2023 13:15
Send private message

2D is looking into it as the problem as it started after having a stable connection for nearly 6 months.

 

Router is connected to directly to the ONT and I have used the same gear since late 2020 with a few providers.

Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.


Updates »

Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.








RSS feeds
Main feed
Forums feed
Copyright
©2002-2026 Geekzone®
Site features
Geekzone BI dashboard
Geekzone Badges
Geekzone Status Page

 

Site Information
Subscribe to Geekzone
Privacy Statement
Forum Usage Guidelines (FUG)
Advertising
Trademark and copyright