Re: TFTP over anycast

2024-04-06 Thread Saku Ytti
On Sat, 6 Apr 2024 at 12:00, Bill Woodcock wrote: > That’s been the normal way of doing it for some 35 years now. iBGP > advertise, or don’t advertise, the service address, which is attached to the > loopback, depending whether you’re ready to service traffic. If we are talking about eBGP,

Re: 2600:: No longer pings

2024-04-06 Thread Gaurav Kansal via NANOG
2409:: is replying the ICMPv6 request, in case anyone interested > On 6 Apr 2024, at 15:31, nanog@nanog.org wrote: > > It appears that 2600:: no longer responds to ICMP. > > $ mtr -rwc 1 2600:: > Start: 2024-04-06T10:53:41+0100 > HOST: metropolis Loss% >

Re: Netskrt - ISP-colo CDN

2024-04-06 Thread Tim Burke
I have been trying to get _away_ from caching appliances on our network — other than Google, we are able to pick up most of the stuff that otherwise would be cacheable via private peering; so it doesn’t make a whole lot of sense for us to have appliances in the datacenter taking up space,

Re: 2600:: No longer pings

2024-04-06 Thread Stephane Bortzmeyer
On Sat, Apr 06, 2024 at 06:19:57PM +0800, Soha Jin wrote a message of 50 lines which said: > I don't know what happed to 2600::, but 2a09:: and 2a11:: can be > used as alternatives. These are addresses of https://dns.sb/ running > by xTom. Very good DNS service, buy the way. But, although I

RE: 2600:: No longer pings

2024-04-06 Thread Soha Jin
I don't know what happed to 2600::, but 2a09:: and 2a11:: can be used as alternatives. These are addresses of https://dns.sb/ running by xTom. > -Original Message- > From: NANOG On Behalf Of Ben > Cartwright-Cox via NANOG > Sent: Saturday, April 6, 2024 6:01 PM > To: North American

2600:: No longer pings

2024-04-06 Thread Ben Cartwright-Cox via NANOG
It appears that 2600:: no longer responds to ICMP. $ mtr -rwc 1 2600:: Start: 2024-04-06T10:53:41+0100 HOST: metropolis Loss% 1.|-- lcy02.flat.b621.net 0.0% [...] 6.|-- ldn-b4-link.ip.twelve99.net 0.0% 7.|--

Re: TFTP over anycast

2024-04-06 Thread Bill Woodcock
> On Apr 6, 2024, at 10:30, Ray Bellis wrote: > On 27/02/2024 18:47, William Herrin wrote: >> Then I'd write a script to monitor the local tftp server and stop frr if it >> detects any problems with the tftp server. > There are other ways to achieve this without actually stopping the routing

Re: TFTP over anycast

2024-04-06 Thread Ray Bellis
On 27/02/2024 18:47, William Herrin wrote: Then I'd write a script to monitor the local tftp server and stop frr if it detects any problems with the tftp server. There are other ways to achieve this without actually stopping the routing daemon. We have DNS servers where the anycast