Project

General

Profile

Actions

Bug #12947

closed

DHCP6 client does not take any action if the interface IPv6 address changes during renewal

Added by David Myers over 2 years ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv6)
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
24.03
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

I recently started using T-Mobile 5G Home Internet. The gateway device you're required to use is almost completely unconfigurable. You can't even change DHCP or DNS settings, forget about having a bridge mode or any sort of DMZ or IP bypass. So for IPv6 I need to use NAT, which actually works pretty well.

The problem is that occasionally the IPv6 address will change without the interface going down. First the Router Advertisements change and NAT and dpinger break. Eventually dhcp6c notices the change but does nothing about it:

Mar 11 03:44:26 router dhcp6c[32738]: Sending Renew
Mar 11 03:44:27 router dhcp6c[32738]: dhcp6c Received INFO
Mar 11 03:44:27 router dhcp6c[32738]: remove an address 2607:fb90:5128:15d0:24dc:4e2:d0b6:df11/128 on igb2
Mar 11 03:44:27 router dhcp6c[32738]: add an address 2607:fb90:5120:e987:24dc:4e2:d0b6:df11/128 on igb2
Mar 11 03:44:27 router dhcp6c[32738]: T1(1125) and/or T2(1800) is locally determined

Manually restarting dpinger and reloading the filters gets things working again, but what probably really needs to happen is to run /etc/rc.newwanipv6.

I'm thinking of patching (the generation of) /var/etc/dhcp6c_opt1_script.sh to run /etc/rc.newwanipv6 if the current interface IPv6 address does not match /var/db/opt1_ipv6 after a DHCPv6 INFO or RENEW. Is this a reasonable short-term fix?


Files

dhcp6c-renew-12947.diff (3.78 KB) dhcp6c-renew-12947.diff Jim Pingle, 03/16/2022 02:36 PM
dhcpd.log (31.7 KB) dhcpd.log David Myers, 03/18/2022 01:59 PM
system.log (884 Bytes) system.log David Myers, 03/18/2022 01:59 PM

Related issues

Related to Regression #11570: Gateway monitoring services is not always restarted on interface events, which may prevent a WAN from recovering back to an online stateClosed

Actions
Actions

Also available in: Atom PDF