If I set something like this:
/ip dhcp-server option
add code=252 name=1000M100M value=“‘test’”
works just fine, but if I pick the next code in the reserved space:
/ip dhcp-server option
add code=253 name=1000M100M value=“‘test’”
It doesn’t set the option. Why do some reserved options work and others don’t? The documentation (https://help.mikrotik.com/docs/display/ROS/DHCP#DHCP-DHCPOptions.1) seems to suggest I can put any option code between 1..254, but I can’t seem to get it to work unless I use very specific ones that I’ve guessed.
I see, the client didn’t request that attribute I want to send.
The actual problem is that I want to get something from my radius server into the dhcp script called on lease. If add
Mikrotik-DHCP-Option-Param-STR1 = foo
to my radius server
then create a option with that var:
/ip dhcp-server option
add code=43 name=test value=“$(RADIUS_MT_STR1)”
Then I can get my foo variable in my lease-script:
1 name=“dhcp” owner=“admin” policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon dont-require-permissions=no last-started=2024-06-06 14:39:15 run-count=60 source=
:if ($“leaseBound” =1) do={
:local VendorSpecific ($“lease-options”->“43”)
:log info “Lease Option 43 (Vendor-Specific) is $VendorSpecific”
}
Trouble is that I only get this if the client asks for this attribute. What I would really like instead is for $(RADIUS_MT_STR1) to show up as a variable in the lease-script that way I can pass information from radius into the script regardless if the client asks for it or not.