OPNsense Forum

Hi all,
Since 23.1 update, I have an error every day. Default IPv4 route drop every 24h when my WAN interface renew this DHCP lease.
I'm using this config : https://docs.opnsense.org/manual/how-tos/orange_fr_fttp.html for Orange FTTH provider (in France).
I tried to reinstall and reimport my config, and recreating the VLAN interface from scratch, but without any difference.

I see these logs related to dhcp.

<27>1 2023-02-06T11:04:09+01:00 opnsense.xxx dhclient 61916 - [meta sequenceId="1"] unknown dhcp option value 0x5a
<27>1 2023-02-06T11:04:09+01:00 opnsense.xxx dhclient 61916 - [meta sequenceId="2"] unknown dhcp option value 0x7d
<27>1 2023-02-06T11:04:11+01:00 opnsense.xxx dhclient 61916 - [meta sequenceId="3"] unknown dhcp option value 0x5a
<27>1 2023-02-06T11:04:11+01:00 opnsense.xxx dhclient 61916 - [meta sequenceId="4"] unknown dhcp option value 0x7d
<13>1 2023-02-06T11:04:11+01:00 opnsense.xxx dhclient 37422 - [meta sequenceId="5"] New IP Address (vlan0.832): 83.202.xx.xx
<13>1 2023-02-06T11:04:11+01:00 opnsense.xxx dhclient 39678 - [meta sequenceId="6"] New Subnet Mask (vlan0.832): 255.255.248.0
<13>1 2023-02-06T11:04:11+01:00 opnsense.xxx dhclient 42657 - [meta sequenceId="7"] New Broadcast Address (vlan0.832): 83.202.xx.255
<13>1 2023-02-06T11:04:11+01:00 opnsense.xxx dhclient 44227 - [meta sequenceId="8"] New Routers (vlan0.832): 83.202.xx.1
<13>1 2023-02-06T11:04:11+01:00 opnsense.xxx dhclient 49809 - [meta sequenceId="9"] Creating resolv.conf
<13>1 2023-02-06T11:04:11+01:00 opnsense.xxx opnsense 66635 - [meta sequenceId="10"] /usr/local/etc/rc.newwanip: No IP change detected for WAN[wan]


DHCP lease got from my ISP is for 24h, but when renewing, it seems that the routes related to this link is drop off.
I need, to fix it, to do one of this step :
- manually add default route
- click to renew dhcp lease
- unplug/replug the network cable

IPv6 have no issue, but the DHCP6 lease seems to be longer than the IPv4 one.

I dont find more detailed logs...
Is someone have the same behaviour ? I didnt seen an issue on github.
Thanks

I see 2 files used when dhcp renew an IP

https://github.com/opnsense/core/blob/master/src/etc/rc.newwanip
https://github.com/opnsense/core/blob/master/src/opnsense/scripts/interfaces/dhclient-script
Both have multiple changes between 22.7 and 23.1, regarding the way they manage ips, routes, etc...
I dont understand why my route is removed during the process.
I suppose that a few instants, interface is down, so the system remove the route, and as the new IP is the same than the old, the 2 scripts didnt recreate the route.
But I cant confirm that, and why it seems I'm the only one to have this issue ?

The setup seems classic for a public FAI, a dhclient on interface with vlan (and some custom options but probably not related).

Is there a way to track all route changes ?

Hello,

I have the same problem losing the default route but only in IPv6.
In IPv4, the WAN interface is configured as static IP.

https://forum.opnsense.org/index.php?topic=32263

Hmm, that sounds similar to my issue https://forum.opnsense.org/index.php?topic=32439.0 (https://forum.opnsense.org/index.php?topic=32439.0). Is there a way to trigger the issue?

This is also similar to an issue I am having after upgrading to 23.1. My WAN has no special configuration, just DHCP for IPv4 and IPv6.

Approx. every 24 hours the default IPv4 route vanishes. A reboot of opnsense or disabling and reenabling the IPv4 gateway brings it back and restores connectivity. Haven't found anything useful in the logs yet.

I have found several similar complaints from other users about this behavior after the 23.1 upgrade, but no resolutions.

Hmm, so I wonder who is dropping the default route here? dhclient-script was changed to not touch it a while ago. Could it be that no actual route is being pushed by the DHCP server and it is only sending static routes?

Could someone post their # cat /var/db/dhclient.leases.* file?


Thanks,
Franco

PS: we need a little more logging prior to the renew and the infamous "No IP change detected for WAN[wan]"

Here's the contents, thanks:

root@OPNsense:~ # cat /var/db/dhclient.leases.igb0
lease {
  interface "igb0";
  fixed-address 209.xxx.xxx.218;
  option subnet-mask 255.255.255.0;
  option routers 209.xxx.xxx.1;
  option domain-name-servers 209.206.64.138,209.206.64.246;
  option host-name "xxxxxxxx";
  option domain-name "elevatefiber.com";
  option dhcp-lease-time 7200;
  option dhcp-message-type 5;
  option dhcp-server-identifier 172.20.99.46;
  renew 4 2023/2/16 13:25:05;
  rebind 4 2023/2/16 14:10:05;
  expire 4 2023/2/16 14:25:05;
}
lease {
  interface "igb0";
  fixed-address 209.xxx.xxx.218;
  option subnet-mask 255.255.255.0;
  option routers 209.xxx.xxx.1;
  option domain-name-servers 209.206.64.138,209.206.64.246;
  option host-name "xxxxxxxx";
  option domain-name "elevatefiber.com";
  option dhcp-lease-time 7200;
  option dhcp-message-type 5;
  option dhcp-server-identifier 172.20.99.46;
  renew 4 2023/2/16 14:17:00;
  rebind 4 2023/2/16 15:02:00;
  expire 4 2023/2/16 15:17:00;
}
lease {
  interface "igb0";
  fixed-address 209.xxx.xxx.218;
  option subnet-mask 255.255.255.0;
  option routers 209.xxx.xxx.1;
  option domain-name-servers 209.206.64.138,209.206.64.246;
  option host-name "xxxxxxxx";
  option domain-name "elevatefiber.com";
  option dhcp-lease-time 7200;
  option dhcp-message-type 5;
  option dhcp-server-identifier 172.20.99.46;
  renew 4 2023/2/16 16:07:55;
  rebind 4 2023/2/16 16:52:55;
  expire 4 2023/2/16 17:07:55;
}
lease {
  interface "igb0";
  fixed-address 209.xxx.xxx.218;
  option subnet-mask 255.255.255.0;
  option routers 209.xxx.xxx.1;
  option domain-name-servers 209.206.64.138,209.206.64.246;
  option host-name "xxxxxxxx";
  option domain-name "elevatefiber.com";
  option dhcp-lease-time 7200;
  option dhcp-message-type 5;
  option dhcp-server-identifier 172.20.99.46;
  renew 4 2023/2/16 18:01:20;
  rebind 4 2023/2/16 18:46:20;
  expire 4 2023/2/16 19:01:20;
}


Quote from: debacler on February 16, 2023, 03:34:27 PM
This is also similar to an issue I am having after upgrading to 23.1. My WAN has no special configuration, just DHCP for IPv4 and IPv6.

Approx. every 24 hours the default IPv4 route vanishes. A reboot of opnsense or disabling and reenabling the IPv4 gateway brings it back and restores connectivity. Haven't found anything useful in the logs yet.

I have found several similar complaints from other users about this behavior after the 23.1 upgrade, but no resolutions.

I wonder if the root cause of this issue related to an issue I described: https://forum.opnsense.org/index.php?topic=32490.0

Hi,
That's my dhcp lease db
lease {
  interface "vlan0.832";
  fixed-address 83.xx.xx.96;
  next-server 80.10.247.48;
  option subnet-mask 255.255.248.0;
  option routers 83.xx.xx.1;
  option domain-name-servers 80.10.246.1,81.253.149.9;
  option domain-name "orange.fr";
  option broadcast-address 83.xx.xx.255;
  option dhcp-lease-time 259200;
  option dhcp-message-type 5;
  option dhcp-server-identifier 80.10.247.48;
  option dhcp-renewal-time 84600;
  option dhcp-rebinding-time 207400;
  option option-90 0:0:0:0:0:0:0:0:0:0:0:64:68:63:70:6c:69:76:65:62:6f:78:xxx;
  option domain-search "MSR.access.orange-multimedia.net.";
  option option-125 0:0:5:58:c:1:a:0:1:0:0:0:ff:ff:ff:ff:ff;
  renew 1 2023/2/13 14:45:33;
  rebind 2 2023/2/14 08:23:03;
  expire 3 2023/2/15 15:15:33;
}
lease {
  interface "vlan0.832";
  fixed-address 83.xx.xx.96;
  next-server 80.10.247.48;
  option subnet-mask 255.255.248.0;
  option routers 83.xx.xx.1;
  option domain-name-servers 80.10.246.1,81.253.149.9;
  option domain-name "orange.fr";
  option broadcast-address 83.xx.xx.255;
  option dhcp-lease-time 259200;
  option dhcp-message-type 5;
  option dhcp-server-identifier 80.10.247.48;
  option dhcp-renewal-time 84600;
  option dhcp-rebinding-time 207400;
  option option-90 0:0:0:0:0:0:0:0:0:0:0:64:68:63:70:6c:69:76:65:62:6f:78:xxx;
  option domain-search "MSR.access.orange-multimedia.net.";
  option option-125 0:0:5:58:c:1:a:0:1:0:0:0:ff:ff:ff:ff:ff;
  renew 1 2023/2/13 14:46:08;
  rebind 2 2023/2/14 08:23:38;
  expire 3 2023/2/15 15:16:08;
}
lease {
  interface "vlan0.832";
  fixed-address 83.xx.xx.96;
  next-server 80.10.247.175;
  option subnet-mask 255.255.248.0;
  option routers 83.xx.xx.1;
  option domain-name-servers 80.10.246.1,81.253.149.9;
  option domain-name "orange.fr";
  option broadcast-address 83.xx.xx.255;
  option dhcp-lease-time 259200;
  option dhcp-message-type 5;
  option dhcp-server-identifier 80.10.247.175;
  option dhcp-renewal-time 77562;
  option dhcp-rebinding-time 207400;
  option option-90 0:0:0:0:0:0:0:0:0:0:0:64:68:63:70:6c:69:76:65:62:6f:78:xxx;
  option domain-search "MSR.access.orange-multimedia.net.";
  option option-125 0:0:5:58:c:1:a:0:1:0:0:0:ff:ff:ff:ff:ff;
  renew 4 2023/2/16 12:48:53;
  rebind 5 2023/2/17 04:58:21;
  expire 6 2023/2/18 15:16:11;
}
lease {
  interface "vlan0.832";
  fixed-address 83.xx.xx.96;
  next-server 80.10.247.175;
  option subnet-mask 255.255.248.0;
  option routers 83.xx.xx.1;
  option domain-name-servers 80.10.246.1,81.253.149.9;
  option domain-name "orange.fr";
  option broadcast-address 83.xx.xx.255;
  option dhcp-lease-time 259200;
  option dhcp-message-type 5;
  option dhcp-server-identifier 80.10.247.175;
  option dhcp-renewal-time 79029;
  option dhcp-rebinding-time 207400;
  option option-90 0:0:0:0:0:0:0:0:0:0:0:64:68:63:70:6c:69:76:65:62:6f:78:xxx;
  option domain-search "MSR.access.orange-multimedia.net.";
  option option-125 0:0:5:58:c:1:a:0:1:0:0:0:ff:ff:ff:ff:ff;
  renew 5 2023/2/17 10:46:04;
  rebind 6 2023/2/18 03:13:54;
  expire 0 2023/2/19 12:48:55;
}

And the last renew was :
<27>1 2023-02-16T13:48:53+01:00 opnsense.local dhclient 22 - [meta sequenceId="1"] unknown dhcp option value 0x5a
<27>1 2023-02-16T13:48:53+01:00 opnsense.local dhclient 22 - [meta sequenceId="2"] unknown dhcp option value 0x7d
<27>1 2023-02-16T13:48:55+01:00 opnsense.local dhclient 22 - [meta sequenceId="3"] unknown dhcp option value 0x5a
<27>1 2023-02-16T13:48:55+01:00 opnsense.local dhclient 22 - [meta sequenceId="4"] unknown dhcp option value 0x7d
<13>1 2023-02-16T13:48:55+01:00 opnsense.local dhclient 25784 - [meta sequenceId="5"] New IP Address (vlan0.832): 83.xx.xx.96
<13>1 2023-02-16T13:48:55+01:00 opnsense.local dhclient 27363 - [meta sequenceId="6"] New Subnet Mask (vlan0.832): 255.255.248.0
<13>1 2023-02-16T13:48:55+01:00 opnsense.local dhclient 29780 - [meta sequenceId="7"] New Broadcast Address (vlan0.832): 83.xx.xx.255
<13>1 2023-02-16T13:48:55+01:00 opnsense.local dhclient 31258 - [meta sequenceId="8"] New Routers (vlan0.832): 83.xx.xx.1
<13>1 2023-02-16T13:48:55+01:00 opnsense.local dhclient 36866 - [meta sequenceId="9"] Creating resolv.conf
<13>1 2023-02-16T13:48:55+01:00 opnsense.local opnsense 53565 - [meta sequenceId="10"] /usr/local/etc/rc.newwanip: No IP change detected for WAN[wan]


I also have these files with the correct ip/values
# ls /tmp/vlan0.832_*
/tmp/vlan0.832_nameserver /tmp/vlan0.832_oldipv6 /tmp/vlan0.832_router
/tmp/vlan0.832_oldip /tmp/vlan0.832_prefixv6 /tmp/vlan0.832_searchdomain


@skool, what are the last couple of lines before this one?

<27>1 2023-02-16T13:48:53+01:00 opnsense.local dhclient 22 - [meta sequenceId="1"] unknown dhcp option value 0x5a


thanks so far!

@franco
I'm looking on /var/log/system/system_xxx.log file
previous lines are older and not related

<13>1 2023-02-16T11:50:39+01:00 opnsense.local flowd_aggregate.py 67247 - [meta sequence
Id="11"] vacuum interface_086400.sqlite
<13>1 2023-02-16T11:50:39+01:00 opnsense.local flowd_aggregate.py 67247 - [meta sequence
Id="12"] vacuum done
<27>1 2023-02-16T13:48:53+01:00 opnsense.local dhclient 22 - [meta sequenceId="1"] unknown dhcp option value 0x5a
<27>1 2023-02-16T13:48:53+01:00 opnsense.local dhclient 22 - [meta sequenceId="2"] unknown dhcp option value 0x7d


I can add locally some debug in files, if relevant.
But as I just renewed my IP (at 11:46:04), I need to wait for tomorrow to have new logs :/

Thanks, the absence of further logs seems odd to me considering the default route is gone, but that doesn't mean too much. I would have just suspected the code tripping over itself here.

Once this bad state is entered, can you run the following to see if that fixes it?

# /usr/local/etc/rc.routing_configure

The lease information looks normal and how I would expect it to be fairly similar to test setups here.


Cheers,
Franco

Hi Franco,

tested this morning :

root@opnsense:~ # route show default
route: route has not been found
root@opnsense:~ # /usr/local/etc/rc.routing_configure
Setting up routes...done.
Setting up gateway monitors...done.
Configuring firewall.......done.
root@opnsense:~ # route show default
   route to: default
destination: default
       mask: default
    gateway: lfbn-idf2-1-158-1.w83-202.abo.wanadoo.fr
        fib: 0
  interface: vlan0.832
      flags: <UP,GATEWAY,DONE,STATIC>
recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire
       0         0         0         0      1500         1         0


So this brings back a working state until the next renew?


Cheers,
Franco

Quote from: franco on February 20, 2023, 09:20:51 AM
So this brings back a working state until the next renew?

Yes, the script re-add the missing default route with the right gateway, until next renew where the gateway drops.

Thanks, I will try to reproduce this in the lab later today.


Cheers,
Franco

Hi!
I still have the issue with OPNsense 23.1.1_2-amd64 in strange intervals.  It always happens after several hours (probably 4 since the lease time is 28800?) of my cable modem being off. For some reason the default route is lost. Probably I know, why it is not reestablished:
<13>1 2023-02-21T06:23:10+01:00 OPNsense.lan opnsense 33755 - [meta sequenceId="6"] /usr/local/etc/rc.newwanip: No IP change detected for WAN[wan]
/usr/local/etc/rc.routing_configure fixes the issue also for me.

Ok, so here is a temporary workaround and a debug change to see more of what is going on inside dhclient-script:

https://github.com/opnsense/core/commit/26d26e2054

# opnsense-patch 26d26e2054

Can you guys apply and see if it behaves better? I still need the log output produced by "dhclient" from the general log.


Thanks,
Franco

Hi!

Quote from: franco on February 21, 2023, 09:11:37 AM
Can you guys apply and see if it behaves better? I still need the log output produced by "dhclient" from the general log.

Thanks for the patch, I have applied it this morning. It will take a few days till I can be sure that it had effect. I'll report back.

Here is the log you requested:

2023-02-22T06:24:22 Notice opnsense /usr/local/etc/rc.newwanip: No IP change detected for WAN[wan]
2023-02-22T06:24:22 Notice dhclient Creating resolv.conf
2023-02-22T06:24:22 Notice dhclient New Routers (vtnet2): 81.xxx.xx.1
2023-02-22T06:24:22 Notice dhclient New Broadcast Address (vtnet2): 81.xxx.xx.255
2023-02-22T06:24:22 Notice dhclient New Subnet Mask (vtnet2): 255.255.255.0
2023-02-22T06:24:22 Notice dhclient New IP Address (vtnet2): 81.xxx.xx.x29
2023-02-22T05:19:49 Error dhclient send_packet: No route to host
2023-02-22T04:57:12 Error dhclient send_packet: No route to host
2023-02-22T04:33:03 Error dhclient send_packet: No route to host

I do not know if relevant, but I'm running in a virtualized environment, so the WAN interface does not go down when my cable modem is off.

Thanks, I'd love to see the debug output from the patch here to confirm, but i could also produce a similar lab condition: dhclient-script removes the main address from the interfaces and adds it back which causes the attached default route to disappear. I'm unsure when this behaviour started (FreeBSD 13 has produced more funky  problems around route setup as we've seen last year already) but perhaps we just deconstructed so much scripting that we are now at the breaking point regarding kernel and client capabilities.

https://github.com/opnsense/core/commit/90f1d1d766

# opnsense-revert opnsense && opnsense-patch 90f1d1d766


Cheers,
Franco

Quote from: franco on February 22, 2023, 08:26:48 AM
...perhaps we just deconstructed so much scripting that we are now at the breaking point regarding kernel and client capabilities.
...
Cheers,
Franco

I've been reading this over and over again, but can't get what you are trying to say here. Heidegger? Derrida? :-D

I'm not well-versed in philosophy ;)

The point is we have been removing race conditions, layered scripting and false assumptions from the interface code over the years to see it shrink and provide more consistent/deterministic results which ideally cause fewer bugs in the long run.

The DHCP scripting in particular lost a considerable amount of additions in 23.1 surfacing the default route bug: dhclient-script removes the same IP address and the kernel scrubs the default route because of it. That didn't matter when dhclient-script created a default route which it now cannot (22.7) in order to not break multi-WAN edge cases and on 23.1 the routing configuration was "clever" about not reloading when the IP was still the same from DHCP but missed a reload because it was defunct as per dhclient-script behaviour.


Cheers,
Franco

Hi!

Quote from: franco on February 22, 2023, 08:26:48 AM
Thanks, I'd love to see the debug output from the patch here to confirm,

Ok, sorry, here is the log from this morning with patch 26d26e2054:


2023-02-23T06:24:26 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_DHCP))
2023-02-23T06:24:26 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_DHCP)
2023-02-23T06:24:26 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 81.xxx.xx.1
2023-02-23T06:24:26 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to wan
2023-02-23T06:24:26 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'wan'
2023-02-23T06:24:26 Notice opnsense /usr/local/etc/rc.newwanip: No IP change detected for WAN[wan]
2023-02-23T06:24:26 Notice dhclient Creating resolv.conf
2023-02-23T06:24:26 Notice dhclient New Routers (vtnet2): 81.xxx.xx.1
2023-02-23T06:24:26 Notice dhclient New Broadcast Address (vtnet2): 81.xxx.xx.255
2023-02-23T06:24:26 Notice dhclient New Subnet Mask (vtnet2): 255.255.255.0
2023-02-23T06:24:26 Notice dhclient New IP Address (vtnet2): 81.xxx.xx.x29
2023-02-23T06:24:26 Notice dhclient DEBUG calling add_new_address/add_new_routes
2023-02-23T06:24:26 Notice dhclient DEBUG alias_ip_address:
2023-02-23T06:24:26 Notice dhclient DEBUG new_ip_address: 81.xxx.xx.x29
2023-02-23T06:24:26 Notice dhclient DEBUG new_ip_address: 81.xxx.xx.x29
2023-02-23T06:24:26 Notice dhclient DEBUG old_ip_address: 81.xxx.xx.x29
2023-02-23T06:24:26 Notice dhclient DEBUG entering with BOUND
2023-02-23T05:24:07 Error dhclient send_packet: No route to host
2023-02-23T05:23:27 Error dhclient send_packet: No route to host
2023-02-23T05:22:49 Error dhclient send_packet: No route to host


Default route is still here, but I'm not 100% sure as the issue did not occur everyday on my setup. Do you want me to apply patch 90f1d1d766 or should I wait still for some days to be more sure?

Thanks!

Thanks a lot for this snippet!

I can now confirm the default route disappears when you add an existing address to the interface via ifconfig and i'm a bit baffled why that is since nothing changes except it's being treated as a new address "removing" the old and attached routes.

I think the fix still applies, feel free to try it now:

# opnsense-revert opnsense && opnsense-patch 90f1d1d766


Cheers,
Franco

You're welcome, thanks for the help, the error was pretty annoying as it needed admin rights to fix the Internet. ;)
New patch applied, I will report back in a few days.

Patch log is fine, thanks a lot for your help. From your previous snippet I can already see that the former workaround also addressed the missing route issue and I guess you had no problems with that patch applied?

I tested old images 21.7 and 22.1 for the default route removal behaviour on ifconfig and it seems all old versions react the same so I guess we are at the bottom of the barrel in terms of which DHCP reload behaviour is needed at which point in time.


Cheers,
Franco

Hi,

I tested the 2 patches (with a revert between us, of course).

The first one, yesterday, didnt break (or repaired very fast) the route

<27>1 2023-02-22T13:11:20+01:00 opnsense.local dhclient 28555 - [meta sequenceId="1"] unknown dhcp option value 0x5a
<27>1 2023-02-22T13:11:20+01:00 opnsense.local dhclient 28555 - [meta sequenceId="2"] unknown dhcp option value 0x7d
<27>1 2023-02-22T13:11:22+01:00 opnsense.local dhclient 28555 - [meta sequenceId="3"] unknown dhcp option value 0x5a
<27>1 2023-02-22T13:11:22+01:00 opnsense.local dhclient 28555 - [meta sequenceId="4"] unknown dhcp option value 0x7d
<13>1 2023-02-22T13:11:22+01:00 opnsense.local dhclient 89570 - [meta sequenceId="5"] DEBUG entering with BOUND
<13>1 2023-02-22T13:11:22+01:00 opnsense.local dhclient 91976 - [meta sequenceId="6"] DEBUG old_ip_address:
<13>1 2023-02-22T13:11:22+01:00 opnsense.local dhclient 94043 - [meta sequenceId="7"] DEBUG new_ip_address: 83.xx.xx.96
<13>1 2023-02-22T13:11:22+01:00 opnsense.local dhclient 96031 - [meta sequenceId="8"] DEBUG alias_ip_address:
<13>1 2023-02-22T13:11:22+01:00 opnsense.local dhclient 98298 - [meta sequenceId="9"] DEBUG calling add_new_address/add_new_routes
<13>1 2023-02-22T13:11:22+01:00 opnsense.local dhclient 1724 - [meta sequenceId="10"] New IP Address (vlan0.832): 83.xx.xx.96
<13>1 2023-02-22T13:11:22+01:00 opnsense.local dhclient 4138 - [meta sequenceId="11"] New Subnet Mask (vlan0.832): 255.255.248.0
<13>1 2023-02-22T13:11:22+01:00 opnsense.local dhclient 7308 - [meta sequenceId="12"] New Broadcast Address (vlan0.832): 83.xx.xx.255
<13>1 2023-02-22T13:11:22+01:00 opnsense.local dhclient 10603 - [meta sequenceId="13"] New Routers (vlan0.832): 83.xx.xx.1
<13>1 2023-02-22T13:11:22+01:00 opnsense.local dhclient 14370 - [meta sequenceId="14"] Creating resolv.conf
<13>1 2023-02-22T13:11:22+01:00 opnsense.local opnsense 31227 - [meta sequenceId="15"] /usr/local/etc/rc.newwanip: No IP change detected for WAN[wan]
<13>1 2023-02-22T13:11:22+01:00 opnsense.local opnsense 31227 - [meta sequenceId="16"] /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'wan'
<13>1 2023-02-22T13:11:22+01:00 opnsense.local opnsense 31227 - [meta sequenceId="17"] /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to wan
<13>1 2023-02-22T13:11:22+01:00 opnsense.local opnsense 31227 - [meta sequenceId="18"] /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 83.xx.xx.1
<13>1 2023-02-22T13:11:23+01:00 opnsense.local opnsense 31227 - [meta sequenceId="19"] /usr/local/etc/rc.newwanip: ROUTING: IPv6 default gateway set to wan
<13>1 2023-02-22T13:11:23+01:00 opnsense.local opnsense 31227 - [meta sequenceId="20"] /usr/local/etc/rc.newwanip: ROUTING: skipping IPv6 default route
<13>1 2023-02-22T13:11:23+01:00 opnsense.local opnsense 31227 - [meta sequenceId="21"] /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_DHCP6)
<13>1 2023-02-22T13:11:23+01:00 opnsense.local opnsense 31227 - [meta sequenceId="22"] /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_DHCP6))
<13>1 2023-02-22T13:11:23+01:00 opnsense.local opnsense 31227 - [meta sequenceId="23"] /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_DHCP)
<13>1 2023-02-22T13:11:23+01:00 opnsense.local opnsense 31227 - [meta sequenceId="24"] /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_DHCP))


But the second patch didnt worked for me, I needed to recreate my default route (with the script)

<27>1 2023-02-23T11:38:41+01:00 opnsense.local dhclient 28555 - [meta sequenceId="1"] unknown dhcp option value 0x5a
<27>1 2023-02-23T11:38:41+01:00 opnsense.local dhclient 28555 - [meta sequenceId="2"] unknown dhcp option value 0x7d
<27>1 2023-02-23T11:38:43+01:00 opnsense.local dhclient 28555 - [meta sequenceId="3"] unknown dhcp option value 0x5a
<27>1 2023-02-23T11:38:43+01:00 opnsense.local dhclient 28555 - [meta sequenceId="4"] unknown dhcp option value 0x7d
<13>1 2023-02-23T11:38:43+01:00 opnsense.local dhclient 99899 - [meta sequenceId="5"] New IP Address (vlan0.832): 83.xx.xx.96
<13>1 2023-02-23T11:38:43+01:00 opnsense.local dhclient 1486 - [meta sequenceId="6"] New Subnet Mask (vlan0.832): 255.255.248.0
<13>1 2023-02-23T11:38:43+01:00 opnsense.local dhclient 4127 - [meta sequenceId="7"] New Broadcast Address (vlan0.832): 83.xx.xx.255
<13>1 2023-02-23T11:38:43+01:00 opnsense.local dhclient 5941 - [meta sequenceId="8"] New Routers (vlan0.832): 83.xx.xx.1
<13>1 2023-02-23T11:38:43+01:00 opnsense.local dhclient 12505 - [meta sequenceId="9"] Creating resolv.conf
<13>1 2023-02-23T11:39:28+01:00 opnsense.local opnsense 50563 - [meta sequenceId="10"] /usr/local/etc/rc.routing_configure: ROUTING: entering configure using defaults
<13>1 2023-02-23T11:39:28+01:00 opnsense.local opnsense 50563 - [meta sequenceId="11"] /usr/local/etc/rc.routing_configure: ROUTING: IPv4 default gateway set to wan
<13>1 2023-02-23T11:39:28+01:00 opnsense.local opnsense 50563 - [meta sequenceId="12"] /usr/local/etc/rc.routing_configure: ROUTING: setting IPv4 default route to 83.xx.xx.1
<13>1 2023-02-23T11:39:28+01:00 opnsense.local opnsense 50563 - [meta sequenceId="13"] /usr/local/etc/rc.routing_configure: ROUTING: IPv6 default gateway set to wan
<13>1 2023-02-23T11:39:28+01:00 opnsense.local opnsense 50563 - [meta sequenceId="14"] /usr/local/etc/rc.routing_configure: ROUTING: skipping IPv6 default route
<13>1 2023-02-23T11:39:28+01:00 opnsense.local opnsense 50563 - [meta sequenceId="15"] /usr/local/etc/rc.routing_configure: plugins_configure monitor (1,)
<13>1 2023-02-23T11:39:28+01:00 opnsense.local opnsense 50563 - [meta sequenceId="16"] /usr/local/etc/rc.routing_configure: plugins_configure monitor (execute task : dpinger_configure_do(1,))


I didnt had time to debug the renew today (I was on a visio meeting), but the log says that it set the gateway, but when doing a `route show default`, there was no default route.

Hi! I'm @Threefish4096 on GitHub, with this revert and patch i'm ok!

Quote from: franco on February 23, 2023, 08:05:58 AM
Thanks a lot for this snippet!

I can now confirm the default route disappears when you add an existing address to the interface via ifconfig and i'm a bit baffled why that is since nothing changes except it's being treated as a new address "removing" the old and attached routes.

I think the fix still applies, feel free to try it now:

# opnsense-revert opnsense && opnsense-patch 90f1d1d766


Cheers,
Franco

Hi,

I have exactly the same problem and notice the same symptoms every day or a lot less sometimes (same Orange operator as the OP).

I'll give a try to your patch too to give you feedback.

Thank you for your help.

Quote from: franco on February 21, 2023, 09:11:37 AM
Ok, so here is a temporary workaround and a debug change to see more of what is going on inside dhclient-script:

https://github.com/opnsense/core/commit/26d26e2054

# opnsense-patch 26d26e2054

Sorry no log, but it seems to have solved the problem on my side.

sudo opnsense-patch 26d26e2054

For me works better, but disconnect furthermore for short time!
No IP change but broke connection

2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GLASFASER_DHCP))
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GLASFASER_DHCP)
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GLASFASER_DHCP6))
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GLASFASER_DHCP6)
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: keeping current default gateway 'fe80::ff:XXXX:202%vtnet0'
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv6 default route to fe80::ff:XXXX:202
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv6 default gateway set to opt4
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 100.111.0.1
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to opt4
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'opt4'
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: No IP change detected for wan[opt4]
2023-02-23T20:43:49 Notice dhclient Creating resolv.conf
2023-02-23T20:43:49 Notice dhclient New Routers (vtnet0): 100.111.0.1
2023-02-23T20:43:49 Notice dhclient New Broadcast Address (vtnet0): 100.111.255.255
2023-02-23T20:43:49 Notice dhclient New Subnet Mask (vtnet0): 255.255.0.0
2023-02-23T20:43:49 Notice dhclient New IP Address (vtnet0): 100.111.1XX.83
2023-02-23T20:43:49 Notice dhclient DEBUG calling add_new_address/add_new_routes
2023-02-23T20:43:49 Notice dhclient DEBUG alias_ip_address:
2023-02-23T20:43:49 Notice dhclient DEBUG new_ip_address: 100.111.1XX.83
2023-02-23T20:43:49 Notice dhclient DEBUG old_ip_address: 100.111.1XX.83
2023-02-23T20:43:49 Notice dhclient DEBUG entering with BOUND
2023-02-23T20:43:00 Notice send_telemetry.py telemetry data collected 1 records in 0.04 seconds @2023-02-23 19:42:43.193093
2023-02-23T20:11:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-23 19:10:53.646493
2023-02-23T19:42:30 Notice dhclient Creating resolv.conf
2023-02-23T19:42:30 Notice dhclient DEBUG alias_ip_address:
2023-02-23T19:42:30 Notice dhclient DEBUG new_ip_address: 100.111.1XX.83
2023-02-23T19:42:30 Notice dhclient DEBUG old_ip_address: 100.111.1XX.83
2023-02-23T19:42:30 Notice dhclient DEBUG entering with RENEW
2023-02-23T18:47:11 Notice dhclient Creating resolv.conf
2023-02-23T18:47:11 Notice dhclient DEBUG alias_ip_address:
2023-02-23T18:47:11 Notice dhclient DEBUG new_ip_address: 100.111.1XX.83
2023-02-23T18:47:11 Notice dhclient DEBUG old_ip_address: 100.111.1XX.83
2023-02-23T18:47:11 Notice dhclient DEBUG entering with RENEW
2023-02-23T18:16:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-23 17:15:07.410136
2023-02-23T17:53:54 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GLASFASER_DHCP))
2023-02-23T17:53:54 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GLASFASER_DHCP)
2023-02-23T17:53:54 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GLASFASER_DHCP6))
2023-02-23T17:53:54 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GLASFASER_DHCP6)
2023-02-23T17:53:54 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: keeping current default gateway 'fe80::ff:XXXX:202%vtnet0'
2023-02-23T17:53:54 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv6 default route to fe80::ff:XXXX:202
2023-02-23T17:53:54 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv6 default gateway set to opt4
2023-02-23T17:53:54 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 100.111.0.1
2023-02-23T17:53:54 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to opt4
2023-02-23T17:53:54 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'opt4'
2023-02-23T17:53:54 Notice opnsense /usr/local/etc/rc.newwanip: No IP change detected for wan[opt4]
2023-02-23T17:53:54 Notice dhclient Creating resolv.conf
2023-02-23T17:53:54 Notice dhclient New Routers (vtnet0): 100.111.0.1
2023-02-23T17:53:54 Notice dhclient New Broadcast Address (vtnet0): 100.111.255.255
2023-02-23T17:53:54 Notice dhclient New Subnet Mask (vtnet0): 255.255.0.0
2023-02-23T17:53:54 Notice dhclient New IP Address (vtnet0): 100.111.1XX.83
2023-02-23T17:53:54 Notice dhclient DEBUG calling add_new_address/add_new_routes
2023-02-23T17:53:54 Notice dhclient DEBUG alias_ip_address:
2023-02-23T17:53:54 Notice dhclient DEBUG new_ip_address: 100.111.1XX.83
2023-02-23T17:53:54 Notice dhclient DEBUG old_ip_address:
2023-02-23T17:53:54 Notice dhclient DEBUG entering with BOUND
2023-02-23T16:52:23 Notice dhclient Creating resolv.conf
2023-02-23T16:52:23 Notice dhclient DEBUG alias_ip_address:
2023-02-23T16:52:23 Notice dhclient DEBUG new_ip_address: 100.111.1XX.83
2023-02-23T16:52:23 Notice dhclient DEBUG old_ip_address: 100.111.1XX.83
2023-02-23T16:52:23 Notice dhclient DEBUG entering with RENEW
2023-02-23T15:57:05 Notice dhclient Creating resolv.conf
2023-02-23T15:57:05 Notice dhclient DEBUG alias_ip_address:
2023-02-23T15:57:05 Notice dhclient DEBUG new_ip_address: 100.111.1XX.83
2023-02-23T15:57:05 Notice dhclient DEBUG old_ip_address: 100.111.1XX.83
2023-02-23T15:57:05 Notice dhclient DEBUG entering with RENEW
2023-02-23T15:47:56 Notice configctl event @ 1677163676.34 exec: system event config_changed
2023-02-23T15:47:56 Notice configctl event @ 1677163676.34 msg: Feb 23 15:47:56 OPNsense.localdomain config[4124]: [2023-02-23T15:47:56+01:00][INFO] config-event: new_config /conf/backup/config-1677163676.319.xml
2023-02-23T15:47:56 Notice configctl event @ 1677163676.34 msg: Feb 23 15:47:55 OPNsense.localdomain config[4124]: [2023-02-23T15:47:55+01:00][INFO] config-event: new_config /conf/backup/config-1677163675.8195.xml
2023-02-23T15:47:55 Notice configctl event @ 1677163674.68 exec: system event config_changed
2023-02-23T15:47:55 Notice configctl event @ 1677163674.68 msg: Feb 23 15:47:54 OPNsense.localdomain config[4124]: [2023-02-23T15:47:54+01:00][INFO] config-event: new_config /conf/backup/config-1677163674.6631.xml
2023-02-23T15:47:43 Notice configctl event @ 1677163662.49 exec: system event config_changed
2023-02-23T15:47:43 Notice configctl event @ 1677163662.49 msg: Feb 23 15:47:42 OPNsense.localdomain config[5005]: [2023-02-23T15:47:42+01:00][INFO] config-event: new_config /conf/backup/config-1677163662.4784.xml
2023-02-23T15:47:42 Notice configctl event @ 1677163661.77 exec: system event config_changed
2023-02-23T15:47:42 Notice configctl event @ 1677163661.77 msg: Feb 23 15:47:41 OPNsense.localdomain config[5005]: [2023-02-23T15:47:41+01:00][INFO] config-event: new_config /conf/backup/config-1677163661.753.xml
2023-02-23T15:47:41 Notice configctl event @ 1677163660.51 exec: system event config_changed
2023-02-23T15:47:41 Notice configctl event @ 1677163660.51 msg: Feb 23 15:47:40 OPNsense.localdomain config[5005]: [2023-02-23T15:47:40+01:00][INFO] config-event: new_config /conf/backup/config-1677163660.4891.xml
2023-02-23T15:47:34 Notice configctl event @ 1677163654.44 exec: system event config_changed
2023-02-23T15:47:34 Notice configctl event @ 1677163654.44 msg: Feb 23 15:47:34 OPNsense.localdomain config[32786]: [2023-02-23T15:47:34+01:00][INFO] config-event: new_config /conf/backup/config-1677163654.4282.xml
2023-02-23T15:47:32 Notice configctl event @ 1677163652.39 exec: system event config_changed
2023-02-23T15:47:32 Notice configctl event @ 1677163652.39 msg: Feb 23 15:47:32 OPNsense.localdomain config[32786]: [2023-02-23T15:47:32+01:00][INFO] config-event: new_config /conf/backup/config-1677163652.3764.xml
2023-02-23T15:47:31 Notice configctl event @ 1677163651.18 exec: system event config_changed
2023-02-23T15:47:31 Notice configctl event @ 1677163651.18 msg: Feb 23 15:47:31 OPNsense.localdomain config[32786]: [2023-02-23T15:47:31+01:00][INFO] config-event: new_config /conf/backup/config-1677163651.1677.xml
2023-02-23T15:47:23 Notice configctl event @ 1677163642.82 exec: system event config_changed
2023-02-23T15:47:23 Notice configctl event @ 1677163642.82 msg: Feb 23 15:47:22 OPNsense.localdomain config[62690]: [2023-02-23T15:47:22+01:00][INFO] config-event: new_config /conf/backup/config-1677163642.7993.xml
2023-02-23T15:47:22 Notice configctl event @ 1677163642.20 exec: system event config_changed
2023-02-23T15:47:22 Notice configctl event @ 1677163642.20 msg: Feb 23 15:47:22 OPNsense.localdomain config[62690]: [2023-02-23T15:47:22+01:00][INFO] config-event: new_config /conf/backup/config-1677163642.1811.xml
2023-02-23T15:47:20 Notice configctl event @ 1677163639.72 exec: system event config_changed
2023-02-23T15:47:20 Notice configctl event @ 1677163639.72 msg: Feb 23 15:47:19 OPNsense.localdomain config[62690]: [2023-02-23T15:47:19+01:00][INFO] config-event: new_config /conf/backup/config-1677163639.6977.xml
2023-02-23T15:47:12 Notice configctl event @ 1677163632.23 exec: system event config_changed
2023-02-23T15:47:12 Notice configctl event @ 1677163632.23 msg: Feb 23 15:47:12 OPNsense.localdomain config[62690]: [2023-02-23T15:47:12+01:00][INFO] config-event: new_config /conf/backup/config-1677163632.2123.xml
2023-02-23T15:47:10 Notice configctl event @ 1677163630.36 exec: system event config_changed
2023-02-23T15:47:10 Notice configctl event @ 1677163630.36 msg: Feb 23 15:47:10 OPNsense.localdomain config[62690]: [2023-02-23T15:47:10+01:00][INFO] config-event: new_config /conf/backup/config-1677163630.3482.xml
2023-02-23T15:47:09 Notice configctl event @ 1677163629.13 exec: system event config_changed
2023-02-23T15:47:09 Notice configctl event @ 1677163629.13 msg: Feb 23 15:47:09 OPNsense.localdomain config[5005]: [2023-02-23T15:47:09+01:00][INFO] config-event: new_config /conf/backup/config-1677163629.1132.xml
2023-02-23T15:04:23 Notice dhclient Creating resolv.conf
2023-02-23T15:04:23 Notice dhclient DEBUG alias_ip_address:
2023-02-23T15:04:23 Notice dhclient DEBUG new_ip_address: 100.111.1XX.83
2023-02-23T15:04:23 Notice dhclient DEBUG old_ip_address: 100.111.1XX.83
2023-02-23T15:04:23 Notice dhclient DEBUG entering with RENEW
2023-02-23T14:11:38 Notice dhclient Creating resolv.conf
2023-02-23T14:11:38 Notice dhclient DEBUG alias_ip_address:
2023-02-23T14:11:38 Notice dhclient DEBUG new_ip_address: 100.111.1XX.83
2023-02-23T14:11:38 Notice dhclient DEBUG old_ip_address: 100.111.1XX.83
2023-02-23T14:11:38 Notice dhclient DEBUG entering with RENEW
2023-02-23T13:17:32 Notice dhclient Creating resolv.conf
2023-02-23T13:17:32 Notice dhclient DEBUG alias_ip_address:
2023-02-23T13:17:32 Notice dhclient DEBUG new_ip_address: 100.111.1XX.83
2023-02-23T13:17:32 Notice dhclient DEBUG old_ip_address: 100.111.1XX.83
2023-02-23T13:17:32 Notice dhclient DEBUG entering with RENEW
2023-02-23T12:22:07 Notice dhclient Creating resolv.conf
2023-02-23T12:22:07 Notice dhclient DEBUG alias_ip_address:
2023-02-23T12:22:07 Notice dhclient DEBUG new_ip_address: 100.111.1XX.83
2023-02-23T12:22:07 Notice dhclient DEBUG old_ip_address: 100.111.1XX.83
2023-02-23T12:22:07 Notice dhclient DEBUG entering with RENEW
2023-02-23T11:26:25 Notice dhclient Creating resolv.conf
2023-02-23T11:26:25 Notice dhclient DEBUG alias_ip_address:
2023-02-23T11:26:25 Notice dhclient DEBUG new_ip_address: 100.111.1XX.83
2023-02-23T11:26:25 Notice dhclient DEBUG old_ip_address: 100.111.1XX.83
2023-02-23T11:26:25 Notice dhclient DEBUG entering with RENEW
2023-02-23T10:33:49 Notice dhclient Creating resolv.conf
2023-02-23T10:33:49 Notice dhclient DEBUG alias_ip_address:
2023-02-23T10:33:49 Notice dhclient DEBUG new_ip_address: 100.111.1XX.83
2023-02-23T10:33:49 Notice dhclient DEBUG old_ip_address: 100.111.1XX.83
2023-02-23T10:33:49 Notice dhclient DEBUG entering with RENEW
2023-02-23T09:39:29 Notice dhclient Creating resolv.conf
2023-02-23T09:39:29 Notice dhclient DEBUG alias_ip_address:
2023-02-23T09:39:29 Notice dhclient DEBUG new_ip_address: 100.111.1XX.83
2023-02-23T09:39:29 Notice dhclient DEBUG old_ip_address: 100.111.1XX.83
2023-02-23T09:39:29 Notice dhclient DEBUG entering with RENEW
2023-02-23T08:47:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-23 07:46:01.961127
2023-02-23T08:46:50 Notice dhclient Creating resolv.conf
2023-02-23T08:46:50 Notice dhclient DEBUG alias_ip_address:
2023-02-23T08:46:50 Notice dhclient DEBUG new_ip_address: 100.111.1XX.83
2023-02-23T08:46:50 Notice dhclient DEBUG old_ip_address: 100.111.1XX.83
2023-02-23T08:46:50 Notice dhclient DEBUG entering with RENEW
2023-02-23T08:46:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-23 07:45:02.073074
2023-02-23T07:53:53 Notice dhclient Creating resolv.conf
2023-02-23T07:53:53 Notice dhclient DEBUG alias_ip_address:
2023-02-23T07:53:53 Notice dhclient DEBUG new_ip_address: 100.111.1XX.83
2023-02-23T07:53:53 Notice dhclient DEBUG old_ip_address: 100.111.1XX.83
2023-02-23T07:53:53 Notice dhclient DEBUG entering with RENEW
2023-02-23T07:39:44 Notice configctl event @ 1677134383.71 exec: system event config_changed
2023-02-23T07:39:44 Notice configctl event @ 1677134383.71 msg: Feb 23 07:39:43 OPNsense.localdomain config[70352]: [2023-02-23T07:39:43+01:00][INFO] config-event: new_config /conf/backup/config-1677134383.686.xml
2023-02-23T07:36:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-23 06:35:35.251138
2023-02-23T07:21:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-23 06:20:02.438284
2023-02-23T07:02:28 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for wan[opt4]
2023-02-23T07:02:28 Notice dhcp6c dhcp6c REQUEST on vtnet0 - running newipv6
2023-02-23T07:02:26 Notice dhcp6c RTSOLD script - Sending SIGHUP to dhcp6c


Now installed:
sudo opnsense-revert opnsense && sudo opnsense-patch 90f1d1d766

Now it´s getting worst....

Since tonight, no connection....
( at about 1:26 I got an email, but in log I thing at 02:02)


2023-02-24T06:04:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 05:03:22.430870
2023-02-24T05:58:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 04:57:15.395869
2023-02-24T05:52:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 04:51:08.511828
2023-02-24T05:49:51 Notice dhclient Creating resolv.conf
2023-02-24T05:46:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 04:45:01.742789
2023-02-24T05:39:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 04:38:55.031610
2023-02-24T05:33:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 04:32:48.183564
2023-02-24T05:27:00 Notice send_telemetry.py telemetry data collected 1 records in 0.17 seconds @2023-02-24 04:26:41.404054
2023-02-24T05:21:00 Notice send_telemetry.py telemetry data collected 1 records in 0.11 seconds @2023-02-24 04:20:32.067803
2023-02-24T05:15:00 Notice send_telemetry.py telemetry data collected 1 records in 0.12 seconds @2023-02-24 04:14:22.809344
2023-02-24T05:09:58 Error send_heartbeat.py connection error sending heartbeat to https://opnsense.emergingthreats.net/api/v1/telemetry
2023-02-24T05:09:00 Notice send_telemetry.py telemetry data collected 1 records in 0.13 seconds @2023-02-24 04:08:13.662099
2023-02-24T05:03:00 Notice send_telemetry.py telemetry data collected 1 records in 0.15 seconds @2023-02-24 04:02:04.424705
2023-02-24T04:56:00 Notice send_telemetry.py telemetry data collected 1 records in 0.15 seconds @2023-02-24 03:55:54.994827
2023-02-24T04:55:24 Notice dhclient Creating resolv.conf
2023-02-24T04:50:00 Notice send_telemetry.py telemetry data collected 1 records in 0.12 seconds @2023-02-24 03:49:45.796397
2023-02-24T04:44:00 Notice send_telemetry.py telemetry data collected 1 records in 0.11 seconds @2023-02-24 03:43:36.488802
2023-02-24T04:38:00 Notice send_telemetry.py telemetry data collected 1 records in 0.14 seconds @2023-02-24 03:37:27.250530
2023-02-24T04:32:00 Notice send_telemetry.py telemetry data collected 1 records in 0.13 seconds @2023-02-24 03:31:18.013304
2023-02-24T04:26:00 Notice send_telemetry.py telemetry data collected 1 records in 0.10 seconds @2023-02-24 03:25:08.589171
2023-02-24T04:19:00 Notice send_telemetry.py telemetry data collected 1 records in 0.10 seconds @2023-02-24 03:18:58.714955
2023-02-24T04:13:00 Notice send_telemetry.py telemetry data collected 1 records in 0.10 seconds @2023-02-24 03:12:49.419820
2023-02-24T04:07:00 Notice send_telemetry.py telemetry data collected 1 records in 0.15 seconds @2023-02-24 03:06:40.106696
2023-02-24T04:02:26 Notice dhclient Creating resolv.conf
2023-02-24T04:01:00 Notice send_telemetry.py telemetry data collected 1 records in 0.10 seconds @2023-02-24 03:00:30.674823
2023-02-24T04:00:05 Error send_heartbeat.py connection error sending heartbeat to https://opnsense.emergingthreats.net/api/v1/telemetry
2023-02-24T03:55:00 Notice send_telemetry.py telemetry data collected 1 records in 0.10 seconds @2023-02-24 02:54:21.375515
2023-02-24T03:49:00 Notice send_telemetry.py telemetry data collected 1 records in 0.11 seconds @2023-02-24 02:48:12.011573
2023-02-24T03:43:00 Notice send_telemetry.py telemetry data collected 1 records in 0.11 seconds @2023-02-24 02:42:02.968904
2023-02-24T03:36:00 Notice send_telemetry.py telemetry data collected 1 records in 0.12 seconds @2023-02-24 02:35:53.429234
2023-02-24T03:30:00 Notice send_telemetry.py telemetry data collected 1 records in 0.10 seconds @2023-02-24 02:29:44.322231
2023-02-24T03:24:00 Notice send_telemetry.py telemetry data collected 1 records in 0.10 seconds @2023-02-24 02:23:34.976761
2023-02-24T03:18:00 Notice send_telemetry.py telemetry data collected 1 records in 0.12 seconds @2023-02-24 02:17:25.647374
2023-02-24T03:12:00 Notice send_telemetry.py telemetry data collected 1 records in 0.11 seconds @2023-02-24 02:11:16.212929
2023-02-24T03:08:56 Notice dhclient Creating resolv.conf
2023-02-24T03:07:06 Error send_heartbeat.py connection error sending heartbeat to https://opnsense.emergingthreats.net/api/v1/telemetry
2023-02-24T03:06:00 Notice send_telemetry.py telemetry data collected 1 records in 0.12 seconds @2023-02-24 02:05:06.705410
[...]
2023-02-24T02:22:00 Notice send_telemetry.py telemetry data collected 1 records in 0.10 seconds @2023-02-24 01:22:00.314843
2023-02-24T02:16:00 Notice send_telemetry.py telemetry data collected 1 records in 0.16 seconds @2023-02-24 01:15:50.910864
2023-02-24T02:15:22 Notice dhclient Creating resolv.conf
2023-02-24T02:10:00 Notice send_telemetry.py telemetry data collected 1 records in 0.15 seconds @2023-02-24 01:09:41.530790
2023-02-24T02:05:35 Error send_heartbeat.py connection error sending heartbeat to https://opnsense.emergingthreats.net/api/v1/telemetry
2023-02-24T02:04:00 Notice send_telemetry.py telemetry data collected 1 records in 0.11 seconds @2023-02-24 01:03:31.953147
2023-02-24T02:02:02 Error rule-updater.py download failed for https://opnsense.emergingthreats.net/api/v1/ruleset/version (HTTPSConnectionPool(host='opnsense.emergingthreats.net', port=443): Max retries exceeded with url: /api/v1/ruleset/version (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x80277b340>: Failed to establish a new connection: [Errno 51] Network is unreachable')))
[...]
2023-02-24T02:02:00 Error rule-updater.py download failed for https://sslbl.abuse.ch/blacklist/sslblacklist_tls_cert.rules (HTTPSConnectionPool(host='sslbl.abuse.ch', port=443): Max retries exceeded with url: /blacklist/sslblacklist_tls_cert.rules (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x8027528b0>: Failed to establish a new connection: [Errno 51] Network is unreachable')))
2023-02-24T01:58:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 00:57:22.808024
2023-02-24T01:52:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 00:51:15.972633
2023-02-24T01:46:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 00:45:09.107259
2023-02-24T01:40:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 00:39:02.232873
2023-02-24T01:36:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 00:35:10.695577
2023-02-24T01:33:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 00:32:55.359621
2023-02-24T01:27:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 00:26:48.595669
2023-02-24T01:22:51 Notice dhclient Creating resolv.conf
2023-02-24T01:22:51 Notice dhclient New Routers (vtnet0): 100.111.0.1
2023-02-24T01:22:51 Notice dhclient New Broadcast Address (vtnet0): 100.111.255.255
2023-02-24T01:22:51 Notice dhclient New Subnet Mask (vtnet0): 255.255.0.0
2023-02-24T01:22:51 Notice dhclient New IP Address (vtnet0): 100.111.1XX.83
2023-02-24T01:21:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 00:20:41.495745
2023-02-24T00:20:35 Notice dhclient Creating resolv.conf
2023-02-23T23:27:54 Notice dhclient Creating resolv.conf
2023-02-23T22:34:32 Notice dhclient Creating resolv.conf
2023-02-23T21:40:27 Notice dhclient Creating resolv.conf
2023-02-23T20:58:00 Notice sudo Andreas : TTY=pts/0 ; PWD=/home/Andreas ; USER=root ; COMMAND=/usr/local/sbin/opnsense-patch 90f1d1d766
2023-02-23T20:58:00 Notice syslog-ng Configuration reload finished;
2023-02-23T20:58:00 Notice syslog-ng Configuration reload request received, reloading configuration;
2023-02-23T20:57:59 Notice opnsense (system local trust) skip intermediate certificate /C=US/O=Internet Security Research Group/CN=ISRG Root X1 from R3 (ACME Client)
2023-02-23T20:57:59 Notice opnsense (system local trust) skip intermediate certificate /C=US/O=Let's Encrypt/CN=R3 from R3 (ACME Client)
2023-02-23T20:57:52 Notice sudo Andreas : TTY=pts/0 ; PWD=/home/Andreas ; USER=root ; COMMAND=/usr/local/sbin/opnsense-revert opnsense
2023-02-23T20:57:41 Notice syslog-ng Configuration reload finished;
2023-02-23T20:57:41 Notice syslog-ng Configuration reload request received, reloading configuration;
2023-02-23T20:57:40 Notice opnsense (system local trust) skip intermediate certificate /C=US/O=Internet Security Research Group/CN=ISRG Root X1 from R3 (ACME Client)
2023-02-23T20:57:40 Notice opnsense (system local trust) skip intermediate certificate /C=US/O=Let's Encrypt/CN=R3 from R3 (ACME Client)
2023-02-23T20:57:32 Notice sudo Andreas : TTY=pts/0 ; PWD=/home/Andreas ; USER=root ; COMMAND=/usr/local/sbin/opnsense-revert opnsense
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GLASFASER_DHCP))
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GLASFASER_DHCP)
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GLASFASER_DHCP6))
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GLASFASER_DHCP6)
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: keeping current default gateway 'fe80::ff:XXXX:202%vtnet0'
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv6 default route to fe80::ff:XXXX:202
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv6 default gateway set to opt4
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 100.111.0.1
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to opt4
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'opt4'
2023-02-23T20:43:49 Notice opnsense /usr/local/etc/rc.newwanip: No IP change detected for wan[opt4]
2023-02-23T20:43:49 Notice dhclient Creating resolv.conf
2023-02-23T20:43:49 Notice dhclient New Routers (vtnet0): 100.111.0.1
2023-02-23T20:43:49 Notice dhclient New Broadcast Address (vtnet0): 100.111.255.255
2023-02-23T20:43:49 Notice dhclient New Subnet Mask (vtnet0): 255.255.0.0
2023-02-23T20:43:49 Notice dhclient New IP Address (vtnet0): 100.111.1XX.83
2023-02-23T20:43:49 Notice dhclient DEBUG calling add_new_address/add_new_routes
2023-02-23T20:43:49 Notice dhclient DEBUG alias_ip_address:
2023-02-23T20:43:49 Notice dhclient DEBUG new_ip_address: 100.111.1XX.83
2023-02-23T20:43:49 Notice dhclient DEBUG old_ip_address: 100.111.1XX.83
2023-02-23T20:43:49 Notice dhclient DEBUG entering with BOUND
2023-02-23T20:43:00 Notice send_telemetry.py telemetry data collected 1 records in 0.04 seconds @2023-02-23 19:42:43.193093
2023-02-23T20:11:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-23 19:10:53.646493


Reboot, now working.

I'm curious how long it works

Greet

Good? Morning!

Quote from: franco on February 23, 2023, 08:05:58 AM
I think the fix still applies, feel free to try it now:
# opnsense-revert opnsense && opnsense-patch 90f1d1d766

So I tested this patch, but it does not work for me. Default route was gone again this morning. Here is the log (with the patch applied):
2023-02-24T06:20:32 Notice dhclient Creating resolv.conf
2023-02-24T06:20:32 Notice dhclient New Routers (vtnet2): 81.xxx.xx.1
2023-02-24T06:20:32 Notice dhclient New Broadcast Address (vtnet2): 81.xxx.xx.255
2023-02-24T06:20:32 Notice dhclient New Subnet Mask (vtnet2): 255.255.255.0
2023-02-24T06:20:32 Notice dhclient New IP Address (vtnet2): 81.xxx.xx.x29
2023-02-24T06:19:39 Notice dhclient Creating resolv.conf
2023-02-24T06:19:39 Notice dhclient New Routers (vtnet2): 192.168.100.1
2023-02-24T06:19:39 Notice dhclient New Broadcast Address (vtnet2): 192.168.100.255
2023-02-24T06:19:39 Notice dhclient New Subnet Mask (vtnet2): 255.255.255.0
2023-02-24T06:19:39 Notice dhclient New IP Address (vtnet2): 192.168.100.10
2023-02-24T05:24:03 Error dhclient send_packet: No route to host
2023-02-24T05:17:44 Error dhclient send_packet: No route to host
2023-02-24T05:11:04 Error dhclient send_packet: No route to host
If interesting, you can find the leases in the attached file. Interestingly, this time my modem first provided a local address and a minute later a correct (external) one.

@patman From the log I can see the new "force" doesn't go through, likely because the backend wasn't restarted (no reboot). small oversight on my end in instructions provided. Run this:

# service configd restart

Next time it should fire properly.


Cheers,
Franco

PS: It's really annoying routers give out 192.168.x.x addresses temporarily as it can mess up the system state.

I did the reboot, but today at 11:38 WAN is shorten down! No ipv4 change!


2023-02-24T11:40:22 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : webgui_configure_do(,opt4))
2023-02-24T11:40:22 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : vxlan_configure_do())
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : unbound_configure_do(,opt4))
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : openssh_configure_do(,opt4))
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : opendns_configure_do())
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : ntpd_configure_do())
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : dyndns_configure_do(,opt4))
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : dnsmasq_configure_do())
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (,opt4)
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: Resyncing OpenVPN instances for interface wan.
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : openvpn_configure_do(,opt4))
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : ipsec_configure_do(,opt4))
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (,opt4)
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GLASFASER_DHCP))
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GLASFASER_DHCP)
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GLASFASER_DHCP6))
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GLASFASER_DHCP6)
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: keeping current default gateway 'fe80::ff:fe02:202%vtnet0'
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv6 default route to fe80::ff:fe02:202
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv6 default gateway set to opt4
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 100.111.0.1
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to opt4
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'opt4'
2023-02-24T11:40:21 Notice opnsense /usr/local/etc/rc.newwanip: IP renewal starting (new: 100.111.1XX.83, old: 100.111.133.83, interface: wan[opt4], device: vtnet0, force: yes)
2023-02-24T11:40:21 Notice dhclient Creating resolv.conf
2023-02-24T11:40:21 Notice dhclient New Routers (vtnet0): 100.111.0.1
2023-02-24T11:40:21 Notice dhclient New Broadcast Address (vtnet0): 100.111.255.255
2023-02-24T11:40:21 Notice dhclient New Subnet Mask (vtnet0): 255.255.0.0
2023-02-24T11:40:21 Notice dhclient New IP Address (vtnet0): 100.111.1XX.83
2023-02-24T11:39:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 10:38:50.137754
2023-02-24T10:52:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 09:51:42.397138
2023-02-24T10:38:34 Notice dhclient Creating resolv.conf
2023-02-24T09:46:02 Notice dhclient Creating resolv.conf


so it is better (inet comes back), but the short interruption is not good!

The patch 90f1d1d766 doesn't work for me too.

Will try your command # service configd restart

14:28 again, ipv4 is gone for a while (ipv6 stays alive)


2023-02-24T14:30:35 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : webgui_configure_do(,opt4))
2023-02-24T14:30:35 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : vxlan_configure_do())
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : unbound_configure_do(,opt4))
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : openssh_configure_do(,opt4))
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : opendns_configure_do())
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : ntpd_configure_do())
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : dyndns_configure_do(,opt4))
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : dnsmasq_configure_do())
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (,opt4)
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: Resyncing OpenVPN instances for interface wan.
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : openvpn_configure_do(,opt4))
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : ipsec_configure_do(,opt4))
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (,opt4)
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GLASFASER_DHCP))
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GLASFASER_DHCP)
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GLASFASER_DHCP6))
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GLASFASER_DHCP6)
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: keeping current default gateway 'fe80::ff:feXX:202%vtnet0'
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv6 default route to fe80::ff:feXX:202
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv6 default gateway set to opt4
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 100.111.0.1
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to opt4
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'opt4'
2023-02-24T14:30:34 Notice opnsense /usr/local/etc/rc.newwanip: IP renewal starting (new: 100.111.1XX.83, old: 100.111.1XX.83, interface: wan[opt4], device: vtnet0, force: yes)
2023-02-24T14:30:34 Notice dhclient Creating resolv.conf
2023-02-24T14:30:34 Notice dhclient New Routers (vtnet0): 100.111.0.1
2023-02-24T14:30:34 Notice dhclient New Broadcast Address (vtnet0): 100.111.255.255
2023-02-24T14:30:34 Notice dhclient New Subnet Mask (vtnet0): 255.255.0.0
2023-02-24T14:30:34 Notice dhclient New IP Address (vtnet0): 100.111.1XX.83
2023-02-24T14:29:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-02-24 13:28:28.024076
2023-02-24T13:28:18 Notice dhclient Creating resolv.conf
2023-02-24T12:34:33 Notice dhclient Creating resolv.conf


Quote from: Bytechanger on February 24, 2023, 12:55:48 PM
so it is better (inet comes back), but the short interruption is not good!

If you followed the technical discussion you will see this has always been unavoidable the way the kernel scrubs the default route while ifconfig reconfigures the same address from scratch.

Please don't grasp at straws describing common behaviour as a bug.


Cheers,
Franco

oh very nice.

But it is a misconduct that the route is deleted.
As a non-technical expert, this error description should be allowed.

(In addition, this behavior gets on my family's nerves)... ;-)

Greets

Quote from: franco on February 24, 2023, 08:52:46 AM
@patman From the log I can see the new "force" doesn't go through, likely because the backend wasn't restarted (no reboot). small oversight on my end in instructions provided. Run this:
# service configd restart

Thanks, done, checking over the weekend.

Quote from: franco on February 24, 2023, 08:54:23 AM
PS: It's really annoying routers give out 192.168.x.x addresses temporarily as it can mess up the system state.

Yeah, ask me ... I asked my provider to even set the router into "bridge mode". I wonder how this behavior conforms to bridge according to IEEE 802.1 ...  :-X

Had a chance to test 90f1d1d766 over the weekend. Seems to resolve this issue for me. Thanks!

Lost my Orange France FTTP connection a few weeks ago.
Arrived in France yesterday and rebooted rooter. All good for 24 hours until IPV4 went again.

Did I read correctly that I should do

opnsense-patch 26d26e2054

and then

opnsense-revert opnsense && opnsense-patch 90f1d1d766

Only second one. I have a new patch but I'm still testing locally. The old one still applies. To be precise:

# opnsense-revert opnsense && opnsense-patch 90f1d1d766 && service configd restart


Cheers,
Franco

Long Time no speak @franco

I jumped ahead and already issued

opnsense-patch 26d26e2054

and then

opnsense-revert opnsense && opnsense-patch 90f1d1d766


I guess I just need to do a service configd restart. Any need to specifically reverse the first patch ?

Hey, indeed :)

The revert trashes all the other patches just to be on the safe side. configd restart should be done or a reboot to enable the extended backend command syntax required.


Cheers,
Franco

cool just issued the configd restart

I'll monitor and revert. I think it's due to renew in about 3 hours so I should have an update soon.

Still up? A bit more than 3 hours :D


Cheers,
Franco

I miscalculated

Renewal in 45 mins approx :-)

Ok fingers crossed

renewal done

all seems well currently

Good, let's take this to 11. There is a similar issue for IPv6 and I have a new patch set to try which could be included in 23.1.2 when it performs better overall:

https://github.com/opnsense/core/commit/737d8f3aabb
https://github.com/opnsense/core/commit/f187bcb814d

# opnsense-revert opnsense && opnsense-patch 737d8f3aabb f187bcb814d && service configd restart

But better to reboot and see if all is up and running. I reckon your IPv6 still works so you are my favourite tester?  :)


Cheers,
Franco

Ok will bae back home later

Will try then

<3

Applied and rebooted for good measure
All seems well so far

Renewal would have been tonight but I suspect we will need to wait 24 hours now as reboot has requested wanip

NOTE: I only ever lost ipv4 not ipv6 here.

@franco
Renewal just requested and successful

All good on ipv6 and ipv4

Neat, thanks. I think we can go ahead with that then.


Cheers,
Franco

Quote from: franco on February 28, 2023, 02:59:47 PM
# opnsense-revert opnsense && opnsense-patch 90f1d1d766 && service configd restart

After a week without issue, I can confirm the fix as well.

Just wanted to add that I've had no issues on:

# opnsense-revert opnsense && opnsense-patch 737d8f3aabb f187bcb814d && service configd restart

Thanks!

Thanks a lot, this will be in 23.1.2 tomorrow.


Cheers,
Franco

@franco did these patches make it into today's patch release?

See above ;)

23.1.2 is out now...

23.1.2 works better,
but 1 or 2 times a day there is a ipv4 cut (ipv6 runs).

ipv4 lease on Deutsche Glasfaser is 1 hour.

(I´ve a linux skript wich tests every 5 seconds ipv4 and ipv6 connection).


2023-03-09T03:45:30 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : webgui_configure_do(,opt4))
2023-03-09T03:45:30 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : vxlan_configure_do())
2023-03-09T03:45:28 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : unbound_configure_do(,opt4))
2023-03-09T03:45:28 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : openssh_configure_do(,opt4))
2023-03-09T03:45:28 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : opendns_configure_do())
2023-03-09T03:45:28 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : ntpd_configure_do())
2023-03-09T03:45:28 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : dyndns_configure_do(,opt4))
2023-03-09T03:45:28 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : dnsmasq_configure_do())
2023-03-09T03:45:28 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (,opt4)
2023-03-09T03:45:28 Notice opnsense /usr/local/etc/rc.newwanip: Resyncing OpenVPN instances for interface wan.
2023-03-09T03:45:28 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : openvpn_configure_do(,opt4))
2023-03-09T03:45:28 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : ipsec_configure_do(,opt4))
2023-03-09T03:45:28 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (,opt4)
2023-03-09T03:45:26 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GLASFASER_DHCP))
2023-03-09T03:45:26 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GLASFASER_DHCP)
2023-03-09T03:45:26 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GLASFASER_DHCP6))
2023-03-09T03:45:26 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GLASFASER_DHCP6)
2023-03-09T03:45:26 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: keeping current default gateway 'fe80::ff:fe02:202%vtnet0'
2023-03-09T03:45:26 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv6 default route to fe80::ff:fe02:202
2023-03-09T03:45:26 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv6 default gateway set to opt4
2023-03-09T03:45:26 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 100.111.0.1
2023-03-09T03:45:26 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to opt4
2023-03-09T03:45:26 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'opt4'
2023-03-09T03:45:26 Notice opnsense /usr/local/etc/rc.newwanip: IP renewal starting (new: 100.111.133.83, old: 100.111.133.83, interface: wan[opt4], device: vtnet0, force: yes)
2023-03-09T03:45:26 Notice dhclient Creating resolv.conf
2023-03-09T03:45:26 Notice dhclient New Routers (vtnet0): 100.111.0.1
2023-03-09T03:45:26 Notice dhclient New Broadcast Address (vtnet0): 100.111.255.255
2023-03-09T03:45:26 Notice dhclient New Subnet Mask (vtnet0): 255.255.0.0
2023-03-09T03:45:26 Notice dhclient New IP Address (vtnet0): 100.111.133.83
[...]
2023-03-08T23:54:03 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : webgui_configure_do(,opt4))
2023-03-08T23:54:03 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : vxlan_configure_do())
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : unbound_configure_do(,opt4))
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : openssh_configure_do(,opt4))
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : opendns_configure_do())
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : ntpd_configure_do())
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : dyndns_configure_do(,opt4))
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : dnsmasq_configure_do())
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (,opt4)
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: Resyncing OpenVPN instances for interface wan.
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : openvpn_configure_do(,opt4))
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : ipsec_configure_do(,opt4))
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (,opt4)
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GLASFASER_DHCP))
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GLASFASER_DHCP)
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GLASFASER_DHCP6))
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GLASFASER_DHCP6)
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: keeping current default gateway 'fe80::ff:fe02:202%vtnet0'
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv6 default route to fe80::ff:fe02:202
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv6 default gateway set to opt4
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 100.111.0.1
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to opt4
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'opt4'
2023-03-08T23:54:02 Notice opnsense /usr/local/etc/rc.newwanip: IP renewal starting (new: 100.111.133.83, old: 100.111.133.83, interface: wan[opt4], device: vtnet0, force: yes)
2023-03-08T23:54:01 Notice dhclient Creating resolv.conf
2023-03-08T23:54:01 Notice dhclient New Routers (vtnet0): 100.111.0.1
2023-03-08T23:54:01 Notice dhclient New Broadcast Address (vtnet0): 100.111.255.255
2023-03-08T23:54:01 Notice dhclient New Subnet Mask (vtnet0): 255.255.0.0
2023-03-08T23:54:01 Notice dhclient New IP Address (vtnet0): 100.111.133.83
[...]
2023-03-08T13:50:51 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : webgui_configure_do(,opt4))
2023-03-08T13:50:51 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : vxlan_configure_do())
2023-03-08T13:50:50 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : unbound_configure_do(,opt4))
2023-03-08T13:50:50 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : openssh_configure_do(,opt4))
2023-03-08T13:50:50 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : opendns_configure_do())
2023-03-08T13:50:50 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : ntpd_configure_do())
2023-03-08T13:50:50 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : dyndns_configure_do(,opt4))
2023-03-08T13:50:50 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : dnsmasq_configure_do())
2023-03-08T13:50:50 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (,opt4)
2023-03-08T13:50:50 Notice opnsense /usr/local/etc/rc.newwanip: Resyncing OpenVPN instances for interface wan.
2023-03-08T13:50:50 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : openvpn_configure_do(,opt4))
2023-03-08T13:50:50 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : ipsec_configure_do(,opt4))
2023-03-08T13:50:50 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (,opt4)
2023-03-08T13:50:49 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GLASFASER_DHCP))
2023-03-08T13:50:49 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GLASFASER_DHCP)
2023-03-08T13:50:49 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GLASFASER_DHCP6))
2023-03-08T13:50:49 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GLASFASER_DHCP6)
2023-03-08T13:50:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: keeping current default gateway 'fe80::ff:fe02:202%vtnet0'
2023-03-08T13:50:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv6 default route to fe80::ff:fe02:202
2023-03-08T13:50:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv6 default gateway set to opt4
2023-03-08T13:50:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 100.111.0.1
2023-03-08T13:50:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to opt4
2023-03-08T13:50:49 Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'opt4'
2023-03-08T13:50:49 Notice opnsense /usr/local/etc/rc.newwanip: IP renewal starting (new: 100.111.133.83, old: 100.111.133.83, interface: wan[opt4], device: vtnet0, force: yes)
2023-03-08T13:50:49 Notice dhclient Creating resolv.conf
2023-03-08T13:50:49 Notice dhclient New Routers (vtnet0): 100.111.0.1
2023-03-08T13:50:49 Notice dhclient New Broadcast Address (vtnet0): 100.111.255.255
2023-03-08T13:50:49 Notice dhclient New Subnet Mask (vtnet0): 255.255.0.0
2023-03-08T13:50:49 Notice dhclient New IP Address (vtnet0): 100.111.133.83



Greets

Yep, this is an ISP-related disruption with overly-aggressive lease time:

2023-03-09T03:45:26   Notice   opnsense   /usr/local/etc/rc.newwanip: IP renewal starting (new: 100.111.133.83, old: 100.111.133.83, interface: wan[opt4], device: vtnet0, force: yes)

There is room for improvement from our end but very likely not in the next 3 months.


Cheers,
Franco

Ok, thanks for reply.
How can I solve it?
Should I connect a FritzBox to ISP and then OPNSense to FritzBox?
FritzBox to ISP should work?!

Greets

That's what I use here, yes.


Cheers,
Franco

Oh, thanks..

OPNSense as exposed Host?
No problems/ latency with double NAT in ipv4??

Greets

I don't use exposed host, but it depends on requirements. No latency but not a lot of traffic as per requirement either.


Cheers.
Franco

OK,now I put my FritzBox to ISP-Modem, and on FritzBox OPNSense.
This works, but 2 questions:

1. in my log is every few seconds:

2023-03-11T12:17:22 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T12:17:20 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T12:14:10 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T12:14:07 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T12:12:44 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T12:12:42 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T12:06:39 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T12:06:37 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T12:04:12 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T12:04:10 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T12:04:08 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T12:04:05 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T11:55:10 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T11:55:07 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T11:54:31 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T11:54:29 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T11:47:49 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T11:47:47 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T11:46:00 Notice send_telemetry.py telemetry data collected 4 records in 0.03 seconds @2023-03-11 10:45:26.297534
2023-03-11T11:45:31 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T11:45:28 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T11:45:00 Notice send_telemetry.py telemetry data collected 1 records in 0.03 seconds @2023-03-11 10:44:45.594789
2023-03-11T11:42:39 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T11:42:37 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T11:36:40 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]
2023-03-11T11:36:37 Notice opnsense /usr/local/etc/rc.newwanipv6: No IP change detected for FritzBoxWAN[opt10]


2. I request a /56 Prefix-length for FritzBox and on OPNSense I request /60 prefix.
All works fine, BUT when I change something on FritzBox, so its restarting internet, ipv6-connection on OPNSense got lost (ipv6 seems to be there, but no traffic is possible).
When I restart OPNSense, it works fine...

Greets

Byte

I think it could be a prefix change issue.
When GritzBox get a new prefix und send it to Opnsense, it doesn't handle it good...

How can I fix it??

Greets