|
Bugzilla – Full Text Bug Listing |
| Summary: | IPV6_FORWARD remains set, ipv6 ignores router advertisements | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | James Carter <jimc> |
| Component: | YaST2 | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | lnussel |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | openSUSE 11.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
smells like yast2-network done in yast2-network-2.18.15 (checkbox set both IP_FORWARD and IPV6_FORWARD) + documented in help text |
IPv6 router advertisements are sent from a OpenSuSE 10.3 box by radvd-0.9-72. A 32bit i686 system running OpenSuSE 11.1 with an unhacked kernel-pae-2.6.27.7-9.1 and an up-to-date package iproute2-2.6.25-41.24, receives these router advertisements (according to tcpdump), but ignores them, failing to configure either the host's IPv6 address or the default route. There are no ip6tables rules (yet). Other v10.3 machines on the same net do recognize and obey the router advertisements. By an ad-hoc script and diff I discovered: -/proc/sys/net/ipv6/conf/all/forwarding 0 (on 10.3) +/proc/sys/net/ipv6/conf/all/forwarding 1 (on 11.1) When I disabled forwarding the router advertisements were obeyed immediately. This control is set in /etc/init.d/boot.ipconfig (unhacked) according to the variable IPV6_FORWARD which is set (incorrectly) in /etc/sysconfig/sysctl to "yes". The variable was set wrongly because the file was copied from a different machine which *is* a router. In YaST2 under Network Devices / Network Settings / Routing, there is a checkbox for <q>Enable IP Forwarding</q>, which affects IP_FORWARD in /etc/sysconfig/sysctl. Being checked because IP_FORWARD == "yes", if I uncheck it, /etc/sysconfig/sysctl is edited so IP_FORWARD="no", but IPV6_FORWARD remains unchanged as "yes". This is a bug. (Workaround: hand-edit the value.) I suggest that the checkbox should affect both settings, or possibly there should be one checkbox for each. In addition, the rest of the Routing dialog should provide a similar service level as for IPv4, that is, it should accept IPv6 routes, and should edit /etc/radvd.conf accordingly, and should restart this daemon.