I know it should be possible by tweaking the mac address, but a self specified address (as rfc states), could be much more better than just a software limitation.What does "stateful" link-local IP mean?
Does this mean that you want to assign a static link-local address? I know Cisco lets you do it, and it's nice because you can make the access router on a segment be a simple fe80::1 for every network...
You can fake this with a Mikrotik by changing the administrative MAC address of the interface to something that maps to what you want, so long as you're prepared to accept the fffe in the middle....
.... so if this is what you mean, then add my vote for this.
This is a great read. I've been using fe80::1 as the link-local gateway for a while in GNS3 for my Cisco labs - it's cool to see that this was a good idea in others' opinions. I'm going to go read the rest of the links at the end of this page.
Yes - we would really like to see this feature as well. No need to use EUI64 address for static default gateway for a device (we don't assign global addresses for ptp subnets, relying entirely on link-local).For those interested - the code is one nibble for network region (aka OSPF area) with the next 2 nibbles for router number within the region. With our relatively small number of routers and regions, this should scale well for us for quite some time. So in region 8, router 2's block for customer assignments would be 2001:db8:8020::/40, and its loopback address would be 2001:db8::802. Therefore, all of its active OSPF transit interfaces would have fe80::802 as the link-local address. (customer-facing interfaces will all be fe80::1 for primary routers and fe80::2 for backup routers)
nope. in this case - for example GRE - routeros just takes the remote IP address in hexadecimal format, and generates link local addresses by putting them into the last 32 bits of the addressThis is the most frustrating side effect of not being able to manually configure link local addresses, preventing us from deploying IPv6 to a site entirely.
[me@router] /interface gre> add remote-address: hgw.netadmin.hu [me@router] /interface gre> print Flags: X - disabled, R - running 0 name="gre-tunnel1" mtu=auto actual-mtu=1476 local-address=0.0.0.0 remote-address=hgw.netadmin.hu current-remote-address=126.96.36.199 keepalive=10s,10 dscp=inherit clamp-tcp-mss=yes dont-fragment=no allow-fast-path=yes [me@router] /interface gre> /ipv6 address print where interface=gre-tunnel1 Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local # ADDRESS FROM-... INTERFACE ADV 0 DL fe80::2:bc06:c79f/64 gre-tunnel1 no
well, you can still specify addresses if you want, as you're not limited to have just one or two addresses on the link.The ability to manually specify the Link-local address can make other things easy than just a consistent default GW on all network access segments.