So I am running multi-WAN, and I do have NPt set up to translate my /48 with an HE.net /48 on my backup connection, and I see the same behavior you posted a screen shot of. I tried removing the NPt rule and still observed the same behavior on my primary WAN (IPv6 address being reported as the router WAN IP, not my desktop IPv6 address)

Any suggestions on things I could check or this just a side effect of using multi-WAN and gateways w/fail-over?

@ksdehoff Odd that yours didn't work for the static mapping, maybe because I enumerated the entire interface ID (::7d86:e96:bb0c:fe85 for example). So I don't have to mess with changing anything in the static mapping. I had another issue unrelated to it (caused by Snort of all things) and I had as part of troubleshooting, unchecked the 'do not allow release...' setting and rebooted, and yep the prefix changed and the servers got new IPs with the same interface ID and the new prefix. So I am happy with that small victory.

@nineeyes

maybe you have a wrong address somewhere
or maybe the address changed

I would check the $FRIEDL_FARM interface settings to see if there are wrong settings there

Hmm... look... another ISP (in Germany this time) with the same issue. I guess Comcast isn't the only one broken. Can this be looked into now to see where the problem lies as far as pfSense's handling of prefix size received being different from prefix size requested?

https://forum.netgate.com/topic/159463/ipv6-not-working-wan-and-lan-interface-getting-an-ip-adress-not-any-client

@gamienator-0

At the moment, you're using an even number prefix. What happens if you pick an odd one? That /63 moves the boundary between the prefix and suffix over by one to the left. Will a prefix ID 1 now be the same as 0?

@jknott Yes, the "routing" is done by link local address.

@johnpoz

Perhaps a touch. However, I have noticed a lot of misunderstanding about IPv6, because people are so used to IPv4. While many things work the same way, some others are quite different. When I had that IPv6 problem, a couple of years ago, I found I had to educate the 2nd level tech support (I wouldn't waste my time with 1st) and senior tech at my ISP on the finer details of how some things worked with IPv6.

As for the WAN address, a public address is entirely optional with IPv6, relying on the link local address for routing. That seems to be quite a leap for many to understand.

@johnpoz said in ipv4 only no more:

How many vlans do you have?

I have 8 subnets/vlans.

LAN (default vlan): Switchs, APs and controller
Infrastructure: Pi-Hole
Home: iPhones, iPads, Macbooks
Media: LG TV, Roku TV, Apple TVs, Sonos Speakers
Server: Synology and QNAP NAS
Printer: HP printers
IoT: Kindles and Bike Computers
Guest:

I have 3 SSIDS

Freeside: Enterprise Radius assigned VLAN
Chiba: PSK Radius assigned VLAN by MAC address
Sprawl: Guest

I put everything I could on Freeside, including one of my printers that supports WPA2 Enterprise EAP-TLS. Lots of fun with Apple Configurator for the others.

Chiba gets the kindles, bike computers and Roku TV. Before anyone has a fit, no you can't get on this network by MAC address only. They are only used to do VLAN assignments. You still have to know the pre shared key. Unifi is kinda misleading with this, they call it 'RADUIS MAC AUTHENTICATION". I tested this and found that you have to have a user in Radius that matches the MAC address and the PSK. Radius shows it as a successful logon if you have no password or the wrong password but the AP doesn't connect you in that case. Maybe you could do this on an open network or do something in Radius to make it a MAC bypass. That is a terrible idea.

Sprawl is the guest network.

Everything that is stationary is on a wired connection with the exception of the Roku TV and one Apple TV.

One printer (an all-in-one) is on a cart and connects to Freeside (didn't know it supported Enterprise EAP-TLS until recently, never bothered to look when I bought it) :)

I violate the F out of the L2 segregation using avahi (mDNS/Bonjour) and udpbroadcastrelay (SSDP, for the Sonos). I'd post up all my firewall rules but that would just serve to make me look dumber than I already do. They get the job done but are not nearly as locked down as they could be.

There is a lot that could be improved. We're probably going to move late spring/early summer and that will be the time to get some gear that is quieter and more energy efficient. A Netgate appliance and new switch(s). Get rid of my unifi stuff and replace them with Ruckus APs if I can find some for a decent price used. Put bigger drives in my Synology and retire the QNAP. There's always something...

@jan_berg This approach seemed to be working for me: https://wiki.cable-wiki.xyz/OPNsense

Caveats:

Can't be done through UI, needs to be executed in a shell. The tunnel will not be visible in the UI. Doesn't persist. Would need to re-execute every time the WAN comes up and has a global IPv6 assigned. Need to extract the AFTR name and its IPv6 address. In my case, the name comes through via DHCPv6 from the ISP as option 64. Could extract it via tcpdump. Then resolved it to an IP address and used that when setting up the tunnel. Breaks again if AFTR name/IP changes.

So, no real DS-Lite support in pfSense currently, but possible to set up manually.

@jknott Honestly, I don't think I ever intentionally set anything up for that (nor knew it was an option to disable it either). It's just something that's always been there on the dashboard. I assumed it was pfsense pinging the gateway address and getting the answer (since the gateway is usually given by dhcp on the WAN).

I just found the checkboxes to disable it - all good :-)

8be775e9-6ceb-4d0d-90d3-7915e64cb8fa-image.png

@pfguy2018

I recently changed the rules for my guest WiFi VLAN to IPv6. in some cases it was only necessary to change from IPv4 to IPv4 & IPv6. I have only one rule that is IPv6 specific and none that are IPv4 specific. That IPv6 one is to block anything within my prefix.

Here are my rules:

Screenshot_20201212_161304.png

@jknott OK - so have sussed it -am on a pure IPv6 connected PC now! So Static IPv6 address on link, DHCPv6 disabled, but RA set as assisted with a DNS server with the link ipv6 address set on the RA tab.

So I think this is SLAAC + RDNSS working properly?

Even managed to use a literal IPv6 address for the pfsense box - https://[ipv6 address] needed in edge - square brackets eh?

Irony of testing though one of the Test -Ipv6 sites I was using didn't resolve an IPv6 address (test-ipv6.com) where as ipv-test.com was happy!

@bob-dig

All the addresses appear automagically. One of each type is consistent, based on the MAC address. The privacy addresses are based on random numbers. The only thing I configure is the DNS entries, which I point to the consistent addresses. I do not ever use a privacy address for DNS, as it would only last for a week. It is also possible to have consistent addresses based on a random number, for those who are worried about someone tracking their MAC address.

@gertjan

While I haven't seen 2 link local addresses in a device with only 1 interface, multiple routeable addresses are common. For example, this computer, once it's been up for a week, will have a total of 16 routeable addresses, 8 global and 8 unique local. Of those, one of each is consistent and MAC based and the others are privacy addresses, of which I get new ones every day, with them expiring after 7 days.

I see. Will tracerouting the ipv4 addresses shown in the registration process be sufficient to tell if a specific tunnel endpoint is a good choice or will it require registration and bringing up the tunnel itself to be sure?

True, line 9 :
@kaj said in ICMPv6 Trouble?:

prefix ::101:101/128 {

is not ok at all.

@wlp94611 see https://redmine.pfsense.org/issues/10984

You've probably either figured this out already or just decided to ignore it but I have found that those errors are typically caused by an IPv6 client that doesn't support DHCPv6 and your IPv6 Router Advertisements are configured not to support SLAAC (set to either "Managed" or "Disabled" on that interface).

Under "Services/DHCPv6 Server & RA", change your RA mode to "Assisted" or "Stateless" on the interface those clients are connected to and this error should disappear.