svc:/network/routing/route:default usually is not needed nowadays
Assigning routes statically or getting them via DHCP is a much more common case today than getting them via RIP or IRDP. There's little to no use in having routed enabled by default nowadays.
Updated by C Fraire over 3 years ago
I have a patch to net-routing-setup to also examine /etc/inet/static_routes early when determining defrouters. This way, default static routes will also cause net-routing-setup to disable routeadm/default-ipv4-routing.
net-routing-setup already iterates through /etc/inet/static_routes as the last stage in its processing for "Adding persistent routes:", so this could not be considered a major change to the script.
Updated by Gordon Ross about 3 years ago
I've run into this annoyance too. If one uses "route -p ..." to setup a default route,
at some later date (i.e. after some sleep/resume cycles on a laptop) one may
discover that in.routed has removed the static route.
Note, "route -p ..." stores the persistent state in /etc/inet/static_routes.
Work around: create /etc/defaultrouter instead.