General • DHCP Client Default Route in VRF Missing @vrf Suffix on Gateway

I have configured a VRF (vrf-LTE) on my MikroTik router and assigned ether2 to it. When I add a DHCP client on ether2, the default route is initially placed in the main routing table instead of vrf-LTE.

To fix this, I set the default-route-table option in the DHCP client to vrf-LTE. This successfully moves the default route to the correct VRF table. However, the gateway does not include the @vrf-LTE suffix, making it unreachable.
Version 7.18.2
Steps to Reproduce:

Create a VRF and assign ether2 to it:Add a DHCP client on ether2 with default-route-table=vrf-LTE:






Observe the default route appearing in vrf-LTE, but the gateway is missing the @vrf-LTE suffix.

Expected Behavior:

The default route should be created in vrf-LTE with the gateway properly formatted as GATEWAY_IP@vrf-LTE.

Actual Behavior:

The gateway is missing the @vrf-LTE suffix, making the route unreachable.

Workaround (Temporary Fix):

Manually add the correct default route:
Request:
Could this behavior be fixed so that the DHCP-acquired gateway is automatically assigned to the correct VRF?

Statistics: Posted by irghost — Thu Mar 27, 2025 11:39 pm

---