The only other thing in the mix is a dumb gigE switch between my ONT and my pfSense box (in case I want to give something else a public IP... like the vpn/AP device my work gives me that I don't want anywhere on my network :)
I also wanted to ping the IPv6 Experts here to make sure its not just me misconfiguring.
I am running a Mikrotik RouterOS, so configs are a little special.
So I went to the Labs config page to "request" an allocation.
I assume the first is the address of the of the 6to4 interface I should create, and the second is the allocated address space I should use? Maybe?
So I created a 6to4 tunnel interface with my WAN IPv4 and the specified tunnel endpoint.
I picked a /64 from the address space 2001:5a8:4:55::1/64 and assigned it to the LAN side.
I enable RA messages for that interface.
I also enabled ND for the LAN interface to advertise DNS and the prefix.
I also enabled ND for the WAN 6to4 interface (?) but disabled DNS and configuration, just MAC addr.
Which works and now my hosts are picking addresses.
And I can ping the router. I can also ping the 6to4 interface.
But of course I cannot ping anything through there.
Looks like my packets head through the 6to4 interface and disappear.
Is that pretty much expected until the IPv6 is supported in some state?
You mean 6in4.6to4
There was a couple of details missing / confusing in the configuration details.
Firstly, the tunnel type is 6in4
Secondly, the ipv4 server-side address for the tunnel is 220.127.116.11
Thirdly, the ipv6 server-side address is the one listed as "Transport::" on the Labs->IPv6 Tunnel page in the Sonic customer portal (the one that ends in /127)
Lastly, and most confusingly, you need to set the current IPv4 Address of your router in the Labs->IPv6 Tunnel page. Where it says "Your current tunnel endpoint is:" you need to enter your current Sonic IP address. Once you enter it, click the "View/Request/Change Tunnel" button and it will be saved. I'm guessing you need to update it every time your IPv4 address changes.
I have it working on my ASUS router, using the 6in4 Tunnel option with the following values:
The Server IPv4 Address is 18.104.22.168 (and will be the same for everyone).
The Client IPv6 Address is the ipv6 address that Sonic calls "Network::" on the Labs->IPv6 Tunnel page (the one that ends with /60)
IPv6 Prefix Length is 60
Server IPv6 Address is the ipv6 address that Sonic calls "Transport::" on the Labs->IPv6 Tunnel page (the one that ends with /127)
I set LAN IPv6 Prefix to the Client IPv6 Address from above, and LAN Prefix Length to 64 (60 should work too).
Best Current Operational Practice for Operators: IPv6 prefix assignment for end-users - persistent vs non-persistent, and what size to chooseAssigning a /64 or longer prefix does not conform to IPv6 standards and will break functionality in customer LANs. With a single /64, the end customer CPE will have just one possible network on the LAN side and it will not be possible to subnet, assign VLANs, alternative SSIDs, or have several chained routers in the same customer network, etc.
This is rectified on newer enablements, I get a /56 prefix.davygrvy wrote: Notice that the prefix delegation size is /64 when it should be /56. A /64 delegation can not be divisible; it is only one address block. It is useless for subnetting.
Who is online
Most users ever online was 999 on Mon May 10, 2021 1:02 am
Users browsing this forum: No registered users and 1 guest