1
23.7 Legacy Series / Upgrade search bugging out (SOLVED)
« on: September 04, 2023, 02:04:41 am »
Hoping someone brighter than I can crack this nut...I have internet and can ping other hosts/gateway. But I run into trouble trying to update OPNSense. Seems to be DNS related. Clicking the button to update would lead to a very slow process without the popup at the end showing no updates were found. As the spinning wheel keeps spinning, I cannot see / manage plugins either. The output for the update included "Fetch: transfer timed out" and "changelog.txz appears to be truncated 0/111324bytes"
Setup: OPNSense VM on HyperV in Win11. DNS is Mimugmail's AdGuardHome + Unbound.
This started about a week ago. Thinking I had tinkered with something, I tried starting a new VM from scratch. Got everything working vanilla with box checked to prefer IPv4 over IPv6. Things still failed once I changed Unbound's port and set up AdGuard Home. How to figure this out?
Running Audit - Connectivity:
FIXED. Go to SYSTEM: SETTINGS: GENERAL. Check the box "Do not use the local DNS service as a nameserver for this system".
I (think I) now understand that checking this box will make OPNSense itself respect your DNS settings. Whatever you enter as the DNS servers above this is what it will now use to resolve DNS.
Setup: OPNSense VM on HyperV in Win11. DNS is Mimugmail's AdGuardHome + Unbound.
This started about a week ago. Thinking I had tinkered with something, I tried starting a new VM from scratch. Got everything working vanilla with box checked to prefer IPv4 over IPv6. Things still failed once I changed Unbound's port and set up AdGuard Home. How to figure this out?
Code: [Select]
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 23.7.3 at Sun Sep 3 16:13:31 PDT 2023
Fetching changelog information, please wait... fetch: transfer timed out
fetch: /usr/local/opnsense/changelog/changelog.txz appears to be truncated: 0/111324 bytes
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 852 packages processed.
Updating mimugmail repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: ........ done
Processing entries: .......... done
mimugmail repository update completed. 190 packages processed.
All repositories are up to date.
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking for upgrades (99 candidates): .......... done
Processing candidates (99 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***
Running Audit - Connectivity:
Code: [Select]
***GOT REQUEST TO AUDIT CONNECTIVITY***
Currently running OPNsense 23.7.3 at Sun Sep 3 16:04:23 PDT 2023
Checking connectivity for host: pkg.opnsense.org -> 89.149.222.99
PING 89.149.222.99 (89.149.222.99): 1500 data bytes
1508 bytes from 89.149.222.99: icmp_seq=0 ttl=39 time=173.346 ms
1508 bytes from 89.149.222.99: icmp_seq=1 ttl=39 time=173.278 ms
1508 bytes from 89.149.222.99: icmp_seq=2 ttl=39 time=167.787 ms
1508 bytes from 89.149.222.99: icmp_seq=3 ttl=39 time=167.959 ms
--- 89.149.222.99 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 167.787/170.592/173.346/2.720 ms
Checking connectivity for repository (IPv4): https://pkg.opnsense.org/FreeBSD:13:amd64/23.7
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 852 packages processed.
Updating mimugmail repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: ........ done
Processing entries: .......... done
mimugmail repository update completed. 190 packages processed.
All repositories are up to date.
Checking connectivity for host: pkg.opnsense.org -> 2001:1af8:5300:a010:1::1
PING6(1548=40+8+1500 bytes) 2001:558:6025:23:41bf:3112:7fd:1176 --> 2001:1af8:5300:a010:1::1
1508 bytes from 2001:1af8:5300:a010:1::1, icmp_seq=0 hlim=40 time=164.397 ms
1508 bytes from 2001:1af8:5300:a010:1::1, icmp_seq=1 hlim=40 time=163.611 ms
1508 bytes from 2001:1af8:5300:a010:1::1, icmp_seq=2 hlim=40 time=170.041 ms
1508 bytes from 2001:1af8:5300:a010:1::1, icmp_seq=3 hlim=40 time=165.012 ms
--- 2001:1af8:5300:a010:1::1 ping6 statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 163.611/165.765/170.041/2.518 ms
Checking connectivity for repository (IPv6): https://pkg.opnsense.org/FreeBSD:13:amd64/23.7
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 852 packages processed.
Updating mimugmail repository catalogue...
pkg: https://opn-repo.routerperformance.net/repo/FreeBSD:13:amd64/meta.txz: Unknown resolver error
repository mimugmail has no meta file, using default settings
pkg: https://opn-repo.routerperformance.net/repo/FreeBSD:13:amd64/packagesite.pkg: Unknown resolver error
pkg: https://opn-repo.routerperformance.net/repo/FreeBSD:13:amd64/packagesite.txz: Unknown resolver error
Unable to update repository mimugmail
Error updating repositories!
***DONE***
FIXED. Go to SYSTEM: SETTINGS: GENERAL. Check the box "Do not use the local DNS service as a nameserver for this system".
I (think I) now understand that checking this box will make OPNSense itself respect your DNS settings. Whatever you enter as the DNS servers above this is what it will now use to resolve DNS.