Messages

1

24.7 Production Series / Re: New dashboard does not play well with mobile device.

« on: September 25, 2024, 01:34:57 am »

Thanks for the reply.
Good that it is not just me then.

Even if the old dashboard is a bit outdated (hower not bad in my opinion) but it was strict sizes and aligning which would make small screens behave better and large screens also behave in a predictable way.

Now it feels cluttered and not well adjusted.
I agree with your statement and think this needs to be revisited with someone having better experience with UX design to get back to what was powerfull with the old dashboard design and structure BUT with a newer more updated and agile design.

Best regards
Dan Lundqvist

2

24.7 Production Series / New dashboard does not play well with mobile device.

« on: September 23, 2024, 01:46:33 am »

Hello,
Not up to start a flamewar but is it more usets than me that agree with me that the new dashboard does NOT play well with mobile devices. But also placement, size and movement of widgets is more problematic than on the old dashboard.

Widgets placed in a three column way, was automatically
stacked 1+2+3 on a mobile display in the old versions
But in the new dashboard mixes the items mishmash
from all stacks and there is no strict discipline that it
stacks column 1,2,3,n in that order.
Another problem also seen is that certain widgets
Is offshifted to the right on mobile display so widgets
is not exactly on top of each other.
This was much better in old dashboard where widget
width was always the same and they was always
left-shifted.

I can agree that some of widgets looks nicer in the new
gui but some works needs to be done to make widget
aligning better and also widget sorting more strict
to the old way of column 1,2,3,n.

That is my 2 cent worth of constructive criticism.
Don't get me wrong,  I really do like Opnsense and
has been running it for many years and have no
plans of swapping.

Best regards
Dan Lundqvist
Stockholm, Sweden

3

23.1 Legacy Series / [SOLVED] VPN: IPsec: Status Overview and Widget shows Remote IP as "%any".

« on: March 07, 2023, 07:50:41 am »

Since upgrade to OPNsense 23.1.1_2, VPN: IPsec: Status Overview shows ALL Remote IP as "%any".
Also the IPSec Widget shows  "%any" in the "(...)

Br Dan Lundqvist

UPDATE: Seems to have been solved in 23.1.3
Now updated with "0.0.0.0/0,::/0" both in IPSec Status and in Widget.

4

Hardware and Performance / Re: OpnSense in Synology VirtualManager VM does not shut down VM properly

« on: January 28, 2023, 01:28:30 pm »

Does Synology has some ACPI options to enable?

Nope, not that I have found.
It is based on a Intel Celeron J4125 2GHz but don't  have access to any BIOS settings as it boots up nativly.
Have not found any settings for it in GUI.

I have even tried "shutdown -p now" from commandline in OPNsense and it still does not shutdown the VM as seen in the VM Manager in Synology. :-/

Have tried both legacy and UEFI....
It is a bit of a bummer. :-|

I am not saying it is a fault in OPNSense, don't get me wrong.

Bst regards
Dan Lundqvist

UPDATE:
Just as a test (to see if FreeBSD could shutdown VM in Synology at all) I installed latest pfSense in a VM.
An then tried to shutdown VM from Synology VM manager and it both started the shutdown in pfSense window also managed to shutdown completly so Synology VM and FreeBSD are able to do it.
I tested with the exact same VM for both installations just to compare apples and apples.

(yes, I know, opnsense vs pfsense battle/flamewar. Don't worry. I made the decision to go away from pfSense to opnsense and have no plans on going in the oposite direction. :-)

I checked the difference in FreeBSD version
OPNSense: FreeBSD 13.1-RELEASE-p5
pfSense: FreeBSD 12.3-STABLE

Conclusion: 
pfSense on FreeBSD 12.3 stable are able to shutdown OK but opnsense on FreeBSD 13.1 p5 is not.
Reason unknown right now.
Same Synology HW/SW, Same VM BIOS, Same VM settings.

UPDATE2:
I have now tested the following to see if any of them works:
OPNsense 21.1   FreeBSD 12.1 (HardenedBSD)          OK, shuts down and power off OK.
OPNsense 21.7   FreeBSD 12.1 (HardenedBSD)            OK, shuts down and power off OK.
OPNsense 22.1   FreeBSD 13-STABLE                  NOK, does not power off.
OPNsense 22.7   FreeBSD 13.1-RELEASE               NOK, does not power off.

Conclusion: Something has changed between FreeBSD 12.1 -> FreeBSD 13 (and/or OPNsense 21.x -> 22.x) causing it to stop working in shutting it down when running in Synology Virtual VM. (QEMU/KVM). :-/

Found the following thread. Will try the settings to see if it helps.
https://forums.freebsd.org/threads/cannot-shutdown-reboot-after-upgrade-to-13-0-release.80199/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253175

Disabling the USB interface seems helping it to get stuck in uhub0: detached indefinetly and is now able to shut down OK.  Also added the tunable "hw.kern.efi.poweroff=0" but that on it's own did not help. Only by disabling USB interface.
Adding the tuneable "hw.usb.no_shutdown_wait=1" but did not help as long as I have USB hub enabled.
Only swithing USB hubb off helps it to truly shut down. Lucky for me I do not need the USB hub in my VM.

I think someone needs to look into this as it seems to be more people having same issue on FreeBSD 13 and it seems to be related to that

Seems like the issue is related to that it won't shutdown the VM. It waits at uhub0: detached indefinetly.
t seems there are situations in which a none USB related issue is at work (referring here to SirDice's post #3), preventing the machine to power off. 

A comment regarding running in VirtualBox VM they stated
"Setting the VM's system chip set to ICH9 (instead of the default PIIX3), with enabled USB controller, and default hw.efi.poweroff=1 the VM powers off immediate after uhub0: detached.
Apparently there is a relation between the chip set in use and a complete power off of the VM."

5

22.7 Legacy Series / Routing table corruption after reboot. *PROBLEM FOUND/SOLVED*

« on: October 14, 2022, 11:13:02 am »

Hello,

I have an issue that has been going on now for some time that is very anoying and still after 22.7.6 upgrade persists.

BACKGROUND:
I have 4 IPsec tunnels (one standard and 3 VTI) and a OpenVPN Server configured

PROBLEM:
What happens is that every time I reboot the opnsense, two of the static routes configured gets corrupted and selects a different gateway. Happens every time I reboot. If I remove and set them up again the routing table becomes correct and routing starts working OK.

After REBOOT
Destination             Gateway              Flags    Use     MTU     Netif         Netif(name)
192.168.10.0/24     192.168.121.2   UGS     NaN     1500   ovpns1     OVPN_SERVER
192.168.20.0/24     192.168.121.2   UGS     NaN     1500   ovpns1     OVPN_SERVER

After reconfigure 192.168.10.0 and 192.168.20.0
Destination             Gateway              Flags    Use     MTU     Netif         Netif(name)
192.168.10.0/24     link#8                 US        NaN     1400   ipsec1     HENRIK_VTI
192.168.20.0/24     link#9                 US        NaN     1400   ipsec3     HENRIK_MAMMAPAPPA_DIREKT

Have tried all sorts of things but problem still persists and ONLY one these two routes...
Feel it is a bug lurking...

Has anyone else seen this problem and could someone at opnsense have a look.
I have attached some screenshots and logfiles.

Contact me with pm for more screenshots, logs and I could include the config.xml as well.

UPDATE:
I have now found the culprit.

I had a by misstake defined a bunch of networks in OpenVPN Server config "IPv4 Remote Network" which caused it to highjack these nets towards the ovpns1 interface instead of the one I had defined in the routing table. Problem is now solved...




Best regards
Dan Lundqvist
Stockholm, Sweden

6

Hardware and Performance / Re: OpnSense in Synology VirtualManager VM does not shut down VM properly

« on: September 29, 2022, 01:56:04 pm »

Is there no one who has stumbled on to this problem running OpnSense in a Synology VM ?

I do have the OpnSense plugin "QEMU Guest Addon" installed.  Even tried to re-install but same result.

Best regards
Dan Lundqvist (mrzaz)

7

Hardware and Performance / OpnSense in Synology VirtualManager VM does not shut down VM properly

« on: August 11, 2022, 03:55:55 am »

Hello,

I am trying to run OpnSense in a Synology DS920+ Virtual Manager VM which works OK. No problems.
However, I have some issues with halting OpnSense. It halts Opnsense but does not halt the VM itself.
Tested from the GUI and CLI to shut down OpnSense.

Have tested to install the QEMU plugin in OpnSense but no difference.
- Operating System = Other (as i am installing a VM containing FreeBSD)
- Legacy BIOS
- Setup 2 vSwitch entries with WAN in one (LAN2) and LAN in the other (LAN1) and added 2 NICs. Both VirtIO.
- 1 CPU (during testing)
- videocard vga
- Normal priority

All works OK with the VM, just the halt that does not halt the VM itself, only the content of the VM (OpnSense).
Anyone have any ideas how to get this working OK ?

Best regards
Dan Lundqvist (mrzaz)

8

Development and Code Review / Re: APC UPS new plugin

« on: February 01, 2022, 08:52:02 am »

Hi,
This could already be done if you click on "advance mode". 🙂

Best regards
Dan Lundqvist (mrzaz)

9

Development and Code Review / Re: APC UPS new plugin

« on: August 26, 2021, 03:13:37 pm »

Hello,

I have joined Droid999's small team of developing the Apcupsd plugin and the current version in external repo works OK now. Have tried to help Droid999 to squash some issues found.

I am in the process to do some cleanup, preparing the plugin to be migrated into the official opnsense_plugin repo.  Have not planned a official date yet for the move as I may need some help with the GitHub migration so we don't screw anything up or loose some data. If someone is good in doing that, please contact us through PM. :-)

Best regards
Dan Lundqvist (mrzaz)

10

21.1 Legacy Series / [Bug] Reproduced bug with IPSec Routed and an routing entry getting lost.

« on: April 01, 2021, 01:33:06 am »

Hello,

I have found a reproducible bug with IPSec Routed and a routing entry getting lost causing issues to ping/reach remote tunnel-IP.

Prerequsit:
- Tested with 21.1.4
- Setup IPSec Routed in both end. 
example:
I have a IPSec routed net with phase1 and phase2 setup with a tunnel-net 10.6.110.0/30.
Router1   10.6.110.1/30     (LAN: 192.168.120.221/24)
Router2   10.6.110.2/30     (LAN: 192.168.120.231/24)
- Have enabled "Dynamic gateway policy" and it has created the Dynamic Gateways in the gateway tab.
- I have also added rule on IPSec+VTI_ifc+LAN with a "Allow Firewall to respond to pings"
  Dir: in, IPv4, ICMP, Any, This Firewall
- Configured the dynamicly created gateways with "Far Gateway"

1. restart routers. Both routers have the following entries. (reversed order in router2)
Destination        Gateway            Flags     Netif Expire
default            178.132.73.97      UGS      vtnet0
10.6.110.1         link#7             UHS         lo0
10.6.110.2         link#7             UH       ipsec1

2. Go to Gateways and edit the dynamic gateway created from IPsec.

3. Untick the "Disable Gateway Monitoring" and enter the tunnelIP on the other side and press APPLY.
(eg. 10.6.110.2)

4. Go to Gateways and edit the dynamic gateway created from IPsec again.

5. Tick the "Disable Gateway Monitoring" and remove the tunnelIP so editbox is blank and press APPLY.

6. Now the routing table has lost one entry. (the "10.6.110.2         link#7             UH       ipsec1"
Destination        Gateway            Flags     Netif Expire
default            178.132.73.97      UGS      vtnet0
10.6.110.1         link#7             UHS         lo0

This is a bug.

Have now been issued in:
https://github.com/opnsense/core/issues/4888

Also another issue seen is that even when both entries exists and you could ping the remote tunnel IP both from commandline or through OPNSense webgui, if you enable gateway monitoring the monitorIP shows as blank and Gateway also blank and it is always OFFLINE.

I found the following in github that looks like the problem.
https://github.com/opnsense/core/issues/4676

In pfSense, from where I am currently migrating from to OPNSense (which will be my router to use in the future), the IPSecRouted dynamicly created gateways always picks up and shows the Gateway IP and the Monitor IP even if IP says "dynamic".  This could possible be an additional bug.

Best regards
Dan Lundqvist
Stockholm, Sweden

11

Virtual private networks / Frustrated on strange behaviour on tunnel net IPs in IPsec Routed.

« on: March 31, 2021, 06:34:39 pm »

Hello,

I'm coming from pfsense and is migrating to OPNSense and have stumbled on a strange intermittent issue that I could not find a root cause or solution for.

I know that some but not all of this has been discussed in some threads but even implementing the proposals i do not get it to work solid.

I have a IPSec routed net with phase1 and phase2 setup with a tunnel-net 10.6.110.0/30.
Router1   10.6.110.1/30     (LAN: 192.168.120.221/24)
Router2   10.6.110.2/30     (LAN: 192.168.120.231/24)
- Have enabled "Dynamic gateway policy" and it has created the dynamic Gateways in the gateway tab.
- I have even tried the proposal in the OPNSense manual about creating the gateways manually but that works even worse. :-/  It gives "The following input errors were detected: Cannot add IPv4 Gateway Address because no IPv4 address could be found on the interface." so the handbook config does not work. (Tried to follow it by the book)

- I have also added rule on IPSec+VTI_ifc+LAN with a "Allow Firewall to respond to pings"
  Dir: in, IPv4, ICMP, Any, This Firewall
- I have also tested with or without Firewall / Settings /Advanced/ Disable force gateway enabled.
- I have created a Static route to router2 LAN via VTI gateway. (and same in reverse router)

What happens is that occactionally it is possible to ping the tunnel IP both locally and remote either direct or by specifying the tunnel source IP when done from the router itself. (lets say from router1 ping 10.6.110.2 or even it's own 10.6.110.1) but then later for long times it is not possible to ping at all.  Just gets connection timeout.

If I however tries to ping the LAN IP on the other side of the link it is working 100% successful.
So the link is up and also when i do a manual ping to the LAN ip and capture on link in other side it comes through and replies:

I compared a pfSense routing table with the OPNsense and there i could see that it misses an entry for the remote side:

pfsense: (different site-to-site VTI but same prinnciple. also having dynamic gateway for IPSecVTI)
Destination   Gateway   Flags   Use   Mtu   Netif   Expire
10.6.106.1   link#10   UH   8565   1400   ipsec1000   
10.6.106.2   link#10   UHS   0   16384   lo0

opnsense:
It is all over the place. in router1 neither 106.1 or106.2 is visible in the routing table and in router2 they are but still not possible to to ping remote tunnel-IP.  So weird.

UPDATE:
After a restart of router1 the routes came back to the routing table and now I was able to ping
the other sides tunnel IP.

- Question is why these routes intermittently dissapears from the routing table ? (bug?)
- Still Gateway Monitoring does not work. Still OFFLINE regardless if I set monitor-ip o not but normal ping from commandline or through ping GUI works OK.

UPDATE2:
Now after a short while (5-10min) the 10.6.110.2 entry is again lost from the routing table.
The entry:
ipv4   10.6.110.2   link#7   UH   2446   1400   ipsec1   Router1Router2

It still exists in the router2.

UPDATE3:
I have now reproduced problem and feels like a bug.

1. restart routers. Both routers have the following entries. (reversed order in router2)
Destination        Gateway            Flags     Netif Expire
default            178.132.73.97      UGS      vtnet0
10.6.110.1         link#7             UHS         lo0
10.6.110.2         link#7             UH       ipsec1
2. Go to Gateways and edit the dynamic gateway created from IPsec.
3. Untick the "Disable Gateway Monitoring" and enter the tunnelIP on the other side and press APPLY.
4. Go to Gateways and edit the dynamic gateway created from IPsec again.
5. Tick the "Disable Gateway Monitoring" and remove the tunnelIP so editbox is blank and press APPLY.
6. Now the routing table has lost one entry. (the "10.6.110.2         link#7             UH       ipsec1"
Destination        Gateway            Flags     Netif Expire
default            178.132.73.97      UGS      vtnet0
10.6.110.1         link#7             UHS         lo0

Who do I contact to write this in as a bug-report ?
I tried this on the abslute latest update done 10min ago with same result.


UPDATE:
Have now done a bug report.
https://forum.opnsense.org/index.php?topic=22400.0
https://github.com/opnsense/core/issues/4888


Best regards
Dan Lundqvist
Stockholm, Sweden

12

Development and Code Review / Re: APC UPS new plugin

« on: February 28, 2021, 11:13:08 am »

Hi,
I would really like to see this one official through Plugins.
I come from pfSense but has now taken a decision to move to
OPNSense permanently and have a few plugins I use a lot and
the apcupsd is one them as I use it to control a proper shutdown
if power outage that finally shuts down UPS so it could go down
gracefully.

Best regards
Dan Lundqvist

13

21.1 Legacy Series / Interface Description not saved in IPSEC1 (Policy VTI created IFC).

« on: February 21, 2021, 02:08:46 am »

I have created a route based IPSec (VTI) and it has created a IPSEC1 interface which is working OK.
However I found a bug that when you try to update Description for this interface and press save it is then gone after save updates the screen.
So even after Apply the description is not saved/stored.

I would like to rename my VTI based interfaces to ..._VTI.

Running OPNsense 21.1.1-amd64.

Best regards
Dan Lundqvist
Stockholm, Sweden