<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in 80-container-host0.network</title>
    <link>http://src.iws.cs.ovgu.de/source/rss/systemd/network/80-container-host0.network</link>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2005</copyright>
    <generator>Java</generator>
    <item>
        <title>network: turn on DHCP timezone passing between container and host
    
    Let's turn on DHCP timezone passing from the host to a container, so
    that the timezone is always in sync.</title>
        <description>/systemd/network/80-container-host0.network - e26b50585b29acfe1ca9346850490b8fbe84aece</description>
        <pubDate></pubDate>
        <dc:creator>Lennart Poettering &lt;lennart@poettering.net&gt;</dc:creator>
    </item>

    <item>
        <title>network: fix 'LinkLocal' -&gt; 'LinkLocalAddressing' in network files
    
    'LinkLocal' was renamed to 'LinkLocalAddressing' in:
    
        commit 56fd6bf795926409b087bce406ea851ad89f9fe8
        Author: Tom Gundersen &lt;teg@jklm.no&gt;
        Date:   Sat Feb 14 00:32:26 2015 +0100
    
            networkd: .network - rename LinkLocal to LinkLocalAddressing
    
    ..but apparently the network files were not updated. Fix this.</title>
        <description>/systemd/network/80-container-host0.network - 0737984f6910fdffdf6494f20c1c64a027806273</description>
        <pubDate></pubDate>
        <dc:creator>David Herrmann &lt;dh.herrmann@gmail.com&gt;</dc:creator>
    </item>

    <item>
        <title>networkd: generalize IPv4LL to LinkLocal
    
    This allows both IPv4 and IPv6 link-local addresses to be enabled or disabled. By default
    we still enable IPv6LL and disable IPv4LL. The old config option is kept for backwards
    compatibility, but removed from the documentation.</title>
        <description>/systemd/network/80-container-host0.network - d0d6a4cd70477970812bff0a37e70f66208d7c14</description>
        <pubDate></pubDate>
        <dc:creator>Tom Gundersen &lt;teg@jklm.no&gt;</dc:creator>
    </item>

    <item>
        <title>networkd: introduce an AddressFamilyBoolean enum type
    
    This introduces am AddressFamilyBoolean type that works more or less
    like a booleaan, but can optionally turn on/off things for ipv4 and ipv6
    independently. THis also ports the DHCP field over to it.</title>
        <description>/systemd/network/80-container-host0.network - cb9fc36a1211967e8c58b0502a26c42552ac8060</description>
        <pubDate></pubDate>
        <dc:creator>Lennart Poettering &lt;lennart@poettering.net&gt;</dc:creator>
    </item>

    <item>
        <title>networkd: merge DHCPv4 and DHCPv6 config
    
    If there are v4 or v6 specific options we can keep those in separate sections,
    but for the common options, we will use only one.
    
    Moreovere only use DHCP=[yes/both|no/none|v4|v6] to enable or disable the clients.</title>
        <description>/systemd/network/80-container-host0.network - ed942a9eb22d50f667909ad6184b45015d28d054</description>
        <pubDate></pubDate>
        <dc:creator>Tom Gundersen &lt;teg@jklm.no&gt;</dc:creator>
    </item>

    <item>
        <title>net: enable dhcp6 for containers</title>
        <description>/systemd/network/80-container-host0.network - 5a0e3f28ad2c5c0a9db46d2acc2c906ec11e2461</description>
        <pubDate></pubDate>
        <dc:creator>Lennart Poettering &lt;lennart@poettering.net&gt;</dc:creator>
    </item>

    <item>
        <title>network: always take possession of host side of nspawn veth tunnels and do IPv4LL on them</title>
        <description>/systemd/network/80-container-host0.network - 4eaea66423ca58dfd7cfd1099ed902d7c81d8622</description>
        <pubDate></pubDate>
        <dc:creator>Lennart Poettering &lt;lennart@poettering.net&gt;</dc:creator>
    </item>

    <item>
        <title>network: default to IPv4LL on host0
    
    Now that we have a graceful handover from IPv4LL to DHCP, there is no longer any reason to leave this off by default.</title>
        <description>/systemd/network/80-container-host0.network - 60a0d61e7de8f1a87396fecc01e3cd0b2c6f8ae4</description>
        <pubDate></pubDate>
        <dc:creator>Tom Gundersen &lt;teg@jklm.no&gt;</dc:creator>
    </item>

    <item>
        <title>networkd/nspawn: enable dhcp client on veth device created in guest
    
    When starting systemd-nspawn with --network-veth, we create a veth device called
    host0 in the guest. Pick up on this and start a dhcp client on it. We will also
    pick up host0 netdevs created by other containers should they chose to use the
    same name.</title>
        <description>/systemd/network/80-container-host0.network - dd4d2c1cd1eb7c1f3163f6f922362af3189df0a3</description>
        <pubDate></pubDate>
        <dc:creator>Tom Gundersen &lt;teg@jklm.no&gt;</dc:creator>
    </item>

</channel>
</rss>

