netplan and bond definition

How to change below in to a netplan yaml file for Ubuntu18.04 ?

root@ubuntu-sio1-cpa117-2:/etc/network# cat interfaces

This file describes the network interfaces available on your system

and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

The loopback network interface

auto lo iface lo inet loopback

auto eno1 iface eno1 inet manual bond-master bond0 bond-primary eno1

auto eno2 iface eno2 inet manual bond-master bond0

auto bond0 iface bond0 inet manual bond-mode active-backup bond-miimon 100 bond-slaves none

auto bond0.40 iface bond0.40 inet static address 192.168.34.20 netmask 255.255.255.0 network 192.168.34.0 broadcast 192.168.34.255 vlan-raw-device bond0

auto bond1 iface bond1 inet manual bond-mode 4 bond-miimin 100 bond-lacp-rate 1 bond-slaves none

auto enp175s0f0 iface enp175s0f0 inet manual bond-master bond1

auto enp94s0f0 iface enp94s0f0 inet manual bond-master bond1

auto bond1.1001 iface bond1.1001 inet static address 10.93.129.100 gateway 10.93.129.97 netmask 255.255.255.248 dns-nameservers 10.221.16.10 10.221.16.11 vlan-raw-device bond1 up route add -net 10.93.129.96 netmask 255.255.255.248 gw 10.93.129.97

Netplan Bridge Stuck in Degraded Mode

I’m trying to add a Bridge on 18.04 Server VM on Hyper-V with LXD Installed and the bridge never comes up and never gets an IP Address. Hopefully someone sees what I’m doing wrong.

network:   version: 2   renderer: networkd   ethernets:     eth0:       dhcp4: no       dhcp6: no   bridges:     br0:       interfaces:         - eth0       dhcp4: yes       dhcp6: no 

networkd status

IDX LINK             TYPE               OPERATIONAL SETUP   1 lo               loopback           carrier     unmanaged   2 eth0             ether              carrier     configured   3 br0              ether              degraded    configuring   4 lxdbr0           ether              routable    unmanaged   6 vethC0L5GN       ether              degraded    unmanaged 

networkd log

● systemd-networkd.service - Network Service    Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)    Active: active (running) since Sun 2019-10-13 15:40:13 UTC; 7min ago      Docs: man:systemd-networkd.service(8)  Main PID: 12869 (systemd-network)    Status: "Processing requests..."     Tasks: 1 (limit: 4915)    CGroup: /system.slice/systemd-networkd.service            └─12869 /lib/systemd/systemd-networkd  Oct 13 15:40:13 lxd1 systemd-networkd[12869]: eth0: Link is not managed by us Oct 13 15:40:13 lxd1 systemd-networkd[12869]: lo: Link is not managed by us Oct 13 15:40:13 lxd1 systemd-networkd[12869]: vethC0L5GN: Link is not managed by us Oct 13 15:40:13 lxd1 systemd-networkd[12869]: lxdbr0: Link is not managed by us Oct 13 15:40:13 lxd1 systemd-networkd[12869]: eth0: Lost carrier Oct 13 15:40:13 lxd1 systemd-networkd[12869]: br0: Lost carrier Oct 13 15:40:13 lxd1 systemd-networkd[12869]: eth0: IPv6 successfully disabled Oct 13 15:40:13 lxd1 systemd-networkd[12869]: eth0: Gained carrier Oct 13 15:40:13 lxd1 systemd-networkd[12869]: eth0: Configured Oct 13 15:40:13 lxd1 systemd-networkd[12869]: br0: Gained carrier 

If I change back to this and reboot everything comes up fine.

network:   version: 2   renderer: networkd   ethernets:     eth0:       dhcp4: yes       dhcp6: no 

Server 18.04 netplan, multiple NICs / gateways, and routing (DHCP)

My apologies if this is dumb or redundant, but I have not found an accurate or complete answer to this question.

I have a fully current 18.04 server with multiple NICs across different networks. I have DHCP reservations set up for each adapter on its respective network, so I don’t need or particularly want to configure static IPs / gateways for each adapter, but I do need for each adapter to respond to traffic through the correct gateway because (for instance) I do have traffic coming to a specific adapter on that server across an openVPN connection (so coming from a different subnet that is not duplicated anywhere else in the system). As I have things configured now, each adapter responds correctly within it’s own subnet, so I know I have connectivity, but I need something more.

The problem is that all traffic from the server goes out through one gateway, so return traffic does not come back from the IP it is expected from (so is ignored). I’ve tried to use the information in the NetPlan man pages, but cannot find a clear answer for my configuration needs. My working 01-network-manager-all.yaml looks like this:

network:   version: 2   renderer: networkd   ethernets:     eno1:       dhcp4: yes       dhcp-identifier: mac       dhcp4-overrides:         route-metric: 100     eno2:       dhcp4: yes       dhcp-identifier: mac       dhcp4-overrides:         route-metric: 100     enp3s0f0:       dhcp4: yes       dhcp-identifier: mac       dhcp4-overrides:         route-metric: 100     enp3s0f1:       dhcp4: yes       dhcp-identifier: mac       dhcp4-overrides:         route-metric: 10 

This obviously pushes all non-adapter-local traffic out through the enp3s0f1 adapter, which isn’t what I want. If I change the route-metric on that adapter to 100, I don’t reliably get traffic out through any adapter. What I need are concrete examples of multiple adapters on DHCP with distinct subnets / routes, where traffic to each adapter goes out through its respective gateway. Can anyone help?

Configure GRE via Netplan (headless/aws)

How to translate the below to a Netplan yaml file with networkd as the renderer?

At the command line these commands work and build a GRE tunnel with an MTU of 1476.

ip tunnel add gre1 mode gre remote [x.x.x.x] local [y.y.y.y] ttl 255 ip link set gre1 up ip addr add [z.z.z.z]/30 dev gre1 

Where [x.x.x.x] is the remote GRE endpoint, [y.y.y.y] is the private IP of GRE endpoint and [z.z.z.z] is the address assigned to the local GRE interface.

Tried using the following yaml fragment the tunnel is defined but MTU is ‘ignored’ and the LAN i/f MTU-24 is set.

    tunnels:         gre1:             mode: gre             local: [y.y.y.y]             remote: [x.x.x.x]             mtu: 1476             addresses:                 - [z.z.z.z]/30 

The output from various commands:

# systemctl status systemd-networkd | grep gre1 Sep 16 11:49:40 ip-y-y-y-y systemd-networkd[1283]: gre1: Cannot enable IPv6 for interface gre1: No such file or directory Sep 16 11:49:40 ip-y-y-y-y systemd-networkd[1283]: gre1: Could not bring up interface: Address family not supported by protocol  # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00     inet 127.0.0.1/8 scope host lo        valid_lft forever preferred_lft forever     inet6 ::1/128 scope host        valid_lft forever preferred_lft forever 2: ens5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc mq state UP group default qlen 1000     link/ether 16:74:7e:e0:07:46 brd ff:ff:ff:ff:ff:ff     inet [y.y.y.y]/24 brd [y.y.y.255] scope global dynamic ens5        valid_lft 2631sec preferred_lft 2631sec     inet6 fe80::1474:7eff:fee0:746/64 scope link        valid_lft forever preferred_lft forever 3: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN group default qlen 1000     link/gre 0.0.0.0 brd 0.0.0.0 4: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN group default qlen 1000     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 5: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN group default qlen 1000     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 6: gre1@NONE: <POINTOPOINT,NOARP> mtu 8977 qdisc noop state DOWN group default qlen 1000     link/gre [y.y.y.y] peer [x.x.x.x]     inet [z.z.z.z]/30 brd [z.z.z.255] scope global gre1        valid_lft forever preferred_lft forever 

Bridging LAN and WIFI using netplan not working and killing AP

Hello everyone and thanks in advance!

I’m trying to extend my local LAN network via WIFI and would like all devices in the same network. The setup is as follows:

  • DHCP/DNS server running inside the LAN
  • separate PC linked to the LAN, with WIFI capability (sadly it’s not an option, to have the DHCP/DNS server running on this machine)

Since I’m running Ubuntu 18.04, I’m trying to use netplan to set everything up. Here’s my conf file:

network:   version: 2   renderer: NetworkManager   ethernets:     enp2s0:       dhcp4: no       addresses: [192.168.1.10/24]       gateway: 192.168.1.1       nameservers:         addresses: [192.168.1.2, 8.8.8.8, 8.8.4.4]   wifis:     wlp1s0:       access-points:         "MyWifi":           mode: ap           password: "DONTLOOK"   bridges:     br0:       dhcp4: yes       interfaces: [enp2s0, wlp1s0] 

Now, running the two network separately, i.e without the bridges section, everything works. With dnsmasq activated I can connect to the access point.

However I can’t seem to get the bridge working. Even worse is, as soon as the bridge gets activated access to the AP is no longer possible.

Does anybody have an idea, what I’m missing?

Apply last edits in netplan with no service

On my virtual computer I hace two NICs. Internet connection works fine, thanks to network-bridge. Now, I edited my /etc/netplan/01-netcf...yaml. Since I have no network services as network-manager or networking I always have to reboot whole computer, to apply the changes. (I cannot restart any service). Is there any way to avoid restarting whole PC ?

Setting up new ubuntu server through ESXI (netplan not working)

No doubt I am doing something wrong but I am not familiar with ubuntu, not even linux that well.

I have deployed ubuntu server via ESXI on an OVH Dedicated server.

I’ve done this a million times with windows machines but it is a alot easier on there…

img: this is what the settings would be on windows

How would I format this on netplan now?

How to use netplan to create two seperate routing tables?

I have an Ubuntu 18.04 host with two network interfaces on two subnets. I would like to set up symmetric routing so that traffic received from one interface is sent symmetrically out that same interface.

I know how to use Netplan for simple network configurations, but I’m stumped for more advanced configurations. Specifically:

  1. What is the Netplan syntax to add a default route like I do with ip route add default via 192.168.0.1 dev ens192 tab 1?
  2. How can I add a priority tag to a route?

My server has two IPs:

$   ip a|grep "inet " inet 127.0.0.1/8 scope host lo inet 192.168.0.10/22 brd 192.168.0.255 scope global ens192 inet 192.168.1.10/24 brd 192.168.1.255 scope global ens224 $   

I can use the following ip rules to get the tables that I want:

First, I create a route for each network and then add a default gateway.

$   ip route add 192.168.0.0/24 dev ens192 tab 1 $   ip route add 192.168.1.0/24 dev ens224 tab 2 $   ip route add default via 192.168.0.1 dev ens192 tab 1 $   ip route add default via 192.168.1.1 dev ens224 tab 2 

Then, I can create corresponding rules:

$   ip rule add from 192.168.0.10/32 tab 1 priority 100 $   ip rule add from 192.168.1.10/32 tab 2 priority 200 $   ip route flush cache 

This gets the routes that I want:

$   ip route show tab 1 default via 192.168.0.1 dev ens192 $   ip route show tab 2 default via 192.168.1.1 dev ens224 $   ip route default via 192.168.0.10 dev ens192 

As well as the rules that I want:

$   ip rule show 0:      from all lookup local 100:    from 192.168.0.10 lookup 1 200:    from 192.168.1.10 lookup 2 32766:  from all lookup main 32767:  from all lookup default 

Define hostapd configuration settings on netplan

I recently discovered that netplan can manage hostapd accesspoints, but this is the extent of the example config:

    wlp1s0:       access-points:         "guest":            mode: ap            # no WPA config implies default of open 

I can find no other documentations of how to define other settings like WPA security and passphrase. I need the following hostapd.conf settings defined and EAP in the future as well:

interface=wlo1 bridge=br0 hw_mode=g channel=0 ieee80211d=1 country_code=AE ieee80211n=1 wmm_enabled=1  ssid=SSID auth_algs=1 wpa=2 wpa_key_mgmt=WPA-PSK  rsn_pairwise=CCMP wpa_passphrase=********* 

I am aware netplan requires NetworkManager for access point configuration, and I don’t know if keeping the bridge managed by networkd will hinder the bridging. If possible, please clarify this point as well.