I was surprised that no one else replied THIS to this thread already.
If you had an authenticated account - you can connect to the authenticated server(s) and get a /56 prefix delegated to your connection. Then your computer with the Gogo6 Client program becomes an IPv6 Router for your local network. There is a check box for Enable Routing Advertisements in the Advanced tab. Then computers, iPhones, laptops, etc. that are IPv6 aware will automatically configure themselves using your prefix to a compatible Ipv6 Address and will use your Gogo6 (Router) computers Link Local (FE80) address as their gateway for IPv6 traffic to all other networks (meaning the Internet.)
* So what they are saying above is that you cannot use the GoGo6 client on more than one computer to make more than one Tunnel to get IPv6 ... but you can use "authenticated" service to get MORE than enough IPv6 Space and share it with all of the computers and devices that you have on your network. It's kind of reminds you of the old Internet Connection Sharing in Windows, although this is actually different, but it does Connection Share 1 single IPv6 Tunnel. Your computing devices actually Auto-Configure themselves using the Routing Advertisement messages to actual world route-able IPv6 addresses based on your Network Prefix. They just have one more router hop, your Gogo6 computer. Your computing devices are treated as real IPv6 hosts with Unique Global IPv6 Address ... all the respect and all the functionality that you need. :-)
I have always understood that only one computer could use to connect using an authenticated account. This is because you are assigned a static IP address which, of course, cannot be assigned to more than one computer. For this reason, when away from home, I use an unauthenticated connection on my notebook computer. As for the comparison with Windows connection sharing, that is not accurate. The NAT function in a firewall/router would be similar to it. With the gogonet tunnel, configured for a subnet, your computer is acting as a regular router, making individual public addresses available to each device. This is the way the internet was intended to be used, before the IPv4 address shortage forced the use of hacks such as NAT, to connect more devices. The only difference between using a subnet with gogonet and regular rooting, is the use of a 6in4 tunnel to get IPv6 to you via an IPv4 only provider.
I pretty much already knew everything that you just wrote. My reference to Windows connection sharing was a loose similarity in functionality comparison ... and I think I said that (in other words) ... and I said that "... actually auto-configure themselves using Routing Advertisement messages to actual world routable IPv6 addresses..." I don't see where anything was not accurate.
A bicycle is *like* a car in that it gets you from one place to another, although this is actually different ... because they are constructed differently and use different propulsion systems. But they do provide transportation. And the Gogo6 Client with a /56 Prefix does share that IPv6 connection - being similar to WIndows ICS in that it Shares the Connection.
Why can't they just say, "Go to this place, and here's the treasure, spend it wisely"?
(National Treasure - Movie.)
My comment was that connection sharing is the same as NAT firewall, in that all computers using it appear to be coming from the same IP address. This is not the case with gogonet where every computer has it's own unique public address(es)¹. This means that if you want to reach an individual computer, you can, without having to worry about port forwarding etc.
1. With recent operating system versions, you can have both a MAC based address and a random number based address. This is done because some people consider a MAC based address a privacy risk. So, you use the random address when "surfing the web" and the MAC address when you need DNS to point to a computer. The random number address will change frequently.
Ok, 'nuff said. This growing beyond the FAQ/Thread topic. I'd love to chat more - but I think this would need to move to a new thread.
My whole point of posting in this thread was just to say that there was a way to share your Gogo6 Freenet Connection ... and you hit me on a technicality there ... and again on the Windows Sharing comparison. So we're down to having a battle over words - even if I wasn't really ever wrong. Nothing personal ... you want to talk. You have the chair. You are giving more details - not really needed to just to share 1 connection on this with multiple computers. It's nice to know more - but not necessary.
You can share a Freenet authenticated connection on your LAN. There's the treasure ... spend it wisely.
Not directly - as in having the Gogo6 Client on more than one computer logged on at the same time. No.
Can you share a Gogo6 Client's IPv6 Connection with more than one computer on a Local Area Network (LAN)? Yes you can with Authenticated Service. This doesn't work with Anonymous Service.
(Now for the technically advanced... Am I missing anything other than Authenticated Service in order to Turn on this Sharing Capability that will derive from a /56 being delegate and what happens automatically on the LAN? I don't remember if I had to do anything specifically to Request the /56? But I think it turns on (it's a toggle in the settings) Router Advertisement and that allows Computing Devices on your LAN to Auto configure themselves and use your Gogo6 Client Computer as an IPv6 Router.)
You need to run radvd and ensure the firewall can pass the IPv6 subnet.
You need to take a break.
I haven't run the Linux version of Freenet for awhile ... but I did some years ago. I would imagine by now that they've automated that into the Client software on that platform. I guess I was mostly talking about the Windows Gogo6 Client. We were harping on Windows before. So now we're going to harp on Linux?
Steve Jobs, if he were still alive, would tell you to Keep it Simple - Keep it Beautiful. It's a beautiful thing. I don't think we're really talking about a production Linux Server environment in this thread anyway. If we were then yes we'd have to worry about all of that. And Freenet would be too slow anyway for production server Ipv6 traffic. it would need to be a real ISP IPv6 arrangement.
I did put Freenet on a Business DSL connection for awhile with real web domains ... mainly as a test - so I could do the DNS and Firewall and all of that. So still ... nothing new here.