From Fedora Project Wiki
< Tools | NetworkManager
(Created page with "== 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 resolve using th...") |
No edit summary |
||
| Line 1: | Line 1: | ||
== Kernel == | |||
* 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 | |||
== dnssec-trigger == | == dnssec-trigger == | ||
Revision as of 15:13, 13 July 2012
Kernel
- 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
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 resolve using the global DNS systems. This is incompatible with VPNs with their own private DNS zones.
firewalld
NetworkManager supports firewall zones for firewalld.