Sebastian Freundt wrote:
You were referring to an ISP having to monitor subscriber traffic.
That has nothing to do with getting permission to use an RFC1918 address on the local network. Does your ISP see that 192.168.x.y address? Not if you're behind your NAT router. Is the ISP providing that subnet?
Nope, and nope. They do see traffic I happen to route to the routers address (::1 in my /64 here) from addresses other than my assigned one (::2 in my /64 here). And even though technically it's possible to route that traffic, they don't, because I don't give them enough money. So what's the problem again?
I'm not sure what you have there. You say you have a single address. How many computers do you have? If more than one, how are they connected to your ISP? Also, ::1 is an address with a string of 127 "0" bits and one "1". It seems very strange to have that sort of address, unless you're referring to a router on your local network, in which case it should be <your network address>::1. For example, on my network, my routers address on my network is the subnet address provided to me followed by ::1. All the computers have the same network address followed my the MAC derived or random portion. An address that's simply ::1 or ::2 is outside of the allocated unicast address range.
Why do you keep dragging BGP in, when it has nothing to do with the
discussion? Use of a subnet does not require BGP. BGP is only used for automous networks, with multiple routes. That does not descripe the typical subscriber, business or home, user.
Well because if you insist on configuring*your* network it requires you to set up BGP and talk to other carriers, how would they know about*your* network otherwise? From your statement below I get the impression you confuse tunnel'd 6-in-4 traffic (where there IS a BGP entry to `your' (read your tunnelbroker's) network actually you just didn't bother thinking about it) with a native setup where you get your /64, an *assigned* static address within that /64 (mostly ::2), a router address (there's experiments to propagate that through ppp, but for now it's mostly in your /64 the ::1) and that's all you have.
Did you overlook the fact that you have NO control over the remote side's router? Or are you talking about something completely different, see below.
Once again. BGP is not applicable because I do not have an autonomous network. I get a single subnet from the tunnel broker and it is they who would use BGP and not me. For my subnet, they'd be using something like RIP or OSPF, as there is no need for the function that BGP provides. Please look up interior and exterior routing protocols to understand the difference.
With IPv4, addresses are scare. With IPv6, they are extremely
plentiful, so there's no need to ration or charge for them. I get my /56 subnet from a tunnel broker for absolutely no cost. Others hand out /48 subnets, again at no cost.
What do you mean by tunnel then? I thought tunnelbrokers are part of the transition plan and give you a v4 address that you can send 6-in-4 traffic to
I use a 6in4 tunnel to transport IPv6 over IPv4. It does this by placing a 20 byte IP protocol 41 header in front of the IPv6 packet. Tunnel brokers are the organizations who offer this service. They convert the packets to/from 6in4 tunnels to the IPv6 internet.
Well native connectivity costs money here, what can I do about it?
The connection is what costs. It doesn't cost any more to carry more than one address as it is all data over the link. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org