Thanks everyone, HFC is alive again... and I'm up and running. Thankyou for all the suggestions. A couple of things tripped me up: * My attempt to use a different native VLAN didn't work - DHCP wouldn't pick up an IP because it was coming with no VLAN tag / nothing, but the interface was set to a different native VLAN. It's not in the bridge so i figured it really wasn't a big deal. * It kept using the old ADSL connection as the default route. Both had a routing cost of 1, but the new route had a flag "DS" instead of DAC and would only route to the next hop. I ended up modifying the routing cost of the ADSL to get around this. Now the ADSL is higher than the NBN, so effectively it's unused (which is fine). I'll leave the ADSL connected for a while until I'm satisfied that the NBN is actually working ok. * IPSEC just got really unhappy. It refused to connect on either the old WAN or new WAN. in the end I moved the VPN to the new WAN, but the thing that messed it up was that the /ip ipsec policy just borked - they had the old sa-src-address in there. So I updated that using /ip ipsec policy edit 1 sa-src-address <update to new IP> peer peer1 #This had become null and wasn't working after that it all started working and it's working well now. I've compared backups of the config and it looks like it freaked out and corrupted the peer value, and then because there was no peer it didn't update the sa-src-address values. getting 92/40 so pretty happy with that... so long as HFC doesn't fall over again... Cheers, Chris