James Knott
Sebastian Freundt wrote:
Nope, it doesn't matter what you think is suitable or not, my point is that it must be just as easy to adapt to the one situation as to the other.
I can tell you that if I were to plug my computer into that network and booted into either Linux or Windows, I would have that problem, because either way, I would have both MAC and random addresses.
Yes, I know, me too actually. Still, as a network admin, I wouldn't change my network policies just because some devices can't use my network out of the box. And you should be more specific, Ubuntu 11.10 CAN access the network in question out of the box, it's just SuSE 12.1 that can't.
OK, get a new computer with Windows 7 on it. What will happen? This is the situation that most networks will face soon if not already. What will you do about it? You'll have to do exactly the same thing to accomodate 12.1.
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. [snip]
PS: I have been talking to them, and they do offer a fully routed /64, and even a /48, alas they expect me to pay a lot more dosh for that.
You may want to refer them to the IETF guidelines on this. http://www.eu.ipv6tf.org/PublicDocuments/guidelines_for_isp_on_ipv6_assignme...
I'm pretty sure they're aware of this document, after all you're free (not monetarily unfortunately) upgrade and get a /64 or a /48 which is completely routed.
However, this is an example of someone being stuck on IPv4 methods. With IPv4, the shortage of addresses limited what an ISP could offer. With IPv6, there's absolutely no valid reason for not offering at least a /64 subnet. I get my IPv6 subnet from a tunnel broker and it's a /56 (256 /64 subnets). Others offer /48. With the tunnel broker I use, I can configure for either a single address or a subnet, but it's entirely my choice and not theirs.
Nope, that's exactly where you are wrong. Unless you possess an ASN and sign up with a carrier giving you BGP access, you canNOT freely do whatever you want. You have no right and they have no obligation, it's their network after all. What lawful or otherwise (protocol?) enforcing options do you have when your tunnel broker or ISP decides not to route X::dead:beef? Exactly, none. And my theory is that tunnel brokers hand out /56s or /48s for you to get used to them, and then they up their prices when you want them natively. Btw, I expect as much resistance for the orthogonal problem, a network operator with too permissive routing rules. The other day we found out that we can `claim' certain v6 addresses within the surrounding /64s and we reported this as a bug, but (annoyingly) the network operator pointed us to their policies and it's clearly stated how the routing works, which I guess leaves us with the option of putting up with it or wandering off. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org