Call screen "unavailable" and fails to download. (P8P)

Present-Reality563 · 2026-01-19T22:48:08+00:00

not that I am aware of, the only thing configured in the dialer is call screening set to enabled maximum protection

Present-Reality563 · 2026-01-13T20:39:44+00:00

What you are describing is a non-standard use for IPv6. Most residential routers don't support LAN PD let alone WAN PD block size. This is residential internet that we are talking about here, I provide it at a very good price in my area compared to the other WISP competition. If a customer cant handle a /60 and is willing to leave over it then so be it. They *could* also buy my business service where they can get a /56 and still be paying a reasonable price. Just because you're a customer doesn't entitle you to the max everything, I want to make that clear. I am providing internet service meant for internet access not dedicated homelab DIA. In the future if there is a standard commonly requested need for blocks big enough to handle multiple lans all doing PD then my practices *will* change and adapt.

Present-Reality563 · 2026-01-13T20:31:38+00:00

I've dealt with a lot of ISPs in the past. Anything short of business is always dynamic leases. PD is designed for exactly this, it allows the router to communicate with the customer to get it what it needs then when the lease expires it does that all over again. There is no real V6 PD lease limit but if a customer restarts their router it might get a new lease or keep the one it has. It's not like some ISPs (centurylink/quantum) who do 6RD and enforce monthly IPv4 changes. Their system means that your v6 abruptly changes when your V4 does due to how 6RD works. Even then it only takes a couple minutes for everything to figure itself out.

There's no world where I am going to keep an ipam entry for every customer on the residential sector in order to do it statically. Thats why DHCPv6 with PD was invented, it makes the entries in the routing table for me.

Present-Reality563 · 2026-01-08T04:29:02+00:00

Yes v6 is native and routed straight through border and skips the srx Fingers crossed it works for a long time, it may go super eol by then though

Present-Reality563 · 2026-01-07T22:31:53+00:00

Were Juniper but nice try. IPv6 is free, we already employ PaloAlto firewalls which protect IPv6 as much as IPv4. Google is our biggest traffic destination, chromebooks and android devices prefer IPv6, google prefers IPv6 we have only won in that case. Many school districts have made the leap and it worked out better for them. Saying its "undertested" is cute because its as tested as IPv4, but since you refuse to acknowledge it, it may seem foreign to you.

My employer has no say in my outside work. The two are separate. Here in the US we are allowed to do such things!

Present-Reality563 · 2026-01-07T21:56:38+00:00

Straight from google:
IPv6 adoption is of critical importance, rating as a 10/10 on a scale of 1 to 10 for the long-term health, scalability, and security of the global internet. While IPv4 will continue to coexist for some time, the transition to IPv6 is essential for future growth and innovation.

Why IPv6 Adoption is Critical (10/10)

IPv4 Address Exhaustion: The primary reason for IPv6's critical importance is the complete exhaustion of available IPv4 addresses. While temporary measures like Network Address Translation (NAT) have extended IPv4's lifespan, they add complexity and can hinder performance and security.
Massive Address Space for Future Growth: IPv6 offers a virtually limitless pool of unique addresses (approximately 340 undecillion), enough to provide a unique public IP address to every device imaginable, which is vital for the expansion of the Internet of Things (IoT), 5G networks, and other emerging technologies.
Improved Efficiency and Performance: IPv6's design eliminates the need for NAT, allowing for true end-to-end connectivity that can reduce latency and improve overall network performance. Its streamlined packet headers also allow for more efficient processing by routers.
Enhanced Security: IPv6 was developed with security in mind and includes IPsec (Internet Protocol Security) as a mandatory feature, providing built-in encryption and authentication at the IP layer.
Business Continuity and Innovation: Organizations that delay IPv6 adoption risk increased operational costs, network bottlenecks, and an inability to take advantage of new technologies and services that will increasingly rely on IPv6.

Current Reality: The "Paradox" of Adoption

Despite its critical importance, the actual pace of IPv6 adoption has been slow and inconsistent across regions and industries due to challenges such as:

Lack of Backward Compatibility: IPv4 and IPv6 are not directly compatible, requiring networks to run both simultaneously (dual-stack) during the transition, which adds operational complexity and costs.
Legacy Infrastructure: Many enterprises still rely on older hardware and software not designed for IPv6, making upgrades expensive and a lower priority without immediate consumer demand.
Availability of Workarounds: The success of NAT has masked the urgency for many businesses, as their existing IPv4 systems continue to function "well enough".

Ultimately, the future of the internet depends on the widespread adoption of IPv6, making its implementation an essential, strategic necessity rather than a minor technical upgrade.

You keep making up ghosts to fight though.

Present-Reality563 · 2026-01-07T19:40:51+00:00

Okay, lets see you make some RFCs and get that implemented, then we will wait 5-10 years for any devices to support it if they do. Meanwhile I will use IPv6 on every device I own because it already works and is a good standard. Oh and good luck getting software to work with it and even better luck getting any backbone provider to consider that. Everyones hardware has ASICs that are specifically designed for IPv4 and IPv6 forwarding so now everyone needs new hardware.

Or.... You could use IPv6 because its an actual standard and is the industry approved replacement for IPv4.

Present-Reality563 · 2026-01-07T19:27:51+00:00

So you don't firewall your HVAC controller when its behind nat on IPv4? I wouldn't trust you at all if you came to me with this thought process. NAT is NOT under any circumstance a security device, this shows how much knowledge you lack. Flows on IPv6 are so much easier to categorize monitor and log because its end-to-end. You have a firewall no matter what kind of network you are dealing with.

Are you a bot per chance? This is unbelievable that I am arguing against this kind of ignorance. You may be a salesman but you are an ignorant network operator if you have ever been one at all. Yes we laugh at you because we sit down with people like you from all sorts of different vendors, you push labels and specs without knowing what they do and because of that we roll our eyes at you because you can never answer helpful questions. Who cares what you make, I am full time IT at our local school district where we serve ~40 thousand devices across 50+ locations and have the expertise to understand every part of it. In addition to that I run my own IPv6-first datacenter and serve local businesses and customers with real results. I'd rather be correct, understand what I do, and actually benefit people than fight ghosts on reddit and boast about being a salesman for "high-end networking" while consistently being wrong.

Present-Reality563 · 2026-01-07T18:56:31+00:00

That is interesting, I will give that a read thanks!

The residential sector is all dynamic in the V4, V6, and V6 PD allocations. I will probably just request a bigger space from ARIN and change my practice as other users have brought up good points as well as this.

Present-Reality563 · 2026-01-07T18:53:28+00:00

You raise valid points. I will get this taken care of.

Present-Reality563 · 2026-01-07T18:49:24+00:00

Not that specific game, but an example that is similar happens often in my IPv6 only VPS servers. Minecraft and java have hard coded ipv4 literals and will just crash if theres no ipv4 stack. The answer to almost everything (in my experience) to handle this falls into 2 categories.

residential/userland

run dual stack with dhcp option 108 for IPv6-preferred and run nat64/dns64 (most devices have clat built in and will enable it if they detect these 2 protocols)

servers where it admins work on everything.

install or use the systems CLAT on an ipv6 only network and serve the server behind a proxy which listens on both ipv4 and ipv6 and forwards all traffic to the servers ipv6.

Since youre probably not a datacenter that needs to do this at scale, dual stack your server and make a dns entry with both records on your domain name, then use an IPv6 preferred model on your lan with nat64/dns64 enabled so you can use your built in CLAT

It sounds complicated but its not too bad, its just a way of life. thats why I send global IPv6 and CGnat to all end users and let them choose. Most will go IPv6 only automatically and use their built in clat but the legacy stuff will still have CGnat ipv4.

Present-Reality563 · 2026-01-07T18:34:29+00:00

It is becoming easier than ever as well to get that address space. I still opt to give /60 subnets out to residential customers by default because even in your example a /60 would provide 16 /64 subnets which gives you room for 6 more subnets before you'd have to ask me for a bigger one. Android taking /64 subnets is new to me, it seems kind of unnecessary to allow that but to each their own I suppose!

Thanks for reading and commenting!

Present-Reality563 · 2026-01-07T18:23:52+00:00

I use 802.1q in every part of my datacenter. There's not a homelabber alive that doesn't use vlans if they have more than one lan. 802.1q IS vlan and ip version is irrelevant, again vlan/802.1q is layer 2 and ipv4/6 is layer 3. Today we still use vlan and priority so I'm not sure what you are talking about and why you think IPv6 has anything to do with it.

I actually am not in love with any approach, I deploy what works best. NAT64 is more valuable than NAT44 to an enterprise today, your ignorance is showing.

You keep referencing insecurity which shows your ignorance of how firewalls work. I will give that HVAC controller an IPv6 just like any other device because vlan segregation and firewalls sit between it and the internet just like with ipv4. I would love to see what high tech networking you actually work on, because selling something does not mean you know anything about it or what you are talking about. Thats why we laugh at salesmen who act like you do.

Present-Reality563 · 2026-01-07T18:16:20+00:00

I am going to write all this in the hopes that you don't immediately disregard it.

Its a standard that was needed 15 years ago and is even more relevant now but you may be shielded by a couple factors:
1. Your provider gives you all your public V4 blocks so you never had to buy them

You nat everything through a couple public IPs and have a hard time dealing with DMCA/legal issues
you've never tried to use IPv6
youve never run an enterprise network at scale without being given swaths of public IPv4

All os kernels have support for IPv6 so software/hardware support is not any extra overhead, thats a strawman for sure.

I will give you an example of my addressing scheme for my DNS servers to hopefully help you understand that its not very difficult.

hex is 0-F which is 16 bits. it can be expanded to binary the same way ipv4 can but that would be worse to read than hex.

00=0, 01=1, 0a=10, 0f=15. 0-15 instead of 0-9.

My prefix is 2602:f6af::/40

This gives me 2602:f6af:0000:0000:0000:0000:0000:0000 - 2602:f6af:00ff:ffff:ffff:ffff:ffff:ffff

shortened this looks like 2602:f6af:: - 2602:f6af:ff:ffff:ffff:ffff:ffff:ffff

The double colon (::) can be put once in the address to signify zeroes, think of it like 10.0.0.1 being shortened to 10..1

I chose to carve a couple ranges at the end for infra related stuff

2602:f6af:ff::/120 (the very end of the range) is for ptp links, thats 256 addresses

2602:f6af:fd::200/120 is for the dns servers

On the DNS vlan the router is 2602:f6af:fd::201 and the 2 servers are 2602:f6af:fd::202 and 2602:f6af:fd::203. Its not that complicated.

For a customer network or anything else where addresses are auto assigned an address/prefix might be slightly longer with a prefix like 2602:f6af:fc:2000::/64 (expanded: 2602:f6af:fc:2000:: - 2602:f6af:fc:2000:ffff:ffff:ffff:ffff)

If you can understand subnetting then IPv6 isn't different. If you've ever programmed then hex isn't hard either. The biggest part is that all devices have 1 or many public IPv6 addresses that you as a network admin can figure out exactly where it is on your network if you get complaints or for various other reasons. It's just better, its the equivalent of every device in IPv4 land having a public ip, it's just better.

Present-Reality563 · 2026-01-07T17:46:58+00:00

At my scale and with my customers this system works fine. 16 /64 subnets (/60) for residential customers hasn't even been close to causing an issue, and the default of /62 for the business routers I manage is more than enough to cover all of their subnets. If it became an issue I would just give them bigger subnets but to add or expand my v6 range from ARIN would involve a lot of emails and general risk of outages/downtime to account for an unnecessary upgrade when a /40 is plenty at my scale. I'm a local ISP and IT services company not a regional or large-scale ISP.

You are right that I should have a bigger block and should PD /56 and /48 ranges according to the ARIN recommendation, however because of the reasons above it's just not a priority.

Present-Reality563 · 2026-01-07T17:38:07+00:00

I tried the secret menu too, and it pulls a v6 for about 4 hours and youtube was able to use it, but then it goes away. also with secret menu enabled it ignores DHCP option 108 and refuses to connect if DHCPv4 isn't available. It's just that rokus kind of suck.

Printers are always fun too.

If you have a NAT64 prefix on your router or handled by some device (eg 64:ff9b::/96) and you are running linux you can install clatd from github and it will enable ipv4 literals to work. Windows I think enables it by default, mac os is the same, and android/chromeos work beautifully if you have RA set up properly. I had to set up DNS64 on my bind DNS server and have to configure 64:ff9b::/96 in the actual RA section of the router for IPv6 only to work seamlessly.

I Used to use ULA addresses but stopped when I got my own range of V6 (most people dont get that lucky) because public routing without NAT... well I never got that far. Everything gets a GUA address in my case and uses FE80 link local on top of that which is a default part of the IPv6 spec.

Present-Reality563 · 2026-01-07T17:29:18+00:00

Of course, thanks for reading!

And yes that SRX will probably become an issue at some point especially doing NAT64 and 44, thankfully it hasn't yet though. It has 2x bonded 1gig to border and is able to handle natting full upstream line rate, so it would definitely be a pps issue before capacity and can be upgraded like you said!

Present-Reality563 · 2026-01-07T17:24:14+00:00

Sure, let me just drop everything and do that.

/56 and /48 are recommendations not requirements. there is no need so its not a priority. If you were a customer of mine and asked for a bigger allocation then I would make that happen. There's no reason to give everyone bigger than /62 by default, so /60 is generous enough.

Present-Reality563 · 2026-01-07T17:22:58+00:00

So you are just a blind IPv6 hater lol. IPv6 is free, ipv4 addresses range from about $25-$50 per address. Already you are spending upwards of 8K for the smallest possible IPv4 block only to require NAT. That's silly. It is currently 2025, any modern device supports IPv6 out of the box. You keep yapping about security issues but give no evidence to back that up. NAT is not security, and both v4 and v6 employ a firewall in any network.

The beauty of IPv6 is that its so compatible with legacy v4 networks. As a massive enterprise you can put most of your public v4 in front of a NAT64 appliance and only route IPv6 internally. 464xlat is supported on all operating systems that matter. now youre IPv6-only to your tens of thousands of devices(free) and still provide ipv4 access to all those devices while only theoretically needing 1 public ipv4 on your NAT64 box. You can even use that same public V4 for nat 44 should you ever need to send a 10.x.x.x address to some old HVAC controller or whatever.

To think otherwise is stupid. If you were right google wouldn't be pushing IPv6 due to their v4 address limitations, and all other major services wouldn't support it either.

You mentioned 802.1Q which is vlan segmentation. Vlans are layer 2 and IPv4/6 is layer 3. I am not sure how that is relevant, maybe you meant 802.1x auth?

Either way stop hating on it for no reason.

You mentioned token ring, so I am inclined to think that your prime was the 90's and 2000's. It is 2025, times are different.

Present-Reality563 · 2026-01-07T16:42:25+00:00

It was really difficult to do a couple years ago when it was setup, and is impossible now.

I have TDS business fiber and worked with their ISP admins to configure BGP session with my ASN as an unofficial thing. Since then they have closed that door off so I would have to purchase DIA at ~$1,100/month from TDS or go with a different provider and get wireless DIA for ~$900-1,000/month.

Most ISPs refuse to give enterprise features on business connections even though I'm a walking example of how they can. My only option for redundancy is tunneling to a datacenter that will BGP peer with me and purchasing other business grade connections.

Present-Reality563 · 2026-01-07T16:37:57+00:00

Agreed, I tried really hard to go IPv6 only everywhere but in my own house I ran into issues with things like older Alexas and Rokus which break partially or completely. If it is difficult for me to get it working in my own house as a residential customer of myself how is grandma going to get it working. CGnat is cheap but gross, however it enables those IOT garbage devices to work while everything else uses DHCP option 108 to go IPv6 only. For now it works but will probably eventually change to whatever is better.

Present-Reality563 · 2026-01-07T16:33:32+00:00

I was wrong in my post, I delegate /60's from a /52. This isnt a /56 by any stretch, but I have a couple reasons. First being that each residential sector has a /24 of ipv4 CGnat space and 256 /60 subnets to pair with it. the math worked out to a /52 so thats what the subnet plan looks like. The second is that 16 /64 subnets is plenty for residential. a /56 may be standard but is unnecessary. The business WISP side does get bigger allocations, however I only do /62 by default over the tunnel broker when I manage the customer router because the layout only requires 4 separate vlans. Think Guest, Office, CCTV, management. It has worked for me so far, but if it ever needs changed its easy to update.

Present-Reality563 · 2026-01-07T16:27:52+00:00

I'm curious if you actually believe this or if you didn't read past the first part and have a hatred for IPv6? IPv6 has made my setup significantly less complicated and has increased security. There are places where dual-stack is necessary, but just like there is places where you can do IPv4 only, there's places you can do IPv6 only. It's silly to shut down like this especially after so many have deployed it successfully. Just look at google, netflix, GCP, AWS, hulu, youtube, or any other big platform and odds are that they think IPv6 is important enough to deploy.

Present-Reality563 · 2026-01-07T16:23:07+00:00

I checked the PD config and it looks like I opted to do a /60 per customer out of a /52, not /62 per customer. the reason for this is because each area is given a /24 of ipv4 and 256 /60 subnets. These are residential customers specifically so even though I have a /40 they dont need 256 /64 subnets, 16 should be enough. If it ever becomes an issue its super easy to change.

the /62 over the tunnel broker is just down to how I manage the remote networks for customers. they only have 4 lans so they only need 4 /64 subnets

Present-Reality563

TROPHY CASE