<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>13057</bug_id>
          
          <creation_ts>2018-12-03 20:00:33 +0000</creation_ts>
          <short_desc>No default network configuration for systemd-networkd</short_desc>
          <delta_ts>2019-06-14 09:21:04 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>OE-Core</product>
          <component>core</component>
          <version>5.99</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium+</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>2.8 M1</target_milestone>
          
          <blocked>13031</blocked>
          <everconfirmed>1</everconfirmed>
          <reporter name="Paul Eggleton">bluelightning</reporter>
          <assigned_to name="Ross Burton">ross.burton</assigned_to>
          <cc>alessioigorbogani</cc>
    
    <cc>jku</cc>
    
    <cc>kai.kang</cc>
    
    <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
    
    <cc>randy.macleod</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Yes (doc changes required)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>82383</commentid>
    <comment_count>0</comment_count>
    <who name="Paul Eggleton">bluelightning</who>
    <bug_when>2018-12-03 20:00:33 +0000</bug_when>
    <thetext>If you enable systemd (and disable sysvinit) and build an image, e.g. core-image-minimal, the image will currently boot up without enabling any network interfaces. This is because by default we do not seem to deploy a network configuration file under /etc/systemd/network - once I added one there with the appropriate content the network interface got brought up as expected.

Of course the most basic fix would be to write a network config file that just enables DHCP on en*, and let users extend it via a bbappend for anything more complicated. There&apos;s a reasonably good guide to this config here:

  https://wiki.archlinux.org/index.php/systemd-networkd

However, we should probably take this opportunity to take a closer look at how all of this fits together. We&apos;d want to consider what happens when connman (or init-ifupdown) is installed, if anything. Also, would putting a config file under /etc go against any long-term stateless goals (assuming that is a goal)?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>83418</commentid>
    <comment_count>1</comment_count>
    <who name="Jussi Kukkonen">jku</who>
    <bug_when>2019-04-03 07:58:34 +0000</bug_when>
    <thetext>There&apos;s a system config location (/usr/lib/systemd/network/ maybe?) so installing things to /etc is not necessary.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>83861</commentid>
    <comment_count>2</comment_count>
    <who name="Kai Kang">kai.kang</who>
    <bug_when>2019-05-20 07:14:02 +0000</bug_when>
    <thetext>For init-ifupdown, it provides init script /etc/init.d/networking which calls ifup -a to enable network interfaces. And in configure file /etc/network/interfaces, it has set:

auto eth0                                                                                                                                         
iface eth0 inet dhcp                                                                                                                              
iface eth1 inet dhcp 

Then udhcpc is launched to configure the network interfaces.


For connman, it provides built-in dhcp supports. In README of connman source codes,

The following features are built-in into Connection Manager:
    - IPv4, IPv4-LL (link-local) and DHCP
    - IPv6, DHCPv6 and 6to4 tunnels</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>84208</commentid>
    <comment_count>3</comment_count>
    <who name="Kai Kang">kai.kang</who>
    <bug_when>2019-06-14 09:21:04 +0000</bug_when>
    <thetext>Fixed by
https://git.openembedded.org/openembedded-core/commit/?id=d87efd14ce0471135c0aa7fd7b5da2808acb9c76</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>