Leopard and Static IPv6 addresses
I think I've encountered a bug in Mac OS X 10.5's IPv6 configuration tools. If I try to configure a static IPv6 address in System Preferences, I don't actually get an IPv6 address. Here's my networking configuration:
When I run ifconfig(8), I don't have an inet6 entry:
$ ifconfig en0 | grep inet
inet 172.28.73.53 netmask 0xffffff80 broadcast 172.28.73.127
However, if I configure it from the command line, it works fine:
$ sudo ifconfig en0 inet6 2610:8:6800:1::40a/64
$ sudo route add -inet6 -prefixlen 64 default 2610:8:6800:1::1
add net default gateway 2610:8:6800:1::1
$ ifconfig en0 | grep inet
inet 172.28.73.53 netmask 0xffffff80 broadcast 172.28.73.127
inet6 fe80::216:cbff:feaa:879d%en0 prefixlen 64 scopeid 0x4
inet6 2610:8:6800:1::40a prefixlen 64
If I select autoconfiguration in System Prefs, I get an IPv6 address.
I'm going to check this on another machine on my home network before I file a bug with Apple. Has anyone else seen this?
0 TrackBacks
Listed below are links to blogs that reference this entry: Leopard and Static IPv6 addresses.
TrackBack URL for this entry: https://blogs.psu.edu/mt4/mt-tb.cgi/634
Thanks for posting this. I ran into the same problem today and you saved me a lot of time trying to resolve it.
Glad to be of "help," even it's just confirming that a bug exists. I reported this to Apple as a serious bug, but it's not fixed in the latest 10.5.2 preview. For the time being, I'm still using 10.4 on my desktop.
I can confirm: it's still broken in 10.5.2.
Hmm. It is fixed for me in 10.5.2.
Can someone confirm, I have the same issue on 10.5.6 and submited it as bug to apple. I need a confirmation that someone have also problem with this.
I've not see it on 10.5.6. I can't reliably reproduce the problem. So far, I've only seen it on a Mac Minis, not on MacBook Pros or Mac Pros. I can't imagine why the platform would matter though.
You should open a bug with Apple over it. The worst they'll do it flag it as a duplicate.
The workaround is down and up interface after change.
is this still an issue ?
Yes, I still see it on 10.5.7, the latest stable release.
drixter, that workaround doesn't work for me on 10.5.7.
Still broken in 10.5.7 OS X Server. Just had to do it for a new box.
All I can suggest is opening bugs with Apple.
I can't seem to consistently reproduce this bug. Some machines will consistently show it, others never do. It makes triaging it difficult.