OPNsense Forum

English Forums => General Discussion => Topic started by: phunkodelic on September 08, 2025, 02:51:39 PM

Title: IPV6 WAN DHCP Renews itself every 15 minutes --- ISP = Google Fiber.
Post by: phunkodelic on September 08, 2025, 02:51:39 PM
Default setup on my OPNsense Firewall with latest firmware and updates applied.  Google Fiber is my ISP.  Seeing renewals every 15 minutes.  It causes issues every so often where my internet complete drops, or the performance goes to crap.  Only to recover is to bounce the WAN interface.   Reached out to google fiber and they prefer end user equipment to use "lifetime" lease setting.  They also said the leases are for 24 hour time period.  So what are my options or how do I fix this? 
Title: Re: IPV6 WAN DHCP Renews itself every 15 minutes --- ISP = Google Fiber.
Post by: franco on September 08, 2025, 02:57:35 PM
Can you share exact log details and your OPNsense version first. Your instructions are unclear.


Cheers,
Franco
Title: Re: IPV6 WAN DHCP Renews itself every 15 minutes --- ISP = Google Fiber.
Post by: phunkodelic on September 08, 2025, 03:15:29 PM
Seeing this in the logs every 15 minutes along with other DHCP related entries:  dhclient-script: Creating resolv.conf
Firmware Version:  25.7.2

Issue: Internet connectivity dies for clients in my network.   Only to fix it is to bounce/reset the WAN interface.  I need to stop having to manually reset the WAN interface as I should not be losing connectivity. 
Title: Re: IPV6 WAN DHCP Renews itself every 15 minutes --- ISP = Google Fiber.
Post by: franco on September 09, 2025, 08:01:10 AM
dhclient-script is IPv4 and it shouldn't directly impact your IPv6 connectivity.

You may consider enabling IPv6 DHCP debugging under Interfaces: Settings, reboot and taking a look at the logs that "dhcp6c" produces in System: Settings: General.


Cheers,
Franco
Title: Re: IPV6 WAN DHCP Renews itself every 15 minutes --- ISP = Google Fiber.
Post by: phunkodelic on September 09, 2025, 01:15:22 PM
Thanks!  I will give that a try.  It's also happening on IPV4.  I am looking into the hardware side of things as well.  I am running this on a BeeLink EQI4 that's brand new.  Its a mini PC.