[Bug 572202] New: ipv6 stateless autoconfiguration (SLAAC) doesn't work
http://bugzilla.novell.com/show_bug.cgi?id=572202 http://bugzilla.novell.com/show_bug.cgi?id=572202#c0 Summary: ipv6 stateless autoconfiguration (SLAAC) doesn't work Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: wjontofs@atriumberlin.de QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.6) Gecko/20091201 SUSE/3.5.6-1.1.1 Firefox/3.5.6 ipv6 stateless autoconfiguration (SLAAC) doesn't work: ipv6 is enabled, link local address is assigned, router advertisments arrive (sniffed with wireshark), nevertheless, SLAAC doen't occur, no global address is assigned. The same machine has no such problems with opensuse 11.1 (other distribution like ubuntu 9.10 work either). /proc/sys/net/ipv6/conf/all/autoconf is set to "1" /proc/sys/net/ipv6/conf/eth0/autoconf is set to "1" Reproducible: Always Steps to Reproduce: 1.ip address shows only link local ipv6 address 2. 3. Expected Results: assign ipv6 address in accordance with tthe router advertisements received -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=572202 http://bugzilla.novell.com/show_bug.cgi?id=572202#c yang xiaoyu <xyyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |jarrington@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c1 Ian Monroe <novell@monroe.nu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |novell@monroe.nu --- Comment #1 from Ian Monroe <novell@monroe.nu> 2011-02-15 01:08:51 UTC --- I'm new to this IPv6 like most people, but I seemed to have had the same issue. radvdump shows that my router (a netgear WNDR3700 set to 'auto config' for ipv6 as opposed to dhcp) sending advertisements. However I only ever had a link local address until I set a ipv6 address statically. With opensuse 11.3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c2 Aaron Burgemeister <aburgemeister@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jarrington@novell.com |rwagner@novell.com --- Comment #2 from Aaron Burgemeister <aburgemeister@novell.com> 2011-02-17 17:14:28 UTC --- Reassigning PM-ish stuff to PM. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c3 --- Comment #3 from Walter Jontofsohn <wjontofs@atriumberlin.de> 2011-04-07 09:05:21 UTC --- With opensuse-11.3 I can't reproduce the problem. Still on the same hardware, the problem seems solved for me with the newer version of the distribution (opensuse-11.3). @Ian Monroe: did assure that icmpv6 router advertisement messages are not blocked on your host? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c4 andrea florio <andrea@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrea@opensuse.org --- Comment #4 from andrea florio <andrea@opensuse.org> 2011-10-23 12:21:35 UTC --- i'm having the same issue: linux-kenv:~ # cat /proc/sys/net/ipv6/conf/*/autoconf 1 1 1 1 1 1 1 1 linux-kenv:~ # ip -f inet6 addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000 inet6 fe80::221:ff:fe0c:724f/64 scope link valid_lft forever preferred_lft forever 4: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000 inet6 fe80::250:56ff:fec0:1/64 scope link valid_lft forever preferred_lft forever 5: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000 inet6 fe80::250:56ff:fec0:8/64 scope link valid_lft forever preferred_lft forever 6: vboxnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000 inet6 fe80::800:27ff:fe00:0/64 scope link valid_lft forever preferred_lft forever i'm using network manager on suse 11.4 though.. windows 7 works flawless... gonna try with ifup with nm.. let see if it make any difference -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c5 andrea florio <andrea@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Network |Network AssignedTo|rwagner@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com Product|openSUSE 11.2 |openSUSE 11.4 --- Comment #5 from andrea florio <andrea@opensuse.org> 2011-10-24 08:08:54 UTC --- even with ifup it won't work. i also double checked my cisco 1841 router config and it's fine. again only suse won't get the autoconfig! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c zj jia <zjjia@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@suse.com AssignedTo|bnc-team-screening@forge.pr |bili@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c6 Li Bin <bili@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bili@suse.com |mt@suse.com --- Comment #6 from Li Bin <bili@suse.com> 2011-10-25 07:27:40 UTC --- Marius, Assign to you. Any idea? Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c7 --- Comment #7 from andrea florio <andrea@opensuse.org> 2011-10-25 07:49:08 UTC --- is there any sysctl config we need to have? i'm ready to make any required test, and provide router ipv6 config if needed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c8 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |wjontofs@atriumberlin.de --- Comment #8 from Marius Tomaschewski <mt@suse.com> 2011-10-25 08:21:19 UTC --- At the moment I don't have any idea what this could be... works for me. Did you enabled ipv6 forwarding? For example by adding: net.ipv6.conf.all.forwarding = 1 (with "default" or interface name instead of "all"?) to /etc/sysctl.conf or /etc/sysconfig/network/ifsysctl or by setting the IPV6_FORWARD=yes variable in /etc/sysconfig/sysctl (DEPRECATED)? Enabling ipv6 forwarding on a host disables autoconfig. Could you attach the "radvdump" output? You can make your ipv6 addresses anonymous if you like, e.g. by replacing the prefix with 2001:DB8: ... (the documentation prefix). In stateless case it should look like this (only the most important flags): interface eth0 { AdvManagedFlag off; # get IP-Address via dhcpv6 AdvOtherConfigFlag off; # get Other config via dhcpv6 prefix 2001:DB8:aaaa::/64 { AdvAutonomous on; # Allows host to assign address itself } } [in statefull autoconf case at least the AdvManagedFlag is on]. Further, please also attach the /etc/sysconfig/network/ifcfg-eth0 file and the "sysctl net.ipv6.conf.all ; sysctl net.ipv6.conf.eth0" and the output of "ifstatus eth0". Please replace "eth0" with the interface name you're using. I don't know if this matters (don't remember what virtualbox is doing), but looking on the interfaces in comment 4...: Important kernel difference on 11.4 or newer is that the order of bridge and vlan processing has been inverted: a bridge is processed before vlan. This causes, that when there is a vlan and a bridge on the same physical interface (e.g. vlan42 or eth0.42 on eth0 and eth0 is port in br0), then the vlan interface does not work any more, because the bridge "eats" the traffic. The vlan has to be on top of the bridge for newer kernels. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c9 andrea florio <andrea@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|wjontofs@atriumberlin.de | --- Comment #9 from andrea florio <andrea@opensuse.org> 2011-10-25 17:31:21 UTC --- (In reply to comment #8)
At the moment I don't have any idea what this could be... works for me. Did you enabled ipv6 forwarding? For example by adding:
net.ipv6.conf.all.forwarding = 1
(with "default" or interface name instead of "all"?)
to /etc/sysctl.conf or /etc/sysconfig/network/ifsysctl or by setting the IPV6_FORWARD=yes variable in /etc/sysconfig/sysctl (DEPRECATED)?
Enabling ipv6 forwarding on a host disables autoconfig.
that was the issue. i set it manually to 0 and it now worked p.s. i never manually apply that line to sysctl myself. i added both lines setting it to 0 and it worked.
Could you attach the "radvdump" output? You can make your ipv6 addresses anonymous if you like, e.g. by replacing the prefix with 2001:DB8: ... (the documentation prefix).
In stateless case it should look like this (only the most important flags):
interface eth0 { AdvManagedFlag off; # get IP-Address via dhcpv6 AdvOtherConfigFlag off; # get Other config via dhcpv6
prefix 2001:DB8:aaaa::/64 { AdvAutonomous on; # Allows host to assign address itself } }
[in statefull autoconf case at least the AdvManagedFlag is on].
linux-kenv:~ # radvdump # # radvd configuration generated by radvdump 1.3 # based on Router Advertisement from fe80::217:5aff:fe0c:ece7 # received by interface wlan0 # interface wlan0 { AdvSendAdvert on; # Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump AdvManagedFlag off; AdvOtherConfigFlag on; AdvReachableTime 0; AdvRetransTimer 0; AdvCurHopLimit 64; AdvDefaultLifetime 1800; AdvHomeAgentFlag off; AdvDefaultPreference medium; AdvSourceLLAddress on; AdvLinkMTU 1500; prefix 2001:470:1f09:XXXX::/64 { AdvValidLifetime 2592000; AdvPreferredLifetime 604800; AdvOnLink on; AdvAutonomous on; AdvRouterAddr off; }; # End of prefix definition }; # End of interface definition
Further, please also attach the /etc/sysconfig/network/ifcfg-eth0 file and the "sysctl net.ipv6.conf.all ; sysctl net.ipv6.conf.eth0" and the output of "ifstatus eth0".
Please replace "eth0" with the interface name you're using.
I don't know if this matters (don't remember what virtualbox is doing), but looking on the interfaces in comment 4...:
Important kernel difference on 11.4 or newer is that the order of bridge and vlan processing has been inverted: a bridge is processed before vlan.
This causes, that when there is a vlan and a bridge on the same physical interface (e.g. vlan42 or eth0.42 on eth0 and eth0 is port in br0), then the vlan interface does not work any more, because the bridge "eats" the traffic. The vlan has to be on top of the bridge for newer kernels.
that's not the case, since as i said, after making the first change you mentioned it worked! thank you -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c10 --- Comment #10 from andrea florio <andrea@opensuse.org> 2011-10-25 17:35:11 UTC --- more infos: Oct 25 19:32:50 linux-kenv NetworkManager[1781]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) starting DHCPv6 as requested by IPv6 router... Oct 25 19:32:50 linux-kenv NetworkManager[1781]: <error> [1319563970.655392] [nm-device.c:1621] dhcp6_start(): (wlan0): failed to add IPv6 multicast route: Netlink Error (errno = File exists) Oct 25 19:32:50 linux-kenv NetworkManager[1781]: <info> Activation (wlan0) Beginning DHCPv6 transaction (timeout in 45 seconds) Oct 25 19:32:50 linux-kenv NetworkManager[1781]: <info> dhclient started with pid 10505 Oct 25 19:32:51 linux-kenv NetworkManager[1781]: <info> (wlan0): DHCPv6 state changed nbi -> renew6 Oct 25 19:32:51 linux-kenv NetworkManager[1781]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) scheduled... Oct 25 19:32:51 linux-kenv NetworkManager[1781]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) started... Oct 25 19:32:51 linux-kenv NetworkManager[1781]: <info> nameserver '2620:0:ccc::2' Oct 25 19:32:51 linux-kenv NetworkManager[1781]: <info> nameserver '2620:0:ccd::2' Oct 25 19:32:51 linux-kenv NetworkManager[1781]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) complete. Oct 25 19:32:51 linux-kenv NetworkManager[1781]: <info> (wlan0): DHCPv6 client pid 10505 exited with status 0 linux-kenv:~ # ip -f inet6 addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000 inet6 2001:470:1f09:1d66:221:ff:fe0c:724f/64 scope global dynamic valid_lft 2591935sec preferred_lft 604735sec inet6 fe80::221:ff:fe0c:724f/64 scope link valid_lft forever preferred_lft forever 4: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000 inet6 fe80::250:56ff:fec0:1/64 scope link valid_lft forever preferred_lft forever 5: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000 inet6 fe80::250:56ff:fec0:8/64 scope link valid_lft forever preferred_lft forever linux-kenv:~ # cat /etc/resolv.conf ### /etc/resolv.conf file autogenerated by netconfig! # # Before you change this file manually, consider to define the # static DNS configuration using the following variables in the # /etc/sysconfig/network/config file: # NETCONFIG_DNS_STATIC_SEARCHLIST # NETCONFIG_DNS_STATIC_SERVERS # NETCONFIG_DNS_FORWARDER # or disable DNS configuration updates via netconfig by setting: # NETCONFIG_DNS_POLICY='' # # See also the netconfig(8) manual page and other documentation. # # Note: Manual change of this file disables netconfig too, but # may get lost when this file contains comments or empty lines # only, the netconfig settings are same with settings in this # file and in case of a "netconfig update -f" call. # ### Please remove (at least) this line when you modify the file! search site nameserver 8.8.8.8 nameserver 8.8.4.4 nameserver 2620:0:ccc::2 i am wondering.. why forwarding was enable? i enabled from yast "enable ip forwarding" but there never was "enable ipv6 forwarding" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c11 --- Comment #11 from Marius Tomaschewski <mt@suse.com> 2011-10-25 18:26:32 UTC --- (In reply to comment #10)
i am wondering.. why forwarding was enable? i enabled from yast "enable ip forwarding" but there never was "enable ipv6 forwarding"
I guess, there were/is only one switch in yast2 that enables it for both. $ grep forward $(rpm -ql yast2-network) .. /usr/share/YaST2/modules/Routing.ycp: * Enable IP forwarding /usr/share/YaST2/modules/Routing.ycp: SCR::Execute(.target.bash, sformat("echo %1 > /proc/sys/net/ipv4/ip_forward", /usr/share/YaST2/modules/Routing.ycp: SCR::Execute(.target.bash, sformat("echo %1 > /proc/sys/net/ipv6/conf/all/forward .. /usr/share/YaST2/modules/Routing.ycp: .. void WriteIPForwarding() { if ( SuSEFirewall::IsEnabled() ){ SuSEFirewall::SetSupportRoute( Forward ); } else { SCR::Write(.sysconfig.sysctl.IP_FORWARD, Forward ? "yes" : "no"); SCR::Write(.sysconfig.sysctl.IPV6_FORWARD, Forward ? "yes" : "no"); SCR::Write(.sysconfig.sysctl, nil); } SCR::Execute(.target.bash, sformat("echo %1 > /proc/sys/net/ipv4/ip_forward", Forward ? 1 : 0)); SCR::Execute(.target.bash, sformat("echo %1 > /proc/sys/net/ipv6/conf/all/forwarding", Forward ? 1 : 0)); } .. Exactly, yast2 has only one switch for both. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c12 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mt@suse.com |mvidner@suse.com --- Comment #12 from Marius Tomaschewski <mt@suse.com> 2011-10-25 18:34:25 UTC --- -> yast2-network maintainer Martin, there is one point for your todo list: the forwarding switch needs a split. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c13 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mt@suse.com --- Comment #13 from Marius Tomaschewski <mt@suse.com> 2011-10-25 18:37:14 UTC --- BTW: Setting of /etc/sysconfig/sysctl often does not work and is DEPRECATED. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c14 andrea florio <andrea@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Network |YaST2 AssignedTo|mvidner@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com Summary|ipv6 stateless |yast2 : enable ip |autoconfiguration (SLAAC) |forwarding need to bl split |doesn't work |in "ip forwarding" and | |"ipv6 forwarding" QAContact|qa@suse.de |jsrain@suse.com OS/Version|openSUSE 11.2 |openSUSE 11.4 --- Comment #14 from andrea florio <andrea@opensuse.org> 2011-10-25 20:28:55 UTC --- (In reply to comment #12)
-> yast2-network maintainer
Martin, there is one point for your todo list: the forwarding switch needs a split.
and a note that enabling that feature, stateless autoconfig won't work should be also added. thank again for your help. i'm editing the bug name to make it match the real bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c andrea florio <andrea@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |mvidner@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c16 Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |fehr@suse.com, | |meissner@suse.com --- Comment #16 from Michal Filka <mfilka@suse.com> 2013-09-26 12:09:47 UTC --- I did changes on YaST side. However, update in AutoYaST and SuSEfirewall2 will be needed too. Ccing maintainers. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c17 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |mfilka@suse.com --- Comment #17 from Thomas Fehr <fehr@suse.com> 2013-09-26 12:36:36 UTC --- Which updates regarding base autoyast code do you mean? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c18 Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |YaST2 Version|Final |13.1 Beta 1 AssignedTo|mfilka@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com Product|openSUSE 11.4 |openSUSE Factory --- Comment #18 from Michal Filka <mfilka@suse.com> 2013-09-27 08:43:46 UTC --- I've updated product, as the issue is valid even for current version. @Thomas: Adding a key(s) to profile. I never did it before. Thanks for explaining it here: https://github.com/yast/yast-network/pull/116#discussion_r6601425 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED CC| |mfilka@suse.com InfoProvider|mfilka@suse.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |mfilka@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c Martin Vidner <mvidner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner@suse.com Summary|yast2 : enable ip |IPv6 stateless |forwarding need to bl split |autoconfiguration (SLAAC) |in "ip forwarding" and |doesn't work: YaST IP |"ipv6 forwarding" |Forwarding must distinguish | |IPv4/IPv6 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c19 --- Comment #19 from Martin Vidner <mvidner@suse.com> 2013-09-27 18:03:22 CEST --- https://github.com/yast/yast-network/pull/116 reviewed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c20 Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |Basesystem Version|13.1 Beta 1 |RC 1 AssignedTo|mfilka@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com Product|openSUSE Factory |openSUSE 13.1 QAContact|jsrain@suse.com |qa-bugs@suse.de --- Comment #20 from Michal Filka <mfilka@suse.com> 2013-10-16 07:04:53 UTC --- yast2-network updated. Changes are available in 3.1.1 Separate setup is available in UI, CLI and AY. However, for full support of the feature, SuSEfirewall2 has to be updated too. Particularly I speak about this function which supports IPv4 only: # Turn ip forwarding on if configured switch_on_ip_forwarding() { if [ "$FW_ROUTE" = yes ]; then setproc 1 /proc/sys/net/ipv4/ip_forward else setproc 0 /proc/sys/net/ipv4/ip_forward fi } Reassigning to SuSEfirewall2 maintainer. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c Martin Vidner <mvidner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |lnussel@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=572202 https://bugzilla.novell.com/show_bug.cgi?id=572202#c21 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@suse.com AssignedTo|lnussel@suse.com |meissner@suse.com --- Comment #21 from Ludwig Nussel <lnussel@suse.com> 2013-10-16 13:34:53 CEST --- Maintainer is Marcus. I'd not add IPv6 support at that place in SuSEfirewall2. Instead the code for ipv4 there should be removed. YaST should set the sysctl settings itself instead. SuSEfirewall2 could warn if they are set incorrectly but not set them. It's a legacy mistake that just introduces two places to configure things. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com