Messages

never mind, i "fixed" this by reinstalling

Minor updates may be available, answer 'y' to run them instead.

Proceed with this action? [26.7/y/N]: y

Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (0 candidates): . done
Processing candidates (0 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: .......... done
Nothing to do.
Nothing to do.
Flushing temporary package files... done
Starting web GUI...done.
Fetching base-26.1.11-amd64.txz: ..[] failed, no signature found

*** OPNsenseWIN7.localdomain: OPNsense 26.1.11_10 (amd64) ***

Hi there,

when trying to upgrade to 26.7 via console, this fails:

Minor updates may be available, answer 'y' to run them instead.
Proceed with this action? [26.7/y/N]: 26.7
Fetching packages-26.7-amd64.tar: ..[] failed, no signature found
*** OPNsenseWIN7.localdomain: OPNsense 26.1.11_10 (amd64) ***

Trying different mirrors does not help.

I'm a bit lost at this point, any ideas?

Thank you.

no, i have two different certificates, one dedicated server-cert, assigned to the instance, and one dedicated client-cert

i'm pretty sure i do it right, because of the fact that choosing the right ca (and not leave it selfsigned) autofills most of the lines under general. i noticed that every time i created a new cert.

i'll ivestigate further. i have both (the working and non-working) installations as VMs.

for testing purposes i created an new ca, created a server and a client cert from this ca and the error occured when trying to export...

maybe i'll investigate further when i find some time, but to be honest i'm not familiar with openssl...

hi there,

go to System: Firmware: plugins, Click to view the community plugins.

and install plugin: os-strongswan-legacy   1.0_1   120KiB   3   OPNsense   IPsec legacy support

hi there,

im the guy with the "exporting OpenVPN profiles"-Problem.

FYI: i had to downgrade to 26.1.11_10 to make this working again.

Hi there,

Problem was solved by downgrading to 26.1.11_10, export now works as expected again.

Could someone please help me with the certificate-storage-paths ?

i found the root certs in /usr/local/share/certs, but i have no idea where to look for the leaf certificates.

In der shell mal folgendes ausführen

Code Select Expand

opnsense-bootstrap
das installiert die neueste version

Danke für den Hinweis, der Befehl war mir neu, merke ich mir für später.

[rm tar]

so, der Vollständigkeit halber:

nach rm tar und ln -s bsdtar tar ist die Fehlermeldung verschwunden und ich sehe wieder ein changelog.

Jemand hat ihn kaputt gemacht.

wer war das? keiner verlässt den Raum...

lutsch mich rund und nenn mich Bärbel...

auf einer anderen OPNSense ergibt ls -l tar:
lrwxr-xr-x  1 root wheel 6 Jul 13 12:49 tar -> bsdtar

und /usr/bin/bsdtar ergibt nun:
bsdtar: Must specify one of -c, -r, -t, -u, -x

da ist doch wohl tatsächlich der Symlink kaputt... wie kann das?

mich beschleicht der Verdacht, dass tar an sich (als Befehl) das Problem ist...

/usr/bin # tar gibt:
tar: Command not found.

ls -l tar ausgeführt in /usr/bin ergibt:
lrwxr-xr-x  1 root wheel 0 May 11 04:07 tar ->

sollte hinter dem -> nicht noch was kommen? Ein Pfad oder so?