Menu

Show posts

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 Menu

Topics - rheller

#1
20.7 Legacy Series / Upgrade to 20.7 on APU2 did not work
September 07, 2020, 11:34:00 PM
Hi all

I recently tried to go to the new v20.7 but that seemed not to have worked.

My dashboard says that OPNsense is 20.1.9_1-amd64, FreeBSD is 12.1-RELEASE-p7-HBSD and OpenSSL is 1.1.1g 21 Apr 2020

My Audit health status says
***GOT REQUEST TO AUDIT HEALTH***
>>> Check installed kernel version
Version 20.7 is incorrect, expected: 20.1.7
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 20.7 is incorrect, expected: 20.1.7

When I try to 'Check for updates', I get
Firmware status check was aborted internally. Please try again.

So I just tried to go to the console (SSH). Whe I try there to do some pgk update, I discovered that, at least for all mirrors that I was trying, I get
pkg: https://mirrors.dotsrc.org/opnsense/FreeBSD:12:amd64/20.1/latest/meta.txz: Not Found

I checked now at the mirrors and I found that none of the tested ones has a subdirectory '20.1' under the FreeBSD:12 version. This directory only exists under the FreeBSD:11 version.

I assume that I have to go back to some working kernel and base. But before doing that on my own, I would like to have some advice of your cracks since I am not an expert on linux administration and before killing my still operational system, it's better to ask first.

Any help and advice is very appreciated.

Regards, Ralph


#2
German - Deutsch / Save button funktioniert nicht
June 16, 2018, 09:26:40 PM
Hallo

Seit kurzem kann ich in meiner opnsense Firewall keine Aenderungen mehr machen. Egal was ich eingebe (zB ein neues WLAN Passwort), nach dem Speichern ist wieder der alte Eintrag / die vorherige Konfiguration aktiv.

Dazu ein paar Infos: HW ist ein Apu Board von PCEngines, SW ist auf dem Stand von 17.1 (meine Philosophie ist hier 'never change a winning team', wenn ich nicht muss). Irgendwie scheint das Zertifikat per 10.6.2018 abgelaufen zu sein.

Auf die Web Gui Seite komme ich nach wie vor (nut der schon länger vorhandenen Zertifikats-Fehler Meldung). Das Ganze ist Browser-unabhängig (IE11 und Firefix 60). Auch die Firewall funktioniert nach wie vor. Es sind einfach keine Aenderungen mehr machbar.

Was kann ich tun, um mein System wieder vollständig nutzbar machen? Alle Ideen sind sehr willkommen.

Viele Grüsse

Ralph
#3
Hi community

Yesterday I upgraded from my 2 month old Installation to the actual 17.1.9. All worked fine and therefore I went finally to bed having a quiet sleep.

But today there was not anymore Internet available at home (my wife gave me hell but fortunately I was at work  ;D )

This night, after checking my router as well asthe Firewall I finally discovered that DHCP was the cause. In my configuration I did not define the Default Gateways to be transmitted to the clients since if there is no GW defined, OPNsense uses the Interface Address as the GW for the clients. It seems that the actual version of the DHCP Server does not do that anymore. At least before explicitely defining the GW address I had no GW set on the Clients and, of course, after setting it all worked fine.

I would recommend for the next Version to either correct this 'to the old behaviour' or, as my favorite, change the (i) text on the DHCP Setup page to something like 'define the IP address of the GW, leave blank for no assignment'.

Regards, Ralph