For a while routers seem to be reporting some of their addresses twice in their nodeinfo response. The issue stems from the nodeinfo response on the router, as can be seen by calling gluon-neighbour-info locally on an affected router.
An excerpt given by Jason from Freifunk Frankfurt:
root@avm4020:~# gluon-neighbour-info -d ::1 -p 1001 -r nodeinfo -c 1
{
"software": {
"autoupdater": {
"branch": "test",
"enabled": true
},
"batman-adv": {
"version": "2013.4.0",
"compat": 14
},
"fastd": {
"version": "v18",
"enabled": false
},
"firmware": {
"base": "gluon-2018.2",
"release": "v2.5.1-test-0102"
}
},
"network": {
"addresses": [
"2a06:8187:fbba:1234:ca0e:14ff:feb5:e1ad",
"2a06:8187:fbba:1234:ca0e:14ff:feb5:e1ad",
"fddd:5d16:b5dd::ca0e:14ff:feb5:e1ad",
"fe80::ca0e:14ff:feb5:e1ad"
],
"mesh": {
"bat0": {
"interfaces": {
"wireless": [
"be:2e:7d:2c:32:42"
],
"other": [
"be:2e:7d:2c:32:44",
"be:2e:7d:2c:32:43",
"be:2e:7d:2c:32:40"
]
}
}
},
"mac": "c8:0e:14:b5:e1:ad"
},
"location": {
"latitude": 50.12771951,
"longitude": 8.59648837
},
"owner": {
"contact": "...@gmx.net"
},
"system": {
"site_code": "ffffm"
},
"node_id": "c80e14b5e1ad",
"hostname": "avm4020",
"hardware": {
"model": "AVM FRITZ!Box 4020",
"nproc": 1
}
}root@avm4020:~# cat /proc/net/if_inet6
2a068187fbba1234ca0e14fffeb5e1ad 09 40 00 00 br-client
fddd5d16b5dd0000ca0e14fffeb5e1ad 09 40 00 00 br-client
fe80000000000000bc2e7dfffe2c3243 0a 40 20 80 primary0
fe80000000000000bc2e7dfffe2c3240 11 40 20 80 client0
fe80000000000000bc2e7dfffe2c3240 06 40 20 80 br-wan
fe80000000000000ca0e14fffeb5e1ad 0b 40 20 80 bat0
fe80000000000000ca0e14fffeb5e1ad 09 40 20 80 br-client
fe80000000000000144195fffe40f7dc 08 40 20 80 local-node
fe80000000000000bc2e7dfffe2c3242 10 40 20 80 ibss0
00000000000000000000000000000001 01 80 10 80 lo
fddd5d16b5dd00000000000000000001 08 80 00 a0 local-node
fe80000000000000bc2e7dfffe2c3244 04 40 20 80 eth1
The issue could have possibly been introduced in 7408f04 and is not always present. I've only seen it in roughly ~15% of our routers with a recent master build.
For a while routers seem to be reporting some of their addresses twice in their nodeinfo response. The issue stems from the nodeinfo response on the router, as can be seen by calling
gluon-neighbour-infolocally on an affected router.An excerpt given by Jason from Freifunk Frankfurt:
The issue could have possibly been introduced in 7408f04 and is not always present. I've only seen it in roughly ~15% of our routers with a recent master build.