Bug 680643 - NM doesn't configure IPv6 default route properly
Summary: NM doesn't configure IPv6 default route properly
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 15
Hardware: i386
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-26 17:19 UTC by A.J. Werkman
Modified: 2012-05-05 17:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-05 17:53:33 UTC
Type: ---


Attachments (Terms of Use)

Description A.J. Werkman 2011-02-26 17:19:32 UTC
Description of problem:
NetworkManager does not configure the IPv6 default route properly. It makes a default route to a device. As I understand, this is only useful on a point-to-point connnection. Instead it should make a default route through a via <IP-address>.

Version-Release number of selected component (if applicable):
NetworkManager-0.8.2-8.git20101117.f15

How reproducible:
Everytime

Steps to Reproduce:
1. Install Fedora using static IPv6 routing
2. Try to ping6 a host outside the local subnet
  
Results:
/etc/sysconfig/network-scripts/ifcfg-pci10p1

IPV6_DEFAULTGW="2001:838:3ab:1::1"
IPV6INIT="yes"
NM_CONTROLLED="yes"
DNS1="2001:838:3ab:1::1"
IPV6_AUTOCONF="no"
DEVICE="pci10p1"
IPV6ADDR="2001:838:3ab:1::12/64"
ONBOOT="yes"
HWADDR=00:26:18:F1:92:4E
TYPE=Ethernet
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME="System pci10p1"
UUID=bff46ec1-50db-b49a-80d1-782e6761c691
LAST_CONNECT=1298731988

# ip -6 route show

2001:838:3ab:1::/64 dev pci10p1  proto kernel  metric 256 
unreachable fe80::/64 dev lo  proto kernel  metric 256  error -101
fe80::/64 dev pci10p1  proto kernel  metric 256 
default dev pci10p1  proto static  metric 1024 

This is the situation after booting into the system. Now ping6 a host outside the subnet and see that it doesn't ping.

Next do:

# ip -6 route del ::/0 dev pci10p1

# ip -6 route add ::/0 via 2001:838:3ab:1::1

# ip -6 route show

2001:838:375:2::1 via 2001:838:3ab:1::1 dev pci10p1  metric 0 
    cache 
2001:838:3ab:1::/64 dev pci10p1  proto kernel  metric 256 
unreachable fe80::/64 dev lo  proto kernel  metric 256  error -101
fe80::/64 dev pci10p1  proto kernel  metric 256 
default via 2001:838:3ab:1::1 dev pci10p1  metric 1024 

After this reconfiguration do a ping6 to the host outside the subnet and see that the ping is responded.

This shows that NetworkManager should configure routing as in the later example.


Additional info:

Comment 1 Dan Williams 2011-05-25 23:18:56 UTC
Is this still the case with latest updates?

Comment 2 Dan Winship 2012-05-03 19:32:57 UTC
Seems to work fine for me, with an IPv6 address configured vi nm-connection-editor. Is this still a problem for you?

Comment 3 A.J. Werkman 2012-05-05 17:53:33 UTC
I don't see the problem here neither anymore. I close this one.


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