summaryrefslogtreecommitdiff
path: root/network
Commit message (Collapse)AuthorAgeFilesLines
* network: allow LLDP packets to cross non-customer bridges for container ↵Lennart Poettering2016-05-093-3/+3
| | | | | | | | | | | network interfaces This changes the default .network files we ship for nspawn containers to set EmitLLDP=customer-bridge in order to allow propagation of the LLDP packets across bridges. This is useful so that "networkctl status" shows all peers connected to a virtual container network, collecting this data via LLDP. This is safe since the default configuration for these interfaces does not bridge these links to external interfaces, but relies on IP routing for this.
* network: add automatic configuration for the networks created by nspawn ↵Lennart Poettering2016-05-093-0/+30
| | | | | | | --network-zone= This way, they "just work", similar to --network-veth behaves, as long as networkd is enabled and running on all involved nodes.
* network: turn on LLDP tx+rx for the default container network configurationLennart Poettering2016-02-212-0/+4
| | | | | Containers are relatively trusted and the veth tunnels are small networks, hence let's turn on LLDP both ways for them.
* networkd: emit DNS/NTP/Timezone info via DHCP server by defaultLennart Poettering2015-08-271-3/+0
| | | | If we have the data, emit it by default.
* network: turn on DHCP timezone passing between container and hostLennart Poettering2015-08-262-0/+6
| | | | | Let's turn on DHCP timezone passing from the host to a container, so that the timezone is always in sync.
* network: fix 'LinkLocal' -> 'LinkLocalAddressing' in network filesDavid Herrmann2015-02-142-2/+2
| | | | | | | | | | | | 'LinkLocal' was renamed to 'LinkLocalAddressing' in: commit 56fd6bf795926409b087bce406ea851ad89f9fe8 Author: Tom Gundersen <teg@jklm.no> 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.
* networkd: generalize IPv4LL to LinkLocalTom Gundersen2015-02-092-2/+2
| | | | | | 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.
* network: IPMasquerade= implies IPForward=, hence remove itLennart Poettering2015-01-131-1/+0
|
* networkd: introduce an AddressFamilyBoolean enum typeLennart Poettering2015-01-131-1/+1
| | | | | | 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.
* doc: network - add comment about default prefix sizeTom Gundersen2015-01-131-0/+1
| | | | | | Should hopefully make it clear that this is not some magic value, just the default we picked. Suggested by Jan Engelhardt.
* networkd: add minimal IP forwarding and masquerading support to .network filesLennart Poettering2015-01-131-0/+2
| | | | | | | | | | | | | | This adds two new settings to networkd's .network files: IPForwarding=yes and IPMasquerade=yes. The former controls the "forwarding" sysctl setting of the interface, thus controlling whether IP forwarding shall be enabled on the specific interface. The latter controls whether a firewall rule shall be installed that exposes traffic coming from the interface as coming from the local host to all other interfaces. This also enables both options by default for container network interfaces, thus making "systemd-nspawn --network-veth" have network connectivity out of the box.
* udev: link_setup - respect kernel name assign policyTom Gundersen2014-08-081-1/+1
| | | | | | | | | Newer kernels export meta-information about the origin of an ifname. Respect this from the ifname rename logic. We do not rename any interfaces that was originally named by userspace, nor once which have already been renamed from userspace. Moreover, we optionally do not (the default) rename interfaces which the kernel claims to have named in a predictable way.
* networkd: merge DHCPv4 and DHCPv6 configTom Gundersen2014-06-291-2/+1
| | | | | | | 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.
* build-sys: add missing Makefile symlinkLennart Poettering2014-06-191-0/+1
|
* net: enable dhcp6 for containersLennart Poettering2014-06-191-0/+1
|
* network: automatically assign each container veth link a /28 IP address rangeLennart Poettering2014-06-181-0/+2
|
* network: always take possession of host side of nspawn veth tunnels and do ↵Lennart Poettering2014-05-182-0/+20
| | | | IPv4LL on them
* network: default to IPv4LL on host0Tom Gundersen2014-04-031-0/+1
| | | | Now that we have a graceful handover from IPv4LL to DHCP, there is no longer any reason to leave this off by default.
* networkd/nspawn: enable dhcp client on veth device created in guestTom Gundersen2014-02-221-0/+6
| | | | | | | 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.
* udev: net-config - allow interface names to be set from the hwdbTom Gundersen2014-02-191-1/+1
|
* network: move configuration to /etc/systemd/networkTom Gundersen2013-10-291-0/+3
This is private configuraiton, so let's not pollute the namespace (and hence make Debian happy :) ).
View Lorry Controller Status