|
fe80:: route is odd
![[us]](/s/countries/us.gif) Shadow Hawkins on Thursday, 04 February 2010 06:20:19
I configured my machine, which uses aiccu with a dynamic tunnel, with radvd to advertise a /64 from the /48 subnet I've been allocated. Hosts on my LAN are generating ip's within the advertised /64 with no problems. It all comes up when starting networking, but one thing is odd, I haven't quite figured out why it's doing this:
fe80::/64 dev eth0 metric 256 expires 21333365sec mtu 1500 advmss 1220 hoplimit 4294967295
fe80::/64 dev sixxs metric 256 expires 21333376sec mtu 1280 advmss 1220 hoplimit 4294967295
I can manually drop the fe80::/64 route from going out to the sixxs dev, but I'm not sure what would even be making it go out this interface in the first place. It's a Mandriva box, so I suppose it _could_ be a bug. My limited Googling hasn't resulted in any hits on ipv6 bugs with Mandriva networking scripts.
As an aside, do I just pick a /64 at random from within that /48 for radvd to advertise? It's what I did, I'm just checking how other people choose the /64 to advertise.
fe80:: route is odd
![[de]](/s/countries/de.gif) Shadow Hawkins on Thursday, 04 February 2010 07:31:00
Those are link-local routes added by default to every interface which is brought up. They are not bugs. Don't drop them. Ignore them. You probably won't notice them. They are don't cross routers. You can read up on those in any IPv6 primer.
Yes, pick a random /64 out of your /48. For simplicy, use 0, then you can simply use :: in its place. Again, this is documented in every basic IPv6 document.
fe80:: route is odd
Shadow Hawkins on Friday, 05 February 2010 03:22:17
Thanks, I had interpreted "interface" to mean "physical interface". You're saying that's incorrect and it does include virtual interfaces, as my tunnel interface is. I can handle that.
Thanks for the reply.
fe80:: route is odd
Shadow Hawkins on Friday, 05 February 2010 04:40:53
As far as Linux is concerned, it doesn't matter whether an interface is created by a tunnel, a user-space driver, or whether it's physical: they are all treated the same.
fe80:: route is odd
Shadow Hawkins on Friday, 05 February 2010 05:49:13
They are layer 2 abstractions analogous to MAC addresses, and in fact on ethernet they are usually derived from MAC addresses. (My Win7 box seems to be making up its own link local addresses, though.) You definitely need them, but will probably never refer to them directly.
|
Posting is only allowed when you are