Messages

I just updated an intel nic only device w/o any problem too. And yes: services widget looks nice now :D

I faced the same issue, which was solved as soon as I switched to another mirror. I was on DEFAULT, when updates failed (neverending as well as signature invalid).

Thanks Franco,

I was organizing this device's access for different server, all linux, and just continued in the same way with my sense. In fact I wasn't even aware I could do it via OPNsense's gui :D

I deleted the second entry in the file. Checked file. Added the second key via gui. Et violá authorized_keys is again carrying two entries.

Cool coincidence indeed.

Thanks guys!

ssh-copy-id would work for a standard FreeBSD or Linux system but in OPNsense you must use the UI to add the key to the user account in question.

Wow, what a coincidence :)

Just this morning, I manually edited /root/.ssh/authorized_keys on my OPNsense instance and added a second public key to it.

I tend to generate device based keys, which in this case leads to at least two public keys for the same user "root" on OPNsense.

Now: If I checked user parameters via gui, I can only see the original, first key. The second one is not visible. A quick test from my second device shows it nevertheless works. Shouldn't we be able to add more than one pub key to a user for device based keys?

Hi Franco,

concerning ... "would temporarily fix this anyway?"

I applied before mentioned patches yesterday around lunchtime. I haven't done anything since with OPNsense. And zerotier is still working as it should.

A restart of zerotier didn't do anything when the problem occurred for the first time a couple of days ago with the unpatched version.

Confirmed. Patch works here as well. Thanks

This (solution 2) helped me to get my local gateway working. Thanks :)

This helped me to get local DNS and outbound DNS working. Thanks :)

Keep up the great work AND spirit here. OPNSense is not only about a peace of software, it is about people as well. It just feels like being home ;)

Donated!

Thats almost 4 years ago. Some time after my donation I got infected with a virus that caused a lot of pain, for way too long: its name is "USG-PRO-4". I later accepted the fact that I made a mistake and approximately a year ago I returned back and feel relieved ever since.

Today's release of 22.1 reminds me of the great value OPNsense provides to me. Hence I am pleased to donate again.

Hier steht, wie ich es grundsätzlich eingerichtet habe: https://forum.opnsense.org/index.php?topic=21196.0

Damit ist der DNS auf allen Clients, die ihre IP Adresse über sense beziehen, gesetzt. Ausnahmen: Manuel gesetzter DNS oder in IoT Geräten manchmal fest verdrahteter DNS (meist 8.8.8.8 oder so).

Thanks, corrected :)

Ich sehe das genau so: Macht immer weniger Sinn. Gilt m.E. auch für IPS/IDS. Bin auf Feedback gespannt.

Same here.

DHCPv4 shows "Stopped" on dashboard. However, according to logs it is still running and clients still receive IP addresses. A reboot indeed solves it, until changes are made. I did not touch DHCP settings though. The last change I did was related to DynDNS and Gateway Monitoring.

@franco might be worth to look at it?

@meschmesch: might be appropriate to temporarily change thread title to "not solved yet?" so that it gains attention.

Ich habe auf meiner IPU662 mit 16GB proxmox mit 3 VMs laufen:

OPNsense (8GB RAM) - CPU auf HOST
2x Debian mit zahlreichen Docker-Containern - CPU auf kvm

Im Mittel konsumiert die Maschine 21% CPU, in den Spitzen (Updates) sind es mal 80%. Stromverbräuche sind im übrigen auf der Webseite zu den IPUs von nrg-systems in den Daten aufgeführt.

Einfach auf dem Dashboard die Anzeige für das Gateway aktivieren. Dort steht dann IP und Status.