On 11/17/2011 10:17 AM, Sebastian Freundt wrote:
Yes, but in Windows it's just a click, or two, under SuSE it's worth a whole long discussion that has been going on for quite a while and to be honest I lost track if the OP has found a solution or not.
Thanks for everyone's help, it was a true learning experience. After checking with the network gurus here we've got things sorted out. These guys know what they're doing and this particular network has received international accolades for leading the way in IPv6 implementation. They have enough clout that they can actually affect IPv6 policy at Google, Apple, and security-stack hardware vendors. They're good guys. One of the admins penned this morning: thanks for the info. sounds like SuSE Linux has moved to the new default for IPv6 configuration. Win7 and OSX Lion both default to choosing (and changing) a private IPv6 address. that's what we are watching on the testbed VLAN 44. OSX changes the v6 address every 24 hours and keeps the previous handful active on the interface for some days. currently the v6 sweeper on V44 tries to keep the newest IPv6 address registered for a device in DNS and LDAP, assuming that it is the "today" or "after reboot" current address even though others may still show up in the neighbor table on the switch. your host is treated to the old v6 sweeper logic so when it saw a SLAAC address it registered that for him and it will stick. So the problem is basically our network's, in particular the v6 "sweeper", I think. They switched me to the test VLAN and we'll see what happens. I'll report back any SuSE specific issues that might pop up. Now, I'll download 12.1 FCS and go to town! Thanks, Lew -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org