I don’t understand why some configured tagged vlans on my 18.04 LTS desktop don’r reply on ping. I’ve completely disabled NetworkManager, systemd-networkd is running and enabled.
Here is my config;
raymond@htpc:~$ cat /etc/netplan/config.yaml network: version: 2 renderer: networkd ethernets: enp1s0f0: dhcp4: true optional: true enp1s0f1: match: macaddress: "00:26:55:da:9f:9b" set-name: enp1s0f1 dhcp4: false vlans: vlan-lan: id: 130 link: enp1s0f1 dhcp4: true dhcp4-overrides: route-metric: 100 vlan-iot: id: 132 link: enp1s0f1 dhcp4: true dhcp4-overrides: route-metric: 200 vlan-dmz: id: 133 link: enp1s0f1 dhcp4: false raymond@htpc:~$ networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 enp1s0f0 ether no-carrier configuring 3 enp1s0f1 ether degraded configured 4 vlan-lan ether routable configured 5 vlan-iot ether routable configured 6 vlan-dmz ether degraded raymond@htpc:~$ networkctl status ● State: routable Address: 192.168.130.133 on vlan-lan 192.168.132.133 on vlan-iot 169.254.9.221 on enp1s0f0 169.254.9.226 on enp1s0f1 fe80::226:55ff:feda:9f9b on enp1s0f1 fe80::226:55ff:feda:9f9b on vlan-lan fe80::226:55ff:feda:9f9b on vlan-iot fe80::226:55ff:feda:9f9b on vlan-dmz Gateway: 192.168.130.129 on vlan-lan 192.168.132.129 on vlan-iot DNS: 192.168.130.129 192.168.132.129
- Vlan-lan does reply.
- Vlan-dmz was configured for dhcp4. got an IP but never replied in request. I don’t need VM Host to have IP in dmz-subnet. Strange thing is I’ve got a Debian VM Guest assigned on vlan-dmz and it does ICMP-reply from hosts in other subnets.
- Vlan-iot never replies on pinging the interface. Only from within subnet I receive a reply. It’s a bridged interface with wifi on firewall. I’ve also installed Ubuntu on other system with tagged vlans through Netplan and same issue.
Mac configured with tagged vlans, just for testing purposes, does respond like it supposed to do. What am I missing?