OPNsense Forum
Archive => 18.1 Legacy Series => Topic started by: GOCE on July 18, 2018, 05:13:27 pm
-
Hi,
I keep getting a lot of the following entries in the firewall logs:
Jul 18 17:06:51 kernel: sa6_recoverscope: embedded scope mismatch: fe80:5::6231:97ff:fe84:158f%6. sin6_scope_id was overridden
Jul 18 17:06:51 kernel: sa6_recoverscope: embedded scope mismatch: fe80:5::6231:97ff:fe84:158f%6. sin6_scope_id was overridden
Jul 18 17:06:51 kernel: sa6_recoverscope: embedded scope mismatch: fe80:5::6231:97ff:fe84:158f%6. sin6_scope_id was overridden
Has anybody an idea what is going wrong here?
Regards, GOCE
-
Hi GOCE,
The scope is appended using % and should normally match an ifconfig device like %em1. It's "6" here so something is definitely wrong. Do you know where this could come from (service log, ifconfig output).
Cheers,
Franco
-
Hi,
maybe a bit more context is usefull. So here we go:
From /var/log/system.log
Jul 19 16:24:00 fw02-tie-de kernel: sa6_recoverscope: embedded scope mismatch: fe80:6::6231:97ff:fe84:44ac%5. sin6_scope_id was overridden
Jul 19 16:24:00 fw02-tie-de kernel: sa6_recoverscope: embedded scope mismatch: fe80:6::6231:97ff:fe84:44ac%5. sin6_scope_id was overridden
Jul 19 16:24:00 fw02-tie-de kernel: sa6_recoverscope: embedded scope mismatch: fe80:5::6231:97ff:fe84:158f%6. sin6_scope_id was overridden
Jul 19 16:24:00 fw02-tie-de kernel: sa6_recoverscope: embedded scope mismatch: fe80:5::6231:97ff:fe84:158f%6. sin6_scope_id was overridden
Jul 19 16:24:45 fw02-tie-de kernel: sa6_recoverscope: embedded scope mismatch: fe80:5::6231:97ff:fe84:158f%6. sin6_scope_id was overridden
Jul 19 16:24:45 fw02-tie-de kernel: sa6_recoverscope: embedded scope mismatch: fe80:5::6231:97ff:fe84:158f%6. sin6_scope_id was overridden
Jul 19 16:24:45 fw02-tie-de kernel: sa6_recoverscope: embedded scope mismatch: fe80:5::6231:97ff:fe84:158f%6. sin6_scope_id was overridden
Jul 19 16:24:45 fw02-tie-de kernel: sa6_recoverscope: embedded scope mismatch: fe80:5::6231:97ff:fe84:158f%6. sin6_scope_id was overridden
Jul 19 16:25:28 fw02-tie-de kernel: sa6_recoverscope: embedded scope mismatch: fe80:5::6231:97ff:fe84:158f%6. sin6_scope_id was overridden
Jul 19 16:25:28 fw02-tie-de kernel: sa6_recoverscope: embedded scope mismatch: fe80:5::6231:97ff:fe84:158f%6. sin6_scope_id was overridden
Jul 19 16:25:28 fw02-tie-de kernel: sa6_recoverscope: embedded scope mismatch: fe80:5::6231:97ff:fe84:158f%6. sin6_scope_id was overridden
Jul 19 16:25:28 fw02-tie-de kernel: sa6_recoverscope: embedded scope mismatch: fe80:5::6231:97ff:fe84:158f%6. sin6_scope_id was overridden
^C
root@fw2:~ # ping6 fe80:6::6231:97ff:fe84:44ac
PING6(56=40+8+8 bytes) fe80::225:90ff:fef4:7517%igb5 --> fe80:6::6231:97ff:fe84:44ac
16 bytes from fe80::6231:97ff:fe84:44ac%igb5, icmp_seq=0 hlim=64 time=1.582 ms
16 bytes from fe80::6231:97ff:fe84:44ac%igb5, icmp_seq=1 hlim=64 time=1.392 ms
16 bytes from fe80::6231:97ff:fe84:44ac%igb5, icmp_seq=2 hlim=64 time=3.048 ms
^C
--- fe80:6::6231:97ff:fe84:44ac ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 1.392/2.007/3.048/0.740 ms
root@fw2:~ # ping6 fe80:5::6231:97ff:fe84:158f
PING6(56=40+8+8 bytes) fe80::225:90ff:fef4:7516%igb4 --> fe80:5::6231:97ff:fe84:158f
16 bytes from fe80::6231:97ff:fe84:158f%igb4, icmp_seq=0 hlim=64 time=1.535 ms
16 bytes from fe80::6231:97ff:fe84:158f%igb4, icmp_seq=1 hlim=64 time=1.781 ms
16 bytes from fe80::6231:97ff:fe84:158f%igb4, icmp_seq=2 hlim=64 time=1.292 ms
^C
--- fe80:5::6231:97ff:fe84:158f ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 1.292/1.536/1.781/0.200 ms
The firewall fw2 connects on igb4 to router1 and on igb5 to router2. The output is from the second
firewall so CARP will show BACKUP in the ifconfig output.
igb4: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=5400b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,NETMAP,TXCSUM_IPV6>
ether 00:25:90:f4:75:16
hwaddr 00:25:90:f4:75:16
inet6 fe80::225:90ff:fef4:7516%igb4 prefixlen 64 scopeid 0x5
inet6 2a01:598:8880:113b:225:90ff:fef4:7516 prefixlen 64 autoconf
inet 172.16.1.242 netmask 0xffffff00 broadcast 172.16.1.255
inet 172.16.1.250 netmask 0xffffff00 broadcast 172.16.1.255 vhid 2
nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
carp: BACKUP vhid 2 advbase 1 advskew 100
igb5: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=5400b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,NETMAP,TXCSUM_IPV6>
ether 00:25:90:f4:75:17
hwaddr 00:25:90:f4:75:17
inet6 fe80::225:90ff:fef4:7517%igb5 prefixlen 64 scopeid 0x6
inet6 2a01:598:b906:14ec:225:90ff:fef4:7517 prefixlen 64 autoconf
inet 172.16.2.242 netmask 0xffffff00 broadcast 172.16.2.255
inet 172.16.2.250 netmask 0xffffff00 broadcast 172.16.2.255 vhid 9
nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
carp: BACKUP vhid 9 advbase 1 advskew 100
Regards, GOCE
-
Judging by the network stack code, (a) this is done to recover the scope when the network interfaces could change (devices being created or removed) so is helpfully healthy. And (b) it's only a NOTICE so it's less than WARNING so everything is ok except for it filling the system.log due to (a).
Cheers,
Franco