@bmeeks I'm a lot luckier with my ISP. They've been providing native IPv6 for about 6 years and via 6to4 and 6rd tunnels for a while before that. They are also my cell phone carrier so not only does my phone get an IPv6 address, but so do devices I tether to it. Also, my IPv4 address is virtually static and the host name depends on my hardware MAC addresses, so I have no problems with connecting my VPN to my network.

@martywise My IPv4 address is virtually static, but my host name is based on modem and router MAC addresses. If I change hardware, the host name will change. If I change my router or it's NIC, my address will change. On IPv6, my prefix has survived modem and complete replacement of the box I run pfsense on. I suspect it might take a nuke or two, to change it.

@johnpoz said in Access my website from WAN IP: That would be a feature request or bounty.. I am going with feature request.

@johnpoz Done https://redmine.pfsense.org/issues/12600

@almodovaris DHCPv6 does not work with Android. You'll have to switch to SLAAC.

Ok i just gave up on getting pfSense to generate a working configuration... If something in my ISP's weird setup is causing it, a bug or the position of the moon i have no idea. But it works when writing the config file manually and adding the interfaces. The interface still shows nothing about the delegated prefix but everything is working. RA's set to unmanaged on the local interfaces. The config file that works with my setup (on Kviknet in denmark): interface xn3 { send ia-pd 1; send ia-na 1; script "/var/etc/dhcp6c_wan_script.sh"; }; id-assoc na 1 { }; id-assoc pd 1 { prefix ::/48 infinity; prefix-interface xn0 { sla-len 16; sla-id 1; }; prefix-interface xn1 { sla-len 16; sla-id 2; }; };

@abcdefabcdef were you able to resolve telmex's IPv6 connection in bridge mode?

@johnpoz i installed the cert and added it to the trust store so i'm assuming i did lol cool ill take a look

So my config was perfectly fine. rebooted the server and it just suddenly started working. guessing something getting cached

Well... Actually i had quite the same problem as in the referenced thread: The issue was also caused by the WLAN infrastructure (but ExtremeNetworks AP130 AP250 Firmware 10.3.x). I have connected the conspicuous devices to the "WIFI VLAN" via USB-RJ45 adapter and have not seen any problems in the IPv6 connectivity. I also made a case to the WIFI vendor.... Sorry for the noice.

@hmf said in IPv6 and internal DNS registration: Version 21.05.2-RELEASE (amd64) I'm on 2.5.2 (amd64), which is the latest for non Netgate gear. I didn't know there was a version 21 for AMD.

@johnpoz You may not need it now, but the more people procrastinate, the longer it will take to move to IPv6 and the world as a whole will suffer for it. The shortage of IPv4 addresses was obvious many years ago and even to me, when I was just learning about IPv4. I remember sitting in the class and thinking to myself that 4B addresses wasn't enough. We need more mandates to provide IPv6, just as happened in India, China and elsewhere. The move to IPv6 is being driven by the 3rd world, when we should be leading, not following. In Canada, many companies are providing IPv6, but for some reason not Bell Canada, where even on their cell network, where IPv6 is mandatory for 4G, they do a poor job of it. Curiously, Telus, which is Bell's partner (they even shared cell networks) in the western part of the country, was one of the first to provide IPv6, even before Rogers, which I'm on. All the Canadian cable companies I'm aware of provide IPv6, as do some of the resellers that use Bell's ADSL network or Rogers' cable. Sticking with IPv4 is crippling the Internet.

@jknott Thank you so much for pointing that out. The presense of the 192.168.0.0/24 address should have been a clue. Stupid me didn't think of bridge mode. I was able to enable bridge mode and everything is working as expected.

@linuxtracker I tried but still the same problem The name resolution works but I cannot ping nor access a LAN device in IPv6. Thanks

I realized my /60 prefix from Xfinity had changed, once I updated the NPt mapping all is well again. I was thinking that if the prefix changed, the v6 gateway would go down - but, that didn't happen. If anyone has any suggestions for how I might monitor a prefix change without using DHCP6 I'd be very appreciative. Unfortunately, I don't think I can have two interfaces each pulling prefixes with DHCP6: https://redmine.pfsense.org/issues/6880 My workaround was to get the prefix through DHCP6 on the Xfinity interface, then use the assigned ipv6 address, gateway and prefixes to for a static configuration. Can't figure out a better way...

@bob-dig Windows is my home's Domain Controller, DHCP (DHCPv6) and DNS -- soon to be LDAP. I make all address reservations in Windows Server 2019. I am hoping that once I get to the LDAP configuration - I can set pfSense to use LDAP credentials to login - rather than the local account I use now.

@jpvonhemel COMCAST support forums are a huge Joke!!! You got all the COMCAST Staff in there telling you their favorite answer "that configuration is 'not supported'" Trust me - I have B.T.D.T (been there done that). I think I got it working in another way - back to 19/20 - still cannot figure out why I cannot get Hostname for ipv6 to show on the test. I can ping the IPv4 and IPv6 address of the DC and pfSense with name resolution - and they come back with the name from the DC. [image: 1636250571370-b9bcc81a-ac80-4924-ba03-21e23fd72d2e-image.png] From other machines on my network I get this [image: 1636250385736-900cfeeb-31b2-4629-81d9-091153f2d818-image.png] It resolves the NAME - but get ping failure. I checked the Firewall on that workstation and ICMP is on - otherwise it would not have resolved the name or pinged at all.

My comment keeps getting auto-flagged as spam (not the first time) so here's an image of it. [image: 1635365980056-reply.jpg]