Messages

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

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

Thanks!

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

Here's the contents, thanks:

Code Select Expand

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;
}


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.

OK, having toggled prefer ipv6 (presently off) and the firewall advanced enable ipv6 (presently on) it started working again. No faith that it will survive a reboot, but working as expected at the moment. IPV6 pings are working again from the firewall to outside hosts. FYI, never saw these being blocked in the firewall log even when it wasn't working. Was also able to update bogon lists, which also failed previously.

Is there any relevant information I can gather to diagnose and hopefully find a permanent fix? I am all but certain things are going to go belly up again the next reboot.

OK, tried the suggestion by fruit. Out of the gate it appeared to work! Interestingly I could now ping ipv6 from the firewall and the update check completed. However DHCPD6 showed as stopped and never came back up. After a reboot everything reverted to its broken state. Also, i saw that sylog-ng remained stopped. The log showed:

kernel: pid 73816 (syslog-ng), jid 0, uid 0: exited on signal 11 (core dumped)

Not sure if this is related, I've seen this happen several times before. It started manually.

Since the initial success, I've been unable to replicate my first working result. Toggling IPV6 doesn't seem to do anything in regards to updates, and ipv6 pings never worked again from the firewall. However, being able to ping ipv6 from the firewall after changing this the first time leads me to believe something is broken in the firewall rules.

I dunno, I'd like to get all this working as I've heard good things about OPNsense, but between this issue and the general instability of services, I am losing confidence that it is ready to be my daily driver.  :(

Hello all, new to OPNsense and I'm hoping someone can help me out with this problem I ran into. Seems related to ipv6, which is an area I don't have much experience.

I did a new, clean install of 20.7. This went fine, however when checking for updates I would get a timeout or "package manager not responding" error with the plugin screen blank or showing only the installed packages and their status as orphaned.

If I set the system option to prefer ipv4, updates start working as expected. When testing from my desktop pc, ipv6 appears to be working just fine, with hosts resolving and pinging.

From the console, updates display the same behavior as the gui, normally when ipv4 is preferred and hanging when that option is disabled. IPV6 hosts seem to resolve, but pings fail from the console. Why would everything work from the desktop, but fail on the router itself? Have I misconfigured something? This is a very new, extremely basic install, so I'm not sure what I might have changed to cause this. As this happens with a clean install with all default settings, maybe there is some fallback behavior or error messaging that ought to be added to OPNsense to handle this situation?

Again, not my area of expertise - just recently got an ISP with ipv6 support - so hopefully I've done something dumb and you guys can point it out.  ;D