Bug 1030813 - No error when duplicate default routes added in routing table
No error when duplicate default routes added in routing table
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: iproute (Show other bugs)
7.0
All Linux
high Severity medium
: rc
: ---
Assigned To: Petr Šabata
BaseOS QE Security Team
: Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-15 03:40 EST by Guangze Bai
Modified: 2015-02-08 16:39 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-15 04:08:25 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Guangze Bai 2013-11-15 03:40:00 EST
Description of problem:


Version-Release number of selected component (if applicable):
In a RHEL7 guest, the initial routing table is:

# ip r s
default via 192.168.122.1 dev eth0  proto static  metric 1024 
192.168.122.0/24 dev eth0  proto kernel  scope link  src 192.168.122.16

# ip route add default via 192.168.122.1 dev eth0  proto static

No error shown and check it again:

# ip r s
default via 192.168.122.1 dev eth0  proto static 
default via 192.168.122.1 dev eth0  proto static  metric 1024 
192.168.122.0/24 dev eth0  proto kernel  scope link  src 192.168.122.16 

There are two default routes. That's the problem.

How reproducible:
always

Expected results:
Ban adding the duplicate in routing table.

Additional info:
Comment 1 Guangze Bai 2013-11-15 03:42:12 EST
Forgot to say, I use following to reproduce:

iproute-3.10.0-6.el7.x86_64
kernel-3.10.0-48.el7.x86_64
Comment 3 Petr Šabata 2013-11-15 04:08:25 EST
This is not a bug, let alone a regression.  If anything, this is an RFE.  Adding identical routes with different metrics has always been possible.

Even though it doesn't make much sense at first, there may be some scenarios where users could want this.

Note You need to log in before you can comment on or make changes to this bug.