Messages

Well, an ifconfig down and ifconfig up fixes the problem rather than picking option 11 from the menu once ssh'ing into the system.

Happened again, checked a few things.  IP's were still on the WAN interface and routing table looked fine.  But got different messages in /var/log/system/latest.log...

Code Select Expand

<27>1 2025-10-29T06:11:32-04:00 repulse dhclient 34003 - [meta sequenceId="1"] send_packet: No route to host
<27>1 2025-10-29T06:16:33-04:00 repulse dhclient 34003 - [meta sequenceId="1"] send_packet: No route to host
<27>1 2025-10-29T06:22:39-04:00 repulse dhclient 34003 - [meta sequenceId="1"] send_packet: No route to host

These repeated for 50 times or so.

I've been encounting an annoying issue starting with my old opnsense system (21.x) and has continued to my newly installed 25.7.6 system.  Basically systems behind the firewall loses connectivity to the Internet.  I've started digging into the system's logs and I see these messages:

Code Select Expand

<13>1 2025-10-27T00:55:03-04:00 repulse dhclient 69014 - [meta sequenceId="1"] dhclient-script: Reason RENEW on igb0 executing
<13>1 2025-10-27T00:55:03-04:00 repulse dhclient 69658 - [meta sequenceId="2"] dhclient-script: Creating resolv.conf

igb0 is my WAN nic.  Messages following those two are arp entries for my LAN (interface ix1).  Nothing further mentioning igb0 until I reloaded services.

I can rectify the issue by reloading all services.  Next time it happens I'll try just restarting dhclient rather than fixing it via a sledgehammer approach.

What sort of data should I provide to help upstream to rectify this?

You still don't know if it's trying to connect via IPv4 or IPv6 and disabling non-working IPv6 or preferring IPv4 via setting have always been good options.


Cheers,
Franco

True, I failed to mention that I disabled dhcp6 on my wan interface and even clicked to disable ipv6 to try to narrow things down.  My thoughts on that was when I set this instance up, I had it on my lan (ipv4 only) behind an older opnsense (21) instance and it updated just fine.  It stopped updating once I replaced the 21 instance with this one.  And the obvious difference was the ipv6 interface.  So that's where I began troubleshooting the update errors.

In troubleshooting mbuf errors that were showing up in dmesg, I disabled the following.
* hardware checksum offload
* hardware TCP segmentation offload
* hardware large receive offload

Once disabling those I didn't get any further messages appearing in dmesg or on the console.  Plus an added bonus that updates work again... :). Kinda weird that would be enough to do it.

Code Select Expand

root@repulse:~ # pkg update
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
root@repulse:~ #

After all of thie I've re-enabled ipv6, and I don't get errors when trying to update.

Looks like running pkg update in debug mode helps it to not fail as often...

Code Select Expand


root@repulse:~ # pkg -d -4 update
DBG(1)[75326]> pkg initialized
Updating OPNsense repository catalogue...
DBG(1)[75326]> PkgRepo: verifying update for OPNsense
DBG(1)[75326]> Pkgrepo, begin update of '/var/db/pkg/repo-OPNsense.sqlite'
DBG(1)[75326]> Request to fetch https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/meta.conf
DBG(1)[75326]> opening libfetch fetcher
DBG(1)[75326]> Fetch > libfetch: connecting
DBG(1)[75326]> Fetch: fetching from: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/meta.conf with opts "i4"
DBG(1)[75326]> Fetch: fetching from: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/meta.conf with opts "i4"
DBG(1)[75326]> Fetch: fetching from: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/meta.conf with opts "i4"
DBG(1)[75326]> Request to fetch https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/meta.txz
DBG(1)[75326]> opening libfetch fetcher
DBG(1)[75326]> Fetch > libfetch: connecting
DBG(1)[75326]> Fetch: fetching from: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/meta.txz with opts "i4"
DBG(1)[75326]> Fetch: fetching from: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/meta.txz with opts "i4"
DBG(1)[75326]> Fetch: fetching from: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/meta.txz with opts "i4"
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/meta.txz: Operation timed out
repository OPNsense has no meta file, using default settings
DBG(1)[75326]> Request to fetch https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/packagesite.pkg
DBG(1)[75326]> opening libfetch fetcher
DBG(1)[75326]> Fetch > libfetch: connecting
DBG(1)[75326]> Fetch: fetching from: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/packagesite.pkg with opts "i4"
DBG(1)[75326]> Fetch: fetching from: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/packagesite.pkg with opts "i4"
DBG(1)[75326]> Fetch: fetching from: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/packagesite.pkg with opts "i4"
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/packagesite.pkg: Operation timed out
DBG(1)[75326]> Request to fetch https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/packagesite.txz
DBG(1)[75326]> opening libfetch fetcher
DBG(1)[75326]> Fetch > libfetch: connecting
DBG(1)[75326]> Fetch: fetching from: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/packagesite.txz with opts "i4"
DBG(1)[75326]> Fetch: fetching from: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/packagesite.txz with opts "i4"
DBG(1)[75326]> Fetch: fetching from: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/packagesite.txz with opts "i4"
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/packagesite.txz: Operation timed out
Unable to update repository OPNsense
Error updating repositories!
root@repulse:~ #

I'm having a similar issue.  I'm running OPNsense 25.7.3_7-amd64 and running on an Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz.  DNS appears to work fine as it resolves pkg.opnsense.org just fine, and I've also forced my MTU to 1500 even though it had auto-selected that before I forced it.

Code Select Expand

root@repulse:~ # ping -s 1499 pkg.opnsense.org
PING pkg.opnsense.org (89.149.222.99): 1499 data bytes
1507 bytes from 89.149.222.99: icmp_seq=0 ttl=50 time=118.490 ms
1507 bytes from 89.149.222.99: icmp_seq=1 ttl=50 time=118.232 ms
1507 bytes from 89.149.222.99: icmp_seq=2 ttl=50 time=118.205 ms
1507 bytes from 89.149.222.99: icmp_seq=3 ttl=50 time=119.084 ms
1507 bytes from 89.149.222.99: icmp_seq=4 ttl=50 time=119.107 ms
1507 bytes from 89.149.222.99: icmp_seq=5 ttl=50 time=119.041 ms
1507 bytes from 89.149.222.99: icmp_seq=6 ttl=50 time=119.053 ms
1507 bytes from 89.149.222.99: icmp_seq=7 ttl=50 time=117.933 ms
1507 bytes from 89.149.222.99: icmp_seq=8 ttl=50 time=118.468 ms
1507 bytes from 89.149.222.99: icmp_seq=9 ttl=50 time=118.592 ms
^C
--- pkg.opnsense.org ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 117.933/118.621/119.107/0.406 ms

root@repulse:~ # pkg update
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/meta.txz: Operation timed out
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/packagesite.pkg: Operation timed out
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/latest/packagesite.txz: Operation timed out
Unable to update repository OPNsense
Error updating repositories!
root@repulse:~ #