Project

General

Profile

Actions

Bug #14006

open

ipv4-routing should not be enabled by default

Added by Joshua M. Clulow 4 months ago. Updated 4 months 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
Actions #1

Updated by Joshua M. Clulow 4 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 4 months ago

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

Also available in: Atom PDF