Messages

We are running OPNSense 19.7.4 with DHCP4 activated on the LAN interface. DHCP distributes fixed IP addresses to many Linux VMs, along with a lot of static routes that have been defined in system->routes. All of the Linux VMs receive the static routes properly, but they don't get a default route. So after a VM reboot it looks like this:

root@onlyofficeprod:/home/roland# ip route
10.8.1.0/24 via 192.168.0.226 dev ens3
100.70.4.39 via 192.168.0.227 dev ens3
192.168.0.0/24 dev ens3 proto kernel scope link src 192.168.0.174
192.168.3.1 via 192.168.0.26 dev ens3

The default route has to be added manually. In contrast to the described situation with fixed leases, clients with dynamic leases receive their default route properly.

Does anyone have an idea why that happens and how it can be fixed?

Thanks!
Roland

Thanks a lot! Works for me now.

I am setting up an OPNSense Gateway 19.7.2. While trying to define classless static routes to be sent to each DHCP client it seems as if my definitions don't lead to working routes. In a Wireshark trace the 121 option generated with OPNSense is flagged as "in error".

What I did:
- in Services-DHCP-LANInterface-Additonal Options added Number "121", Type "Text" and Value 20:C0:A8:03:01:C0:A8:00:1A:00:C0:A8:00:E2

See pic1.png for the Wireshark trace on a client resulting from this definiton.

See pic2.png for the Wireshark trace resulting from this defintion in a different DHCP server (IPFire) where the route is accepted by the client.

In the first picture the length information appears as 50 (hex 32), which is clearly wrong since in my definition I wrote x'20', which is decimal 32.

Did I commit a mistake in my definition or is this a bug in OPNSense?

We are on our way to create our first OPNsense machine, which seems easy so far, but we hit an issue that download speeds are far below the lines's capabilities, while the uploads speed is as expected.

Two lines, one Unitymedia 280/25 MBit, one Telekom 50/10 MBit. They are configured as MulitWAN Failover, with the faster line as Tier 1.

In the beginning we had download speeds of 300 kB/s. Now we have changed network cards and disabled various interface hardware settings, resulting in 3 MB/s. Which is still only about 1/4 of what we reach via direct access to Unitymedia.

The only place where we see something out of order are packet loss rates on both interfaces that go to around 10% for a few seconds every few minutes.

Of course we checked cables, switches and network cards. Direct access using the Unitymedia network or Telekom network deliver the expected download rates - so the problem seems to be within the OPNsense machine. What is strange: the upload speed is not affected negatively.

The machine is a 4 core i5 650 with 3.2 GHz and 12 GB memory, and the CPU mostly seems to be bored.
OPNSense 18.1.6