[OOR-Users] Fwd: OOR configuration issues

[Holger Zuleger]

Hi,

On 07.08.2018 01:57, Rene 'Renne' Bartsch, B.Sc. Informatics wrote:
> the link local address in the map message is weird. Could it be a
> problem with the Fritz!Box announcing it as default route?

no that the nexthop for the default route is the link-local address of
the advertising router is perfectly legal.

I guess that the link-local address in the debug message is the source
address from your box where oor is running.
Maybe this is because your oor runs in a container (Don't know what LXC
container means).

Could you please double check that oor is able to get the global ipv6
address from the rloc interface (eth0 in your config)?
It must be the DTAG address starting with 2003: .

Have your tried to remove the redundant map-server and proxy-etr-ipv6
config? If not: Please start with just one map-server and one PETR address.

> ----------------------------------------------------------------------------------------------------
> 
> root at router:~# ip -6 route show
> 2003:ce:7f31:5200::/64 dev eth0 proto ra metric 1024 pref medium
> 2003:ce:7f31:5200::/56 via fe80::3681:c4ff:fe2a:17ed dev eth0 proto ra
> metric 1024 pref medium
> 2610:d0:2183::/48 dev eth0 proto kernel metric 256 pref medium
> fd00:0:0:1::/64 dev eth0 proto ra metric 1024 pref medium
> fd00:0:0:1::/64 via fe80::3681:c4ff:fe2a:17ed dev eth0 proto ra metric
> 1024 pref medium
> fd31:8e4b:773c::/64 dev eth0 proto ra metric 1024 pref medium
> fd31:8e4b:773c::/48 via fe80::da58:d7ff:fe00:7a25 dev eth0 proto ra
> metric 1024 pref medium
> fe80::/64 dev eth0 proto kernel metric 256 pref medium
> default via fe80::3681:c4ff:fe2a:17ed dev eth0 proto ra metric 1024 mtu
> 1492 pref medium
> ---------------------------------------------------------------------------------------------
The routing table has more entries than expected.
You do no longer need the ULA addresses (the one starting with fdxx:)
because with LISP you will get a global stable prefix.

The 2610:d0... is your LISP prefix. I can't remember if this one have to
be in the routing table and what's the correct nexthop interface.

> Traceroute looks fine:
> -----------------------------------------------------------------------------------------------------------------
> 
> root at router:~# traceroute6 2001:6c8:130:600::1
> traceroute to 2001:6c8:130:600::1 (2001:6c8:130:600::1), 30 hops max, 80
> byte packets
>  1  2003:ce:7f31:5200:3681:c4ff:fe2a:17ed
> (2003:ce:7f31:5200:3681:c4ff:fe2a:17ed)  0.864 ms  1.059 ms  2.442 ms
>  2  2003:ce:7fff:315d::1 (2003:ce:7fff:315d::1)  10.820 ms  10.790 ms 
> 11.559 ms
>  3  2003:0:130b:4000::1 (2003:0:130b:4000::1)  10.905 ms  11.228 ms 
> 11.455 ms
>  4  2003:0:130b:4002::2 (2003:0:130b:4002::2)  11.714 ms  12.046 ms 
> 13.317 ms
>  5  ar4tdm2nxf1.dk.ip.tdc.net (2001:6c8:40::10b)  30.317 ms  30.585 ms 
> 30.793 ms
>  6  2001:6c8:41:100:0:2:1:c (2001:6c8:41:100:0:2:1:c)  32.100 ms  31.156
> ms  31.134 ms
> -----------------------------------------------------------------------------------------------------------------
Hmm, indeed.

However the DEBUG message with the link-local source address looks strange.

 Holger

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4160 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.openoverlayrouter.org/pipermail/users/attachments/20180808/872cb262/attachment.bin>