@jknott said in Just flipped from Spectrum to FiOS in NYC and have IPv6 out of the box FINALLY: While they provide a global WAN IP, it's not used for routing. Same here. That is why I think using one part of the prefix for WAN wouldn't be a technical problem, just waste of one /64.

@jknott Because GUA with a dynamic prefix is problematic, especially for hosts that don't get notified that the prefix has changed. So for now, only pfSense has to know for its WAN interface. That does work better, as long as pfSense is the first router.

@lolo54000 said in Ipv6 configured but unable to ping internet: In my ovh account i have 6 physical server and each have it's own ipv4 and it's own ipv6 /64 ipv6 To have a router in front, you would need: an IPv6 for the router WAN an IPv4 for the router WAN OVH to route your other IP addresses to those IPs your servers to use your router LAN IPv4/IPv6 as their gateway It sounds like they are simply not set up to handle a router, like you're asking for.

@casperghst42-real-one working here on a 2.6 [image: 1666540604231-workshere.jpg] You can't just leave ::1000 and :2000 You have to set the full range.. Those are just place holders.. That range is quite large 2a06:4004:1234:1:: to 2a06:4004:1234:1:ffff:ffff:ffff:ffff Maybe you want to hand out 2a06:4004:1234:1:42::1000 to 2a06:4004:1234:1:42:2000 so those ::1000 to ::2000 are just place holders for the actual IPs that could be handed out in your selected range. So you have to be specific on your actual range you want to use.

@mariog Thanks for the link. I'll keep an eye on this.

@cyth The gateway is part of the basic RA. The DNS server is an optional part of it and NTP server would require stateless DHCPv6. If needed, you could still rely on IPv4 for those too. However, using DHCPv6 for device addresses will fail for Android devices. Unmanaged is fine, unless you need stateless DHCPv6. The prefix for the alias is the first 56 bits of the addresses (assuming /56).

Like @nogbadthebad I've : [image: 1664873716247-ee3c2974-942b-413f-86ef-40816c315c2d-image.png] and added all the devices that I wanted to give a DHCP static IPv6 lease, like @NogBadTheBad Apple devices play very well with this. Zero issues for the last ... decade or so ?! ( I never had to use an Android based device in my life ) Even if the DUID are not added to the DHCPv6 static mappings list, it works well, an Ipv6 from the pool is used.

@jknott [image: 1664864944764-99a04cc3-fb1d-4f02-b4c7-cff09faa9eb0-image.png] No. Time Source Destination Protocol Length Info 6370 183.350531899 fe80::208:a2ff:fe12:49f2 ff02::1 ICMPv6 198 Router Advertisement from 00:08:a2:12:49:f2 29679 664.793636676 fe80::208:a2ff:fe12:49f2 ff02::1 ICMPv6 198 Router Advertisement from 00:08:a2:12:49:f2 32056 1034.144777006 fe80::208:a2ff:fe12:49f2 ff02::1 ICMPv6 198 Router Advertisement from 00:08:a2:12:49:f2

@mrsunfire I just upgraded to 2.6 and this is STILL an issue....

@mikev7896 Thanks. The setting you recommend was set. I don't recall setting it. Maybe in CE 2.6.0 it's a default? More things to learn...RDNSS, etc. Sigh.

@jknott I went for the nuclear option and rebooted pfSense and it's working fine now. [image: 1664639933263-5293d4c1-c90f-469b-a961-d55af208eeec-image.png]

@mariatech Maybe this will be helpful luckman212/assign-gua-from-iapd - GitHub

@ddbnj I'm on FIOS too (NYC) and spent just about the entire week messing around with and learning the ins and outs of Verizon's implementation. There are definitely some sharp edges but I'm pretty happy now with the way things are working. You might want to check out my helper script to assign a routable IP (GUA) to your WAN from one of the delegated prefix subnets. Link below luckman212/assign-gua-from-iapd - GitHub

I realized the problem was my bridge so I am in the middle of a complete redesign of my network. Will post back when I know more. Hopefully the family wont object too much to the down time.

@johnpoz said in odd ipv6 routing issue: Been in the business for some 30 years, before there was even switches. So, you're a newcomer. I've been in the LAN business since early 1978, before there was Ethernet or IP. It was on the Air Canada reservation system, where the LAN used time division multiplexing over coax @ 2 Mb or triaxial cable @ 8 Mb. I started in telecom in May 1972.

@roycethebiker Did you select 56 for the prefix size?

Looks like a bug has been filed by the dev team.