[opensuse] does wicked update /etc/resolv.conf with ipv6 RDNSS settings?
James Knott wrote:
I have verified that 13.1 does not use RDNSS, at least when using the KDE network manager. I've filed a bug #916613.
I've googled this some, first it looked like you'd need an rdnssd: http://ubuntuforums.org/showthread.php?t=1560285 However, according to https://bugzilla.novell.com/show_bug.cgi?id=740742 "the rdnssd part is made obsolete by wicked". So far I have not seen /etc/resolv.conf be updated with an IPv6 RDNSS address on any of my 13.2 machines. -- Per Jessen, Zürich (-1.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/06/2015 12:34 PM, Per Jessen wrote:
James Knott wrote:
I have verified that 13.1 does not use RDNSS, at least when using the KDE network manager. I've filed a bug #916613. I've googled this some, first it looked like you'd need an rdnssd:
http://ubuntuforums.org/showthread.php?t=1560285
However, according to
https://bugzilla.novell.com/show_bug.cgi?id=740742
"the rdnssd part is made obsolete by wicked".
So far I have not seen /etc/resolv.conf be updated with an IPv6 RDNSS address on any of my 13.2 machines.
I'm curious about when the KDE network manager updates resolv.conf. It appears to have happened last on Feb. 4, even though I've connected several times since then. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 6 Feb 2015 18:47, James Knott
On 02/06/2015 12:34 PM, Per Jessen wrote:
James Knott wrote:
I have verified that 13.1 does not use RDNSS, at least when using the KDE network manager. I've filed a bug #916613. I've googled this some, first it looked like you'd need an rdnssd:
http://ubuntuforums.org/showthread.php?t=1560285
However, according to
https://bugzilla.novell.com/show_bug.cgi?id=740742
"the rdnssd part is made obsolete by wicked".
So far I have not seen /etc/resolv.conf be updated with an IPv6 RDNSS address on any of my 13.2 machines.
I'm curious about when the KDE network manager updates resolv.conf. It appears to have happened last on Feb. 4, even though I've connected several times since then.
Last I checked the code of "KDE network manager" it reads /etc/resolv.conf checks against the fresh DNS data, and only writes the file when there are diffs (June 2014). IMHO this is the "right" way to do this. For bno#740742, I'm missing the proofing test that wicked does the same job as rdnssd would, until then I'm treading wicked as "hot air only". Same as routing, "Yes, wicked does routing", Bah! Proof is out there otherwise. "wicked" gets a big "nono, full shit" from me for anything beyond basic. And, yes, I'm frustrated, - massivly so - , by 13.2 and later networking. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/06/2015 01:06 PM, Yamaban wrote:
"wicked" gets a big "nono, full shit" from me for anything beyond basic.
And, yes, I'm frustrated, - massivly so - , by 13.2 and later networking.
That's why I reverted back to 13.1 on my notebook computer. I had 13.2 on it for a while, but it had too many problems. 13.1 is the next Evergreen, IIRC, so I'll stick with it for a while. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Freitag, 6. Februar 2015 19:06:25 Yamaban wrote:
Same as routing, "Yes, wicked does routing", Bah! Proof is out there otherwise.
Sure, I had a hard time to explain wicked a static route for an otherwise dhcp (v4) controlled device, and finally succeeded. #907495 Mind giving a brief summary of your routing issue? Networking scripts, including NetworkManager stuff is flaky, and has been that way for a looong time. Only the deficits change (and I'm not covering IPv6 at all..). Oh well. Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 6 Feb 2015 19:50, Hans-Peter Jansen
On Freitag, 6. Februar 2015 19:06:25 Yamaban wrote:
Same as routing, "Yes, wicked does routing", Bah! Proof is out there otherwise.
Sure, I had a hard time to explain wicked a static route for an otherwise dhcp (v4) controlled device, and finally succeeded. #907495
Mind giving a brief summary of your routing issue?
Networking scripts, including NetworkManager stuff is flaky, and has been that way for a looong time. Only the deficits change (and I'm not covering IPv6 at all..).
Oh well. Maybe, what I call routing is not what the wicked-devs call routing.
This is the big routerbox: - One router-box, core 2 duo @ 2 GHz , 64bit, 4GB Ram - LTE-modem ca 4Mbit via USB as fallback, with full IPv6 support - DSL-modem1 ca 12 Mbit via ppp-o-eth0, with full IPv6 support - VDSL-modem2 ca 100Mbit via eth1, IPv6 partial, manual DNS needed - LAN segment1 1GBit via eth2, with full IPv6 support - LAN segment2 1GBit via eth3, with full IPv6 support - DMZ-LAN seg3 1GBit via eth4, with full IPv6 support from intern, IPv4only from extren - WLAN segment1 300MBit 5Ghz only via USB, with full IPv6 support - WLAN segment2 150MBit 2.4/5Ghz via eth5, IPv4 only The Box has 2 GB-eth onboard and 1 PCIe Card 4x GB-eth It runs dnsmasq for dhcp and dns relay In OSS 13.1 it took me about 2 days to get it fully working, with IFup/-down config and scripts, incl. Firewall rules. Not trivial, but do-able. So far I have not found any way to produce a comparable routing with wicked. Even smaller things like: One box, 2 eth onboard: - DSL-modem via eth0, - LAN segment1 via eth1, - WLAN segment2 via USB, - DMZ in VM (on routerbox) runs dnsmasq for dhcp (LAN/WLAN) and dns relay Rules: 1. LAN and WLAN shall see Internet and DMZ, but not each other. 2. Full IPv4 and IPv6 support. Simple, but try that in wicked, please, show with examples. Is not really configurable with wicked, two weeks and nothing to show. Frust and Anger is all I got on wicked so far, for anything beyond basic client / server with only one network interface. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Hans-Peter Jansen -
James Knott -
Per Jessen -
Yamaban