mirror of
git://git.openembedded.org/meta-openembedded
synced 2026-01-04 16:10:10 +00:00
a8ebf23dde
The current handling of /etc/resolv.conf by NM has some problems. When networkd is not configuring network, and there's 'ip=dhcp' in kernel command line, the /run/NetworkManager/resolv.conf file is not created, resulting in /etc/resolv.conf being a dead symlink. This is because NM is treating the network interface as externally configured and will not try to reconfigure it again. This means if we want NM to work properly with /etc/resolv.conf, we've got to either ensure there's no 'ip=dhcp' in kernel command line, or we've got to ensure networkd is configuring network. This is weird because normally we should not enable two network managers at the same time. Note that NM syncs part of its codes with networkd, which is the reason I think it happens to work when these two network configuration tools are configuring the same interface at the same time. In fact, NM now works well with resolved. It sends the DNS info it gets to resolved unconditionally by default (the behavior could be disabled in configuration file). Looking at the original commit that sets up the update-alternatives mechanism, it says: """ This brings the networkmanager in sync with how systemd-resolved and connman work. Additionally this allows it to function with a read-only rootFS. """ I guess the author was using systemd but disabling resolved, and the author wanted to use read-only rootFS. In order to keep such combination still works, change to use PACKAGECONFIG to handle things, and when 'man-resolv-conf' is enabled, the above combination could still work. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> |
||
|---|---|---|
| .. | ||
| classes | ||
| conf | ||
| dynamic-layers/meta-python/recipes-connectivity | ||
| files/waf-cross-answers | ||
| licenses | ||
| recipes-connectivity | ||
| recipes-core | ||
| recipes-daemons | ||
| recipes-devtools | ||
| recipes-extended | ||
| recipes-filter | ||
| recipes-irc | ||
| recipes-kernel/wireguard | ||
| recipes-netkit | ||
| recipes-protocols | ||
| recipes-support | ||
| COPYING.MIT | ||
| MAINTAINERS | ||
| README | ||
meta-networking
===============
This layer is intended to be a central point for networking-related
packages and configuration. It should be useful directly on top of
oe-core and compliments meta-openembedded. It should be primarily useful
to the following groups:
- Anyone building a small networking device (eg. a home router /
bridge / switch).
- Anyone wanting to add network services to their device (eg.
anything that might benefit from a small ftp/tftp server)
Dependencies
------------
This layer depends on:
URI: git://git.openembedded.org/openembedded-core
branch: master
For some recipes, the meta-oe layer is required:
URI: git://git.openembedded.org/meta-openembedded
subdirectory: meta-oe
branch: master
URI: git://git.openembedded.org/meta-openembedded
subdirectory: meta-python
branch: master
Maintenance
-----------
Layer maintainers: Khem Raj <raj.khem@gmail.com>
Armin Kuster <akuster808@gmail.com> (recipes-netkit)
Please see the MAINTAINERS file for information on contacting the
maintainers of this layer, as well as instructions for submitting patches.