@Lurick said in Do not allow PD/Address release - Specific Interface Only?: needs it checked otherwise your IPv6 prefix will change Yeah for sure could see that.. Because it would release it.. But not sure how some ISP would need a release from you - for stuff to work.. They might give you a different prefix anyway even if you don't release.. But not sending a release should have nothing to do with getting a prefix in the first place. you sure can not send a release when your first asking for one.

@Dough29 said in Subneting my /56 prefix to multiple internal LANs: forum lafibre.info That's where I go to check if any progress exists

@FOOLiSH86 said in IPV6 on pfsense WAN: I wanted to understand how to properly set up full ipv6 support on my pfsense You might want to mention your ISP, as some might have issues. As for pfSense, you need the modem in bridge mode, as gateway mode won't work for this. Then you need to enable dhcpv6 on the WAN interface. Normally, you use SLAAC on the LAN side. I used unmanaged for RA mode. Try getting started and ask about any issues as you come across them. Also, someone might have already posted configuration for your ISP or similar. Here's the info for mine.

@JKnott I appreciate your knowledge and input. Getting that deep with the ISP customer support is my fear. I don't know if its worth the effort. It would probably be easier changing ISPs :). Luckily, the problem fixed itself after several days! I didn't change my PfSense configuration but I did bring the WAN interface down and back up again today. I guess whatever was hanging up the CMTS is fixed as it decided to honor the prefix delegation it supplied me. IPv6 traffic within that prefix range is finally routing back. Thank you again.

@yobyot My IPv4 address is so "durable" it's virtually static. Also, the host name, provided by my ISP, is based on the modem and router MAC addresses, so it never changes, unless I change hardware.

@Mats I was really excited by your comment and went and created an alias that points to ::/56 then created an inverted pass rule for this alias. Unfortunately it seemed that I could still access my other networks via IPv6, so something was weird. But then I've switched from using the alias "::/56" to actually defining the network ::/56 in the firewall rule and it magically started working. So it seems that you're right you can block by using this. Thank you, this has been very useful!

@bmeeks said in Why do I have to 'Track Interface' on LAN to WAN for IPv6 to work?: The correct way to handle this is to use a separate sub-domain for your internal AD setup. Something like mydomain.com for the public IP domain name and internal.mydomain.com for the Windows AD network in RFC1918 space. That can work. A quick Google search will lead you to a Microsoft best practices and how-to article on this configuration. I highly recommend you restructure you AD configuration to match what is described at this older Microsoft link here: https://social.technet.microsoft.com/wiki/contents/articles/34981.active-directory-best-practices-for-internal-domain-and-network-names.aspx. And here is a slightly newer document showing the same thing: https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc772970(v=ws.10). Thanks for the links - one of them I had looked already (as a Google search pointed to it). My public domain name has a - {dash} in it, and apparently my old ass NAS does not like that. I have tried and tried to get it to recognize the domain-name that I first setup as ad.{mypublicdomain} - even a chat session with them for over an hour (nothing worked - they plan no updates to it. It also only does CIFSv1/SMBv1 - FTP (no sFTP) and NFS (but only to Linux boxes) - and some form of iSCSI. I have over 6TB of files and stuff on there, and they "SEAGATE" is not even willing to 'help' me with another NAS to replace it. One of my IT buddies said I should use {mypublicdomain}.loc for my AD/DS...but still going to resolve the - {dash} in there unless I remove it completely. I have considered creating (renaming my public-facing-domain) as only HomeAssistant uses it (well their app on my phone and the ALEXA and GOOGLE links do too). My older post you referenced was assuming the network was IPv4 only with no IPv6 in use. You want to use IPv6, but your ISP is not guaranteeing you a static assignment (they use prefix delegation which means the IPv6 space might change unexpectedly). That's going to be an issue unless you use both ULA and GUA IPv6 addresses. My post also assumed that your Active Directory domain was never going to be accessed from outside. Sounds like that is not what you intend as you mentioned somewhere up above about using some type of home automation with LDAP authentication I believe (unless I'm confusing this thread with another one). Pretty much what I am going to. Every guide that I have read says not to DISABLE the IPv6 on a DC. I am going to leave it at its default settings and let pfSense take care of it. Same for DHCPv4 - going to only do DNS on AD/DS and I am guessing that pfSense is RESOLVER with the FORWARDING option turned on. I would also need a Domain Override setup to point to AD/DS name and IPv4 address as well. Still trying to grasp the REV LOOKUP (setup in pfSense) thing and the HOST OVERRIDE too. The LDAP stuff that I want to do is not really for Home Automation, per se. I do have HomeAssisitant - what I want to do is sign-ins to the various parts with LDAP credentials so that I do not have to keep up with (currently 22) separate login accounts. All of that stuff is 'inside' my pfSense Firewall - only Alexa and Google can access from outside and their app. I got that working, and hoping that I do not have to go through that again. WHEW!!!

I tried and I tried...it's my ISP that's keeping me in the dark,,,their static IPv6 on the Fast5688w doesn't appear to allow pfSense LAN to communicate with WAN so RA cannot give out ULA's...

@mauropc ???? DHCPv6-PD is the normal way for ISPs to provide IPv6 to home users. You get an IPv6 address for your WAN interface and a prefix with at a minimum 18.4 billion, billion addresses and probably a lot more. Maybe you can describe what you're trying to do and problems you're having.

@Gertjan Yeah i clicked submit then noticed my screenshot error (took it while testing) and then had a server issue at work so had to stop "playing". Thats really helpful info and gives me something to work on, i'm a simple man of PPPoE so this is a new config type for me so it's all weird and wonderful.

I occurred to me that I might have some weird config since I was importing config from a chain of older routers so who knows what might have been lurking in that XML. So I did a factory reset on the 6100 and only set the needed things. Same problem. At this point, if someone had a procedure to downgrade the 6100 to 22.5, I would absolutely do that right now.

@catonic said in 2.4.4 ICMPv6 Firewall Rules?: because ICMPv6 is not an option on the drop-down Sure it is.. What do you think ICMP is when you select IPv6? [image: 1695465961105-icmpv6.jpg] Here created a test rule [23.05.1-RELEASE][admin@sg4860.local.lan]/root: cat /tmp/rules.debug | grep "test icmpv6" pass in quick on $TEST inet6 proto ipv6-icmp from any to any ridentifier 1695465595 keep state label "USER_RULE: test icmpv6" label "id:1695465595" [23.05.1-RELEASE][admin@sg4860.local.lan]/root This thread is 3 some years old - if you are having a problem, it would be best if you actually give details of what your trying to accomplish, how and what you have done to test it. There are also hidden rules that allow some icmpv6 # Allow only bare essential icmpv6 packets (NS, NA, and RA, echoreq, echorep) pass out quick inet6 proto ipv6-icmp from fe80::/10 to fe80::/10 icmp6-type {129,133,134,135,136} ridentifier 1000000108 keep state pass out quick inet6 proto ipv6-icmp from fe80::/10 to ff02::/16 icmp6-type {129,133,134,135,136} ridentifier 1000000109 keep state pass in quick inet6 proto ipv6-icmp from fe80::/10 to fe80::/10 icmp6-type {128,133,134,135,136} ridentifier 1000000110 keep state pass in quick inet6 proto ipv6-icmp from ff02::/16 to fe80::/10 icmp6-type {128,133,134,135,136} ridentifier 1000000111 keep state pass in quick inet6 proto ipv6-icmp from fe80::/10 to ff02::/16 icmp6-type {128,133,134,135,136} ridentifier 1000000112 keep state pass in quick inet6 proto ipv6-icmp from :: to ff02::/16 icmp6-type {128,133,134,135,136} ridentifier 1000000113 keep state Here I created a icmpv6 echo request rule, then sent some ipv6 pings.. [image: 1695466455246-echreq.jpg] And the counter goes up.

Just to close this out... To avoid any issues at the next upgrade I backed out the two changes in the patch and uninstalled the dhcpleases6 package. Then I added a new gateway on my external router that points to the hyper-v router's ipv6 address on its WAN side (the external router's LAN side), and added a static route to direct the delegated prefix subnet to that gateway. This configuration also works to allow IPv6 to work from the internal hyper-v router's LAN side. These two configuration items will be easy to back out at upgrade, assuming the issue is addressed in the next release.

@kiokoman said in HE Tunnelbroker: but the most important thing of all is that they give you a t-shirt if you became a SAGE That's certainly sage advice!

So nobody has any clue on how you can achieve individual interface assignment?