https://bugzilla.novell.com/show_bug.cgi?id=458891 Summary: Cannot set IPv6 default gateway Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mstopka@opensuse.org QAContact: qa@suse.de Found By: --- IPv6 support in YaST is not so good yet, because YaST make ma able to set an IPv6 addresses for interfaces, but not make me able to set default IPv6 gateway. Currently I can set addresses like this: 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:16:d4:61:ae:81 brd ff:ff:ff:ff:ff:ff inet 82.209.54.76/29 brd 82.209.54.79 scope global eth0 inet6 2001:15c0:668e::2/48 scope global valid_lft forever preferred_lft forever inet6 2002:52d1:364a::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::216:d4ff:fe61:ae81/64 scope link valid_lft forever preferred_lft forever but I have two choices I can set default IPv4 gateway like default via 82.209.54.73 dev eth0 or IPv6 gateway, not both so dual stack IPv4 and IPv6 is not possible, at least not easily possible only using YaST. I can set as default gateway 2001:15c0:668e::1 but then I have IPv6 up and running, but not IPv4 for global communication, only for 82.209.54.72/29. I think YaST should detect if there is any IPv6 address on any interface (?except loopback) and if so, YaST should show one more field for default gateway marked like "Default IPv6 gateway". I think something like this would be fine also for IPv4 networking... I mean if there is no IPv4 address on any interface (?except loopback) YaST should not show me an field marked as "Default gateway"... Or to be more precise I think "Default gateway" field should be renamed as "IPv4 default gateway" and this one filed should not be seeing if there is no IPv4 address on any interface. -- 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.