[rlug] Intrebare CoreOS bond/vlan/networkd

Gyula Keresztely-Krall xenexis at gmail.com
Thu Feb 22 15:10:16 EET 2018


Salutare,

Incerc sa configurez un coreos sa pot utiliza interfata bond cu vlan
tag, si se pare ca dau pe langa (posibil sa fi ruginit in networking):
Pe un server Dell (R640) am patru interfete, legate in doua bonduri cu
subnet diferit (unu pt managment/admin) altul pentru traffic normal.
Primul permite pachetele untagged, al doilea nu.

Configuratia actuala:

core at my-kube-worker-01 /etc/systemd/network $ ls -l
total 56
-rw-r--r--. 1 root root  44 Feb 22 11:47 00-vlan2.netdev
-rw-r--r--. 1 root root  91 Feb 20 16:52 10-int.network
-rw-r--r--. 1 root root  91 Feb 22 10:38 15-int.network
-rw-r--r--. 1 root root  69 Feb 22 11:48 20-bond0.netdev
-rw-r--r--. 1 root root 119 Feb 21 13:24 20-bond1.netdev
-rw-r--r--. 1 root root  97 Feb 22 12:32 30-bond0.network
-rw-r--r--. 1 root root  85 Feb 22 12:24 30-bond1.network
core at my-kube-worker-01 /etc/systemd/network $ cat 00-vlan2.netdev
[NetDev]
Name=vlan2
Kind=vlan

[VLAN]
Id=2

core at my-kube-worker-01 /etc/systemd/network $ cat 10-int.network
[Match]
Name=eno3*
Name=eno4*

[Network]
Bond=bond0
LinkLocalAddressing=no
IPv6AcceptRA=no
core at my-kube-worker-01 /etc/systemd/network $ cat 15-int.network
[Match]
Name=eno1*
Name=eno2*

[Network]
Bond=bond1
LinkLocalAddressing=no
IPv6AcceptRA=no
core at my-kube-worker-01 /etc/systemd/network $ cat 20-bond0.netdev
[NetDev]
Name=bond0
Kind=bond
[Bond]
Mode=balance-rr
MIIMonitorSec=1
core at my-kube-worker-01 /etc/systemd/network $ cat 20-bond1.netdev
[NetDev]
Name=bond1
Kind=bond
[Bond]
Mode=802.3ad
LACPTransmitRate=fast
MIIMonitorSec=1s
UpDelaySec=3s
DownDelaySec=9s
core at my-kube-worker-01 /etc/systemd/network $ cat 30-bond0.network
[Match]
Name=bond0
[Network]
DNS=192.168.12.175
Address=192.168.15.243/24
Gateway=192.168.15.254
core at my-kube-worker-01 /etc/systemd/network $ cat 30-bond1.network
[Match]
Name=bond1
[Network]
DNS=192.168.12.175
Address=192.168.12.243/24
VLAN=vlan2


Din care rezulta :

core at amy-kube-worker-01 /etc/systemd/network $ ip add
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: eno1np0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq
master bond1 state UP group default qlen 1000
    link/ether  brd ff:ff:ff:ff:ff:ff
3: eno2np1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq
master bond1 state UP group default qlen 1000
    link/ether  brd ff:ff:ff:ff:ff:ff
4: eno3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq
master bond0 state UP group default qlen 1000
    link/ether  brd ff:ff:ff:ff:ff:ff
5: eno4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq
master bond0 state UP group default qlen 1000
    link/ether  brd ff:ff:ff:ff:ff:ff
6: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc
noqueue state UP group default qlen 1000
    link/ether  brd ff:ff:ff:ff:ff:ff
    inet 192.168.12.243/24 brd 192.168.12.255 scope global bond1
       valid_lft forever preferred_lft forever
    inet6 fe80::2c27:68ff:fe97:15f6/64 scope link
       valid_lft forever preferred_lft forever
7: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc
noqueue state UP group default qlen 1000
    link/ether  brd ff:ff:ff:ff:ff:ff
    inet 192.168.15.243/24 brd 192.168.15.255 scope global bond0
       valid_lft forever preferred_lft forever
    inet6 fe80::14d6:deff:fec9:f2cc/64 scope link
       valid_lft forever preferred_lft forever
8: vlan2 at bond1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue state UP group default qlen 1000
    link/ether brd ff:ff:ff:ff:ff:ff
    inet 192.168.12.205/24 brd 192.168.12.255 scope global dynamic vlan2
       valid_lft 122sec preferred_lft 122sec
    inet6 fe80::2c27:68ff:fe97:15f6/64 scope link
       valid_lft forever preferred_lft forever
9: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN group default
    link/ether 02:42:fd:a3:ad:db brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 scope global docker0
       valid_lft forever preferred_lft forever


core at my-kube-worker-01 /etc/systemd/network $ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.15.254  0.0.0.0         UG    0      0        0 bond0
0.0.0.0         192.168.12.254  0.0.0.0         UG    1024   0        0 vlan2
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
192.168.12.0    0.0.0.0         255.255.255.0   U     0      0        0 bond1
192.168.12.0    0.0.0.0         255.255.255.0   U     0      0        0 vlan2
192.168.12.254  0.0.0.0         255.255.255.255 UH    1024   0        0 vlan2
192.168.15.0    0.0.0.0         255.255.255.0   U     0      0        0 bond0


Ce as dori este sa pot accesa (de pe server) subnetul 192.168.12.x si
acest subnet sa fie si cel default si sa pot accesa adresa bond1 din
exterior.
Ce nu inteleg: nu am setat pentru vlan.netdev sa ceara ip de la dhcp
si totusi o face, desi ar trebui sa utilizeze cea ce e setat pentru
bond1, posibil sa gresesc sa am bungit-o rau cu documentatia de la
CoreOS (care oricum nu e prea generoasa cu exemple).

Daca cineva are vreo idee/link/etc ii multumesc.
Desigur pot oferi alte detalii daca nu cele copiate nu sunt relevante.

Multumesc.

Numai bine,




-- 
Gyula KERESZTELY-KRALL

--
I hate myself, because I'm not open-source.
Worrying about killer AI and the superintelligent robots is like
worrying about overcrowding on Mars. - Garry Kasparov




More information about the RLUG mailing list