Sam.Wilson@ed.ac.uk wrote:
Do the ops types include people like me who worry that every time a NIC has to be replaced it's going to require changes to DNS, ACLs and anything else that's keyed on IP address? If not, where do I look to find out why people aren't worried about those things? (And no, dynamic DNS etc doesn't work for us).
See RFC2464 and RFC2373, quote: 8<----------- The motivation for inverting the "u" bit when forming the interface identifier is to make it easy for system administrators to hand configure local scope identifiers when hardware tokens are not available. This is expected to be case for serial links, tunnel end-points, etc. The alternative would have been for these to be of the form 0200:0:0:1, 0200:0:0:2, etc., instead of the much simpler ::1, ::2, etc. ------------>8 Thus 2001:db8::1 is a 'modified' EUI-64 and thus can be assigned. You are just lying a bit that the local scope id is not available and thus you are making it up, but you do correctly set it as per RFC. Also, the network is _yours_ you can do with it whatever you want. It makes your pain bigger when changing prefixes etc. IMHO EUI-64 (read autoconfig) is very handy and useful for hosts, but not for routers or servers and other critical infrastructure. My idea about it is to have the autoconfig still be in effect but configure the 'critical' IP by script/config, this way one can simply deconfigure the IP on one box, while ssh'd to it over it's autoconfigged IP and then configure it on another. Making a poor mans failover possible. Greets, Jeroen