Cannot set default IPv4 route on new container creation

[rucarrol]

Overall, I'm really liking TrueNAS SCALE - congrats on an excellent job overall, especially for a beta!

I wanted to add a minor bug report: When adding a new container ("Launch Docker Image" from Apps on the sidebar), if you select static IP addressing, you:

• Cannot select /0 from the dropdown to install 0.0.0.0/0 (aka "default")
• Inserting 0.0.0.0/1 (Valid - route for bottom half of IPv4 space) reports invalid route
• Inserting 128.0.0.0/1 (Valid - route for top half of IPv4 space) results in...well the semi-default installed

# netstat -rn | grep net1
128.0.0.0 192.168.0.1 128.0.0.0 UG 0 0 0 net1
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 net1

• No option to disable the internal K8S interface/IPAM:

# netstat -rn | grep eth0
0.0.0.0 172.16.0.1 0.0.0.0 UG 0 0 0 eth0
172.16.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
(So in this case, if the IP exists in the top half of the IPv4 space, we'll use net1, otherwise we follow the default to eth0.. A little bit messy)

So, overall, I'd expect one of two options, as well as a "disable internal networking" option:

• Checkbox to indicate "default" route
• Ability to pick /0 from dropdown and insert 0.0.0.0 as route

Cheers