U

Visitor

 • 

2 Messages

Wednesday, May 3rd, 2023 2:55 AM

Closed

Can no longer get an /60 IPv6 address

I've had issues recently where all of a sudden I can no longer get a /60 IPv6 address. This has happened in the last couple of months, and we've checked to make sure we're sending a DHCP prefix hint yet we don't get anything back at all.


Tech support on the phone has gotten me nowhere as they don't understand what I need.

Setup:

Comcast Gateway with Bridge mode

pfSense Firewall

Houston, TX 77063 

Problem Solver

 • 

1.5K Messages

2 years ago

Looks like the /64 is all the pass out these days in my market too (midwest).  So, Index 0 on your WAN is all you get for your LAN subnet to work with as far as IPV6 goes.  Additional OPTx subnets will be IPV4 only.

At least that's the way it works here unless I've missed something.  Hinting for a /56 or /60 doesn't work.  Apparently, this ISP isn't interested in configurations other than one big slush pile subnet, which doesn't work for many of us.  Up until recently here, IPV6 was completely unreliable entirely, so I guess that's progress......

Visitor

 • 

2 Messages

@flatlander3​ However this wouldn't be in compliance with RFC6177, and it'd be pretty embarrassing if a $175B company can't follow basic standards.

Problem Solver

 • 

1.5K Messages

@user_907e05​ Yeah well.  It wasn't my idea, especially considering there are more IPV6 addresses than there are grains of sand. 

If enough people carp about it, perhaps that will change, but likely not.  Losing customers in competition areas may.

forum icon

New to the Community?

Start Here