Classless static routes issue in 19.7.2

[rhartmannh]

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?

[hbc]

You must use "STRING" not "TEXT" as option type.

The text data type specifies an NVT ASCII string, which must be enclosed in double quotes - for example, to specify a root-path option [...]

The string data type specifies either an NVT ASCII string enclosed in double quotes, or a series of octets specified in hexadecimal, separated by colons.

https://ercpe.de/blog/advanced-dhcp-options-pushing-static-routes-to-clients

[rhartmannh]

Thanks a lot! Works for me now.