Nat disabling dhcp??? after 6.2.45 update

RouterOS General
1

Hi all,
I have a bunch of field routers utilising the hex poe (RB960PGS) with a cellular 4g dongle as the only way to connect to the internet. All ports are bridged due to the dongle. Playing around while setting up my next batch for deployment I noticed something weird in version 6.2.45

If I enable Nat in the quick config page on initial setup the dhcp server refuses to start.

Additionally I couldnt preference the lte dongle distance over my vpn client connection, under ip>dhcp client the field is blocked for editing. Now it prefers the vpn route. I have to add mangle and routing rules to effectively perform “local breakout”.

It’s not a deal breaker but it changes my ability to automate as I have for 6 months.

2

sorry that should read version 6.42.5 (late night)

3

Don’t use quick config, use manual config via winbox windows.

4

When I perform the initial config I use Quick Config, from then on I setup vpn and exclusively use winbox.
Even if I were using quick config after initial config, doing this should not cause DHCP to die!
Besides, I said I enable NAT during initial config in quick config.