VLAN configuration issue eth0 on BB Black

43 views
Skip to first unread message

E Gravel

unread,
Apr 9, 2021, 12:02:22 PM4/9/21
to BeagleBone
I'm attempting to configure VLAN's on eth0 using systemd.network as per instructions provided here:


I've attached my config files to this post. They're located in /etc/systemd/network on the BB Black.


E Gravel

unread,
Apr 9, 2021, 12:15:04 PM4/9/21
to BeagleBone
Apologies - pushed "send" before completing. I'll post the 3 config files on a follow-on message, I'm getting errors posting.

Attempting to ping the other device connected over the same VLAN fails. Doing tcpdump on eth0.33 doesn't show any ARP or ICMP packets when pinging. However, manually tearing down the VLAN link and setting it back up, results in pings functioning. I've looked in /proc/net/vlan before and after, everything is the same. Doing "ip a" and "ip r" also shows the same results, before and after tearing things down. Doing 'arp' before and after is obviously different, showing 'incomplete' before but showing the other side's MAC after.


$ uname -a
Linux beaglebone 4.19.94-ti-r42 #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC 2020 armv7l GNU/Linux

$ ip a
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether e4:15:f6:fa:29:e1 brd ff:ff:ff:ff:ff:ff
    inet 10.0.10.4/24 brd 10.0.10.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::e615:f6ff:fefa:29e1/64 scope link
       valid_lft forever preferred_lft forever
5: eth0.33'@'eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e4:15:f6:fa:29:e1 brd ff:ff:ff:ff:ff:ff
    inet 192.168.17.5/24 brd 192.168.17.255 scope global eth0.33
       valid_lft forever preferred_lft forever
    inet6 fe80::e615:f6ff:fefa:29e1/64 scope link
       valid_lft forever preferred_lft forever

$ arp
Address                  HWtype  HWaddress           Flags Mask            Iface
192.168.17.2                     (incomplete)                              eth0.33

$ sudo ip link del link eth0 name eth0.33 type vlan id 33

$ip a
<no eth0.33 in the list>

$ sudo ip link add link eth0 name eth0.33 type vlan id 33

$ ip a
9: eth0.33'@'eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e4:15:f6:fa:29:e1 brd ff:ff:ff:ff:ff:ff
    inet 192.168.17.5/24 brd 192.168.17.255 scope global eth0.33
       valid_lft forever preferred_lft forever
    inet6 fe80::e615:f6ff:fefa:29e1/64 scope link tentative
       valid_lft forever preferred_lft forever

$ ping 192.168.17.2
PING 192.168.17.2 (192.168.17.2) 56(84) bytes of data.
64 bytes from 192.168.17.2: icmp_seq=1 ttl=64 time=2.60 ms

$ arp
Address                  HWtype  HWaddress           Flags Mask            Iface
192.168.17.2             ether   00:04:f3:22:a8:74   C                     eth0.33

I'm at a loss, I can't figure out what has changed, as the links do appear to be setup correctly.

Any thoughts?

E Gravel

unread,
Apr 9, 2021, 12:16:01 PM4/9/21
to BeagleBone
Adding the config files
eth0 config files.7z

E Gravel

unread,
Apr 10, 2021, 5:56:36 PM4/10/21
to BeagleBone
The solution I found was installing NetworkManager instead of relying on systemd-network.
Reply all
Reply to author
Forward
0 new messages