Project

General

Profile

Actions

Bug #14006

open

ipv4-routing should not be enabled by default

Added by Joshua M. Clulow 10 months ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
networking
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:

Description

As per routeadm, a system that does not have an /etc/defaultrouter file will default to enabling ipv4-routing. This causes in.routed to run and accept RIP routes from the network.

While this configuration may have made sense in the past, it more than likely gets in the way today. One example is, if you configure an interface with DHCP, you're going to get a default route -- but routing is still enabled because a static default route has not been provided. The operator should have to explicitly enable the dynamic routing facility if that's what they want.


Related issues

Related to illumos gate - Feature #8690: Update net-routing-setup to work for an exclusive-IP, DHCP, non-global zoneNewC Fraire2017-09-29

Actions
Has duplicate illumos gate - Feature #8587: svc:/network/routing/route:default usually is not needed nowadaysDuplicate2017-08-25

Actions
Actions #1

Updated by Joshua M. Clulow 10 months ago

If you see log messages like:

Aug  6 13:16:56 vulcan in.routed[502]: route 0.0.0.0/24 --> 0.0.0.0 nexthop is not directly connected

It's likely because of this. You can disable dynamic routing explicitly via:

# routeadm -d ipv4-routing -u
Actions #2

Updated by Joshua M. Clulow 10 months ago

  • Related to Feature #8690: Update net-routing-setup to work for an exclusive-IP, DHCP, non-global zone added
Actions #3

Updated by David Stes about 1 month ago

  • Is duplicate of Feature #8587: svc:/network/routing/route:default usually is not needed nowadays added
Actions #4

Updated by David Stes about 1 month ago

if network/routing would be removed from the server minimal group,

then you could actually request the opposite : you could request that ipv4-routing is immediately and by default enabled ,
when doing a pkg install routing which would install the routing daemons and immediately enable them.

Actions #5

Updated by David Stes about 1 month ago

for example at the SMF level

<instance name='default' enabled='false' >

could be changed to

<instance name='default' enabled='true' >

for route.xml IF network/routing is removed from the minimal group and installed by the user specifically when they want route:default

Actions #6

Updated by Joshua M. Clulow about 1 month ago

  • Status changed from New to Duplicate

This is indeed effectively a duplicate of #14006.

Actions #7

Updated by Joshua M. Clulow about 1 month ago

  • Is duplicate of deleted (Feature #8587: svc:/network/routing/route:default usually is not needed nowadays)
Actions #8

Updated by Joshua M. Clulow about 1 month ago

  • Has duplicate Feature #8587: svc:/network/routing/route:default usually is not needed nowadays added
Actions #9

Updated by Joshua M. Clulow about 1 month ago

  • Status changed from Duplicate to New
Actions

Also available in: Atom PDF