Tools/NetworkManager/Integration: Difference between revisions

Revision as of 09:14, 24 July 2012

NM does't get notified about router advertisements and flag changes → we ask kernel upon any recieved route
NM doesn't get notified about gateways when accept_ra_defrtr=0
Kernel doesn't cache RDNSS and DNSSL, so we have to send router solicitation on NetworkManager start
NM can't trigger kernel router solicitation
Manually sent router solicitations give EADDRNOTAVAIL (link-local is there according to netlink)
Kernel doesn't treat dhcpv6 replies as ESTABLISHED, this is worked around by firewalld
Kernel autoconfigures link-local (and possibly also global) IPv6 addresses for bridge/bond members (I haven't tested this)

NetworkManager doesn't work well with dnssec-trigger as unbound DNS server will not recieve the list of recursive nameservers and will thusresolve using the global DNS systems. This is incompatible with VPNs with their own private DNS zones.
dnssec-triggerd leaves broken /etc/resolv.conf on exit

NetworkManager supports firewall zones for firewalld.

@@ Line 11: / Line 11: @@
 == dnssec-trigger ==
-NetworkManager doesn't work well with dnssec-trigger as unbound DNS server will not recieve the list of recursive nameservers and will thus
+* NetworkManager doesn't work well with dnssec-trigger as unbound DNS server will not recieve the list of recursive nameservers and will thusresolve using the global DNS systems. This is incompatible with VPNs with their own private DNS zones.
-resolve using the global DNS systems. This is incompatible with VPNs with their own private DNS zones.
+* [https://bugzilla.redhat.com/show_bug.cgi?id=842455 dnssec-triggerd leaves broken /etc/resolv.conf on exit]
 == firewalld ==