Mehrere router_ip werden nicht ans Peeringinterface angehangen #197

New Issue

ChristianD · 2021-12-31T12:40:54+01:00

ChristianD commented

2021-12-31 12:40:54 +01:00

Wenn man mehrere router_ip konfiguert werden zwar beide korrekt ans loopback gehangen aber nicht an VLAN Peeringinterfaces (wireguard ungetestet):

/etc/config/gateway

[...]
config gateway 'meta'
	list router_ip '10.50.255.255/32'
	list router_ip '10.83.255.255/32'
	option config_version '2'
[...]
config vlan '7'
	option comment 'device'
	option ports '2'
[...]
config babelpeer 'device'
	option vlan '7'
	option type 'wired'
[...]

führt zu folgender /etc/config/network

[...]
config interface 'babelpeer_device'
        option proto 'static'      
        option ifname 'eth0.7'            
        list ipaddr '10.50.255.255/32 10.83.255.255/32'
[...]
config interface 'loopback'
        option ifname 'lo'
        option proto 'static'
        list ipaddr '10.50.255.255/32'
        list ipaddr '10.83.255.255/32'
[...]

Sieht dann so aus:

root@OpenWrt:~# ip addr sh
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
    inet 10.50.255.255/32 brd 255.255.255.255 scope global lo
       valid_lft forever preferred_lft forever
    inet 10.83.255.255/32 brd 255.255.255.255 scope global lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
[...]
eth0.7@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e8:de:27:65:b3:38 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::eade:27ff:fe65:b338/64 scope link 
       valid_lft forever preferred_lft forever
[...]

Der Syntax für eth0.7 in der network ist mMn falsch, für loopback stimmt er. Mit einer Adresse klappt alles einwandfrei.

Wenn man mehrere router_ip konfiguert werden zwar beide korrekt ans loopback gehangen aber nicht an VLAN Peeringinterfaces (wireguard ungetestet): /etc/config/gateway ``` [...] config gateway 'meta' list router_ip '10.50.255.255/32' list router_ip '10.83.255.255/32' option config_version '2' [...] config vlan '7' option comment 'device' option ports '2' [...] config babelpeer 'device' option vlan '7' option type 'wired' [...] ``` führt zu folgender /etc/config/network ``` [...] config interface 'babelpeer_device' option proto 'static' option ifname 'eth0.7' list ipaddr '10.50.255.255/32 10.83.255.255/32' [...] config interface 'loopback' option ifname 'lo' option proto 'static' list ipaddr '10.50.255.255/32' list ipaddr '10.83.255.255/32' [...] ``` Sieht dann so aus: ``` root@OpenWrt:~# ip addr sh 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 inet 10.50.255.255/32 brd 255.255.255.255 scope global lo valid_lft forever preferred_lft forever inet 10.83.255.255/32 brd 255.255.255.255 scope global lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever [...] eth0.7@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether e8:de:27:65:b3:38 brd ff:ff:ff:ff:ff:ff inet6 fe80::eade:27ff:fe65:b338/64 scope link valid_lft forever preferred_lft forever [...] ``` Der Syntax für eth0.7 in der network ist mMn falsch, für loopback stimmt er. Mit einer Adresse klappt alles einwandfrei.

fbl added the

bug

layer3

labels 2021-12-31 13:10:59 +01:00

fbl added this to the next-bugfix milestone 2021-12-31 13:11:02 +01:00

fbl self-assigned this 2021-12-31 13:11:06 +01:00

fbl referenced a pull request that will close this issue

2022-01-04 12:09:51 +01:00

fff-babeld: Only select first list entry from router_ip #200

fbl referenced this issue from a commit

2022-01-06 01:08:07 +01:00

fff-babeld: Only select first list entry from router_ip