Quote from: osmom on March 19, 2026, 12:03:58 PMWenn du IPv6 hast, stelle mal ein das er IPv4 bevorzugen soll. Das hat bei mir bei Updateproblemen in der Vergangenheit geholfen.
Ne, benutze nur ipv4
Lg 😉
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: osmom on March 19, 2026, 12:03:58 PMWenn du IPv6 hast, stelle mal ein das er IPv4 bevorzugen soll. Das hat bei mir bei Updateproblemen in der Vergangenheit geholfen.
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 26.1.4 (amd64) at Wed Mar 18 14:23:05 CET 2026
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 931 packages processed.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: ....... done
Processing entries: .. done
SunnyValley repository update completed. 15 packages processed.
Updating mimugmail repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: ..... done
Processing entries: .......... done
mimugmail repository update completed. 199 packages processed.
All repositories are up to date.
pkg: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
Checking for upgrades (270 candidates): .......... done
Processing candidates (270 candidates):
pkg: glib-bootstrap has a missing dependency: py311-packaging
pkg: glib-bootstrap has a missing dependency: py311-packaging
pkg: glib-bootstrap has a missing dependency: py311-packaging
pkg: glib has a missing dependency: py311-packaging
Processing candidates (270 candidates)... done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE******GOT REQUEST TO AUDIT CONNECTIVITY***
Currently running OPNsense 26.1.4 (amd64) at Wed Mar 18 14:23:44 CET 2026
Checking connectivity for host: opnsense-mirror.hiho.ch -> 46.235.145.153
PING 46.235.145.153 (46.235.145.153): 1500 data bytes
1508 bytes from 46.235.145.153: icmp_seq=0 ttl=53 time=9.949 ms
1508 bytes from 46.235.145.153: icmp_seq=1 ttl=53 time=10.743 ms
1508 bytes from 46.235.145.153: icmp_seq=2 ttl=53 time=10.459 ms
1508 bytes from 46.235.145.153: icmp_seq=3 ttl=53 time=10.513 ms
--- 46.235.145.153 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 9.949/10.416/10.743/0.290 ms
Checking connectivity for repository (IPv4): https://opnsense-mirror.hiho.ch/FreeBSD:14:amd64/26.1
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 931 packages processed.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: ..... done
Processing entries: .. done
SunnyValley repository update completed. 15 packages processed.
Updating mimugmail repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: ..... done
Processing entries: .......... done
mimugmail repository update completed. 199 packages processed.
All repositories are up to date.
Checking connectivity for host: opnsense-mirror.hiho.ch -> 2a00:d08:1:c::153
ping: UDP connect: No route to host
Checking connectivity for repository (IPv6): https://opnsense-mirror.hiho.ch/FreeBSD:14:amd64/26.1
Updating OPNsense repository catalogue...
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
repository OPNsense has no meta file, using default settings
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
Unable to update repository OPNsense
Updating SunnyValley repository catalogue...
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
repository SunnyValley has no meta file, using default settings
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
Unable to update repository SunnyValley
Updating mimugmail repository catalogue...
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
repository mimugmail has no meta file, using default settings
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
Unable to update repository mimugmail
Error updating repositories!Quote from: stulpinger on March 16, 2026, 07:32:32 PMalle Einträge "verwaist"
sieht nach einem DNS Problem aus - was hast Du eingetragen ?
Was passiert beim Updaten ?
AdGuard installiert ?
***GOT REQUEST TO AUDIT CONNECTIVITY***
Currently running OPNsense 26.1.4 (amd64) at Tue Mar 17 15:00:49 CET 2026
Checking connectivity for host: opnsense-mirror.hiho.ch -> 46.235.145.153
PING 46.235.145.153 (46.235.145.153): 1500 data bytes
1508 bytes from 46.235.145.153: icmp_seq=0 ttl=53 time=12.157 ms
1508 bytes from 46.235.145.153: icmp_seq=1 ttl=53 time=12.212 ms
1508 bytes from 46.235.145.153: icmp_seq=2 ttl=53 time=12.171 ms
1508 bytes from 46.235.145.153: icmp_seq=3 ttl=53 time=12.136 ms
--- 46.235.145.153 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 12.136/12.169/12.212/0.028 ms
Checking connectivity for repository (IPv4): https://opnsense-mirror.hiho.ch/FreeBSD:14:amd64/26.1
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching data: .......... done
Processing entries: .......... done
OPNsense repository update completed. 931 packages processed.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
Fetching data: ...... done
Processing entries: .. done
SunnyValley repository update completed. 15 packages processed.
Updating mimugmail repository catalogue...
Fetching meta.conf: . done
Fetching data: . done
Processing entries: . done
mimugmail repository update completed. 9 packages processed.
All repositories are up to date.
Child process pid=41919 terminated abnormally: Segmentation fault
Checking connectivity for host: opnsense-mirror.hiho.ch -> 2a00:d08:1:c::153
ping: UDP connect: No route to host
Checking connectivity for repository (IPv6): https://opnsense-mirror.hiho.ch/FreeBSD:14:amd64/26.1
Updating OPNsense repository catalogue...
pkg: Failed to fetch https://opnsense-mirror.hiho.ch/FreeBSD:14:amd64/26.1/latest/meta.conf: Could not connect to server
pkg: Failed to fetch https://opnsense-mirror.hiho.ch/FreeBSD:14:amd64/26.1/latest/meta.txz: Could not connect to server
repository OPNsense has no meta file, using default settings
pkg: Failed to fetch https://opnsense-mirror.hiho.ch/FreeBSD:14:amd64/26.1/latest/data.pkg: Could not connect to server
pkg: Failed to fetch https://opnsense-mirror.hiho.ch/FreeBSD:14:amd64/26.1/latest/data.tzst: Could not connect to server
pkg: Failed to fetch https://opnsense-mirror.hiho.ch/FreeBSD:14:amd64/26.1/latest/packagesite.pkg: Could not connect to server
pkg: Failed to fetch https://opnsense-mirror.hiho.ch/FreeBSD:14:amd64/26.1/latest/packagesite.tzst: Could not connect to server
Unable to update repository OPNsense
Updating SunnyValley repository catalogue...
pkg: Failed to fetch https://updates.zenarmor.net/opnsense/FreeBSD:14:amd64/26.1/${SUBSCRIPTION}/meta.conf: Could not connect to server
pkg: Failed to fetch https://updates.zenarmor.net/opnsense/FreeBSD:14:amd64/26.1/${SUBSCRIPTION}/meta.txz: Could not connect to server
repository SunnyValley has no meta file, using default settings
pkg: Failed to fetch https://updates.zenarmor.net/opnsense/FreeBSD:14:amd64/26.1/${SUBSCRIPTION}/data.pkg: Could not connect to server
pkg: Failed to fetch https://updates.zenarmor.net/opnsense/FreeBSD:14:amd64/26.1/${SUBSCRIPTION}/data.tzst: Could not connect to server
pkg: Failed to fetch https://updates.zenarmor.net/opnsense/FreeBSD:14:amd64/26.1/${SUBSCRIPTION}/packagesite.pkg: Could not connect to server
pkg: Failed to fetch https://updates.zenarmor.net/opnsense/FreeBSD:14:amd64/26.1/${SUBSCRIPTION}/packagesite.tzst: Could not connect to server
Unable to update repository SunnyValley
Updating mimugmail repository catalogue...
pkg: Failed to fetch https://opn-repo.routerperformance.net/repo-single/FreeBSD:14:amd64/meta.conf: Could not resolve hostname
pkg: Failed to fetch https://opn-repo.routerperformance.net/repo-single/FreeBSD:14:amd64/meta.txz: Could not resolve hostname
repository mimugmail has no meta file, using default settings
pkg: Failed to fetch https://opn-repo.routerperformance.net/repo-single/FreeBSD:14:amd64/data.pkg: Could not resolve hostname
pkg: Failed to fetch https://opn-repo.routerperformance.net/repo-single/FreeBSD:14:amd64/data.tzst: Could not resolve hostname
pkg: Failed to fetch https://opn-repo.routerperformance.net/repo-single/FreeBSD:14:amd64/packagesite.pkg: Could not resolve hostname
pkg: Failed to fetch https://opn-repo.routerperformance.net/repo-single/FreeBSD:14:amd64/packagesite.tzst: Could not resolve hostname
Unable to update repository mimugmail
Error updating repositories!Quote from: Patrick M. Hausen on February 18, 2026, 03:37:03 PMAlso doch nach draußen. Weshalb fragst du dann explizit nach "nicht nach draußen"? Schreib das doch in den Ausgangspost, Mensch.
Ja, WireGuard, OpenVPN, was immer dir und der Tochter lieber ist.
Falls du eine öffentlich erreichbare IP-Adresse, IPv4 oder IPv6 hast.
Quote from: Patrick M. Hausen on February 17, 2026, 09:36:36 AMVorteile von Kea gegenüber ...?
ISC - einfache Antwort: ISC ist EOL, Kea ist der offizielle Nachfolger
DNSmasq - schwieriger: manche halten Kea für die bessere Architektur, DNSmasq macht sehr viele Dinge auf einmal, ich habe lieber DHCP, DNS und RA in getrennten Diensten. Außerdem kann Kea HA, DNSmasq nicht.
Quote from: Meditux on February 15, 2026, 06:51:10 PMIch hatte nach dem Upgrade ähnliche Erfahrungen. Bei mir lief noch DNSMask. Nach dem Update war der Dienst deaktiviert. Nach einen kurzen Moment doof aus der Wasche schauen war der Fehler eingegrenzt und ich bin zu Kea DHCP gewechselt.
Gruß Meditux
Quote from: Utopia on February 12, 2026, 02:09:42 PMBei mir war das gleiche Problem. Nach dem Update funktionierte das DCHP nicht mehr.
Meine Windows-PCs haben keine IP-Adressen mehr bekommen.
Ich bin im Menü dann auf den Punkt "Dienste", dann auf "DNSMask DNS&DHCP". Im Reiter "Allgemein" war bei dem Menü "ISC / KEA DHCP (veraltet)" der Auswahlpunkt "ISC DHCP4-Leases registrieren" nicht aktiviert. Für mich sieht das so aus, wie wenn dieser Service mit der neuen Version abgeschaltet wurde. Ich habe dort wieder einen Haken gesetzt und auf "speichern" geklickt. Danach haben meine Windows-PC ihre IP-Adresse wieder automatisch über DHCP bekommen.
Ich beobachte das Ganze mal noch etwas, aber augenscheinlich scheint es wieder zu funktionieren.