NetworkManager creating IPv6 routes on the fly?



Following up my previous post, I am noticing something creating IPv6 routes on my local routing table:

2404:6800:4004:805::1007 via fe80::d267:e5ff:feb5:235b dev em1  proto static  metric 1
2404:6800:4006:806::1003 via fe80::d267:e5ff:feb5:235b dev em1  proto static  metric 1
2404:6800:4006:806::1005 via fe80::d267:e5ff:feb5:235b dev em1  proto static  metric 1
2404:6800:4006:806::1007 via fe80::d267:e5ff:feb5:235b dev em1  proto static  metric 1
2404:6800:4006:806::1009 via fe80::d267:e5ff:feb5:235b dev em1  proto static  metric 1
2404:6800:4006:806::100a via fe80::d267:e5ff:feb5:235b dev em1  proto static  metric 1
2404:6800:4006:806::100b via fe80::d267:e5ff:feb5:235b dev em1  proto static  metric 1
2404:6800:4006:806::100c via fe80::d267:e5ff:feb5:235b dev em1  proto static  metric 1
2404:6800:4006:806::100f via fe80::d267:e5ff:feb5:235b dev em1  proto static  metric 1
2404:6800:4006:806::1011 via fe80::d267:e5ff:feb5:235b dev em1  proto static  metric 1
2404:6800:4006:806::1015 via fe80::d267:e5ff:feb5:235b dev em1  proto static  metric 1
2404:6800:4006:806::101d via fe80::d267:e5ff:feb5:235b dev em1  proto static  metric 1
2404:6800:4008:c03::54 via fe80::d267:e5ff:feb5:235b dev em1  proto static  metric 1
2404:6800:4008:c03::5f via fe80::d267:e5ff:feb5:235b dev em1  proto static  metric 1
2a00:1450:4001:807::100f via fe80::d267:e5ff:feb5:235b dev em1  proto static  metric 1

Seeing as this seems "weird", I'm assuming these are also created by NetworkManager.

My only question is why? These routes surely are not needed for anything if we have a working default route.

Cheers,

Dan


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]