NANOG Mailing List

The North American Network Operators' Group discusses fundamental Internet infrastructure issues such as routing, IP address allocation, and containing malicious activity.

List Archives

Latest Posts

Re: Frontier IPv6 Prefix Delegation - AS5650 Tom Beecher via NANOG (Aug 06)
Charter gives out a /56 via PD on normal residential service. It's possible
that /64 is their default, but sending a /56 prefix hint works just fine.
Has for years.

Re: Frontier IPv6 Prefix Delegation - AS5650 Christopher Morrow via NANOG (Aug 06)
<snip>

it wasn't obvious that Chris had attempted PD though?

Re: Frontier IPv6 Prefix Delegation - AS5650 Gary Buhrmaster via NANOG (Aug 06)
Probably not unless you move to business service.
Although it does not hurt (well, your wasted time)
to try to convince them to change.

For residential, it seems most ISPs believe RFC6177
is more of an idea than a firm suggestion[0], and if you
want a /56, you need to upgrade to being what they
consider a business site, and, of course, pay more.

Comcast does offer a /60 for their residential
customers, but if you want a /56 (or more), it is...

Re: Frontier IPv6 Prefix Delegation - AS5650 Marco Moock via NANOG (Aug 06)
Am 06.08.26 um 16:28 schrieb Chris Riling via NANOG:

http://stats.labs.apnic.net/ipv6/AS5650?c=US&p=1&v=1&w=30&x=1

It seems they started the rollout in September.

Re: Frontier IPv6 Prefix Delegation - AS5650 Chris Riling via NANOG (Aug 06)
Similar situation here... mine backhauls about 120 miles, but at least I
started getting some IPv6, so, progress, I guess. I just wish they would do
-something- with best practice... haha... as you said, still the best
option here.

Chris

Re: Frontier IPv6 Prefix Delegation - AS5650 Tim Burke via NANOG (Aug 06)
Good luck…

I guess, despite being against best practices, a /64 is better than nothing… especially considering “most” home users
really only need a /64. The BNG we are on (backhauled from 200 miles away in a completely different metro area,
breaking geolocation, adding significant latency just to get to someone in the same town, etc.) doesn’t even have an
IPv6 address period, let alone DHCPv6-PD. I’ve even tried filing an FCC...

Re: Frontier IPv6 Prefix Delegation - AS5650 Chris Riling via NANOG (Aug 06)
Not via email, at least on a residential line... crappy AI chatbot, or
phone support / social media teams that don't know what subnets are. Hoping
to come across the right contact here :)

On Thu, Aug 6, 2026 at 10:11 AM Marco Moock via NANOG <nanog () lists nanog org>
wrote:

Re: Frontier IPv6 Prefix Delegation - AS5650 Marco Moock via NANOG (Aug 06)
Am 06.08.26 um 14:43 schrieb Chris Riling via NANOG:

Do you have a support address?

They seem to have IPv6 route propagation issues too, AS3320 doesn't know
their prefixes.

Frontier IPv6 Prefix Delegation - AS5650 Chris Riling via NANOG (Aug 06)
Hi,

Anyone here have a knowledgeable contact at Frontier? I’m on a residential
fiber connection and recently started getting a v6 delegation (yay!) but
they’re only handing out /64s. Obviously this doesn’t allow for proper
subnetting, and forces me to use NPTv6 / ULA if I want to do things
“properly”, and devices essentially ignoring their v6 interface. This also
seems to be in conflict with RFC 6177 and seems to somewhat defeat the...

Re: how about a well-known DOWNGRADE BGP Community? (Was: RTBH Support Across the Industry) Saku Ytti via NANOG (Aug 05)
We ran this very config in production while we still had asr9k.

It is slightly confusing as 0, 1 and 2 on CLI are not same in Tomahawk, in HW they are well ordered. But in CLI
unconfigured 0 is worst, 1 is best and 2 is middle, so can be confusing if you debug in HW level to see where packets
are going.

++ytti
________________________________
Lähettäjä: Lukas Tribus <lukas () ltri eu>
Lähetetty: Wednesday, 05 August 2026 22:32:26...

Re: how about a well-known DOWNGRADE BGP Community? (Was: RTBH Support Across the Industry) Lukas Tribus via NANOG (Aug 05)
I am very glad this is possible on the 9k. Are you certain there are
no negative consequences moving the entire BE traffic into a fabric
priority queue (back-pressure, etc)?

The *transit* network is technically protected. But the incentive for
the *customer* network to actually announce the scavenger route is
gone.

If the transit network is injecting a scavenger route itself without
involving the customer, sure, then this makes sense for the...

Re: how about a well-known DOWNGRADE BGP Community? (Was: RTBH Support Across the Industry) Saku Ytti via NANOG (Aug 04)
Mind you, in your scenario, even without ASR9k priorities, the network
is protected.

DoS -> IngressPE -> Core1 -> Core2 -> ASR9k -> Victim

As the victim prefix has community, IngressPE sets the LE QoS bits.
Each hop egress side stops congesting the far end ingress side
Even if ASR9k congests the victim (which it shouldn't with the right
priority level), the rest of the core is protected, so the blast zone
is still just the...

Re: how about a well-known DOWNGRADE BGP Community? (Was: RTBH Support Across the Industry) Saku Ytti via NANOG (Aug 04)
I don't think this is true.

You set 'priority level 1' for NC+AF, 'priority level 2' for BE, and
leave LE unset on the ingress policy.

This sets the fabric priority, and VoQ will honor it.

Re: Recommendations for public-facing automated status page? Riley O via NANOG (Aug 04)
Depending on what you're after, there's a number of options.

There are very simple "turnkey" solutions like UptimeRobot and StatusCake that do periodic ping/traceroute from a
single location.

I stray from host-your-own stuff for monitoring (i.e. UptimeKuma) because you either host it in your network or at a
remote location (single origin).

Single origin pings may be good enough for public status page, but you'll be...

Re: Recommendations for public-facing automated status page? Andrew Langhorn via NANOG (Aug 04)
Atlassian bought statuspage a while ago, so it’s now Atlassian Statuspage.
You can see it in the wild at
https://status.digitalocean.com/. Incident.io is also increasingly popular,
too. Openstatus and cachet are popular OSS systems, but self-hosted.

If your SMS provider supports sending messages after being triggered by
webhook, which Amazon Pinpoint and Twilio do, then Statuspage and others
can be used with your own SMS provider.

More Lists

Dozens of other network security lists are archived at SecLists.Org.