Hello fellow NZers. Chorus recently enabled DHCP Auth on their network, so then a number of ISPs followed and enabled DHCP on their networks. Where this becomes sticky is when assigning a single static ip - a /32 PPPoE is fine, that just works, however with DHCP assigning a static /32 its a bit trickier. This is where RFC 3442 comes in. DHCP Option 121 inserts a classless static route into the request to ensure there is a default route, e.g 0.0.0.0/0 via ISP default gateway. Here is an example in RouterOS /ip dhcp-server optionadd code=121 name=Classless-Route value=0x20C0A8640100000000202278FFF40000000000647FFF05 /ip dhcp-server networkadd ... dhcp-option=Classless-Route ...  What I discovered is that Netcomm devices don't respond to DHCP option 121 so can not use them for DHCP WAN with a /32 IP. You can not set a manual default route. Which means a decent number of ISPs who use these will have to stick to PPPoE Where I am going with this, is that I attempted to set my MX at home to DHCP for the WAN, and the same thing happens. DHCP assigns the WAN IP to the interface, however I can not browse the internet / ping / tracert as my guess is that the MX is not responding to DHCP option 121. I,ve spoken to the owner of the ISP as we have a close relationship and their auth servers are doing exactly the right thing, and the issue is with the firewall. During the testing, i used both an RB5009 mikrotik, and a Unifi UDM Pro, and both picked up the IP and had its route set via option 121 and just worked. I have a case open with support. I want to see if other partners in NZ have this issue with MX's or if they are using them on DHCP. One thing to point out is that DHCP makes the MX a true zero touch deployment, and also reducing CPU overheads when not using PPPoE. Cheers Sean ... View more