I can't visit the https sites
-
I think he is just saying he is running native IPV4 and not native IPV6.
Not sure what other issues he is having.
My HE is set up same as yours, except I'm accessing it via a Openvpn Tunnel that supplies me a dual stack here, so I have to provide a route to the VPN.
Other than that its identical to what your pics show. Works.
I think he should also post his configs and firewall rules.
-
I think he is just saying he is running native IPV4 and not native IPV6.
Not sure what other issues he is having.
My HE is set up same as yours, except I'm accessing it via a Openvpn Tunnel that supplies me a dual stack here, so I have to provide a route to the VPN.
Other than that its identical to what your pics show. Works.
I think he should also post his configs and firewall rules.
yes. I am running native IPV4 and not native IPV6.
I using ipv6 /48 for lan. just visit test-ipv6.com is normal work.
-
The IPv6 address on your IPv6LAX interface AND the local address on your GIF tunnel should be 2001:470:c:1089::2 and the netmask /64.
Assign /64 subnets from your routed /48 to your LAN interfaces, not /48. Carefully look at the two examples already provided.
In short, your IPv6 config is completely wrong. You might want to delete it and start over.
https://doc.pfsense.org/index.php/Using_IPv6_on_2.1_with_a_Tunnel_Broker
-
When you get that up and working on the LANs and you want it to also work for openvpn clients, let me know - Its not much more to do.
-
And there's a /48 on the DHCPv6 config which should probably be /64 to match the /64 you have converted your LAN to. unmanaged works just fine. It might be good to reduce the complexity at first and just use that. I've never configured DHCPv6.
-
Iwant to use short /48ip address, before it was normal work in /48
-
I try setup MSS to 1220, just /48 ipv6 work..
-
https://forum.pfsense.org/index.php?topic=81698.0
-
I think best setup is MTU 1472 and MSS 1412.
The maximum segment size (MSS) is a parameter of the TCP protocol that specifies the largest amount of data, specified in octets, that a computer or communications device can receive in a single TCP segment. It does not count the TCP header or the IP header.[1] The IP datagram containing a TCP segment may be self-contained within a single packet, or it may be reconstructed from several fragmented pieces; either way, the MSS limit applies to the total amount of data contained in the final, reconstructed TCP segment.
The default TCP Maximum Segment Size is 536.[2] Where a host wishes to set the maximum segment size to a value other than the default, the maximum segment size is specified as a TCP option, initially in the TCP SYN packet during the TCP handshake. Because the maximum segment size parameter is controlled by a TCP option, a host can change the value in any later segment.
Each direction of data flow can use a different MSS.
To avoid fragmentation in the IP layer, a host must specify the maximum segment size as equal to the largest IP datagram that the host can handle minus the IP header size and TCP header sizes.[3] Therefore IPv4 hosts are required to be able to handle an MSS of 536 octets (= 576[4] - 20 - 20) and IPv6 hosts are required to be able to handle an MSS of 1220 octets (= 1280[5] - 40 - 20).
Low MSS values will reduce or eliminate IP fragmentation, but will result in higher overhead.[6]
For most computer users, the MSS option is established by the operating system.
-
