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, th
> 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
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 service
information by a person other than intended recipient is unauthorized and may be illegal.
From: NANOG on behalf of Bill Woodcock
Sent: Saturday, February 24, 2024 1:09 AM
To: Ask Bjørn Hansen
Cc: nanog@nanog.org
Subject: Re: TFTP over anycast
CAUTION: This email is from an external source
On Tue, Feb 27, 2024 at 10:02 AM Javier Gutierrez
wrote:
> My design is very simplistic, I have 2 sets of firewalls that I
> will have advertising a /32 unicast to the network at each
> location and it will have a TFTP server behind each firewall.
Hi Javier,
That sounds straightforward to me wit
semination or use of this information by a person other than intended
recipient is unauthorized and may be illegal.
From: NANOG on behalf of
Bill Woodcock
Sent: Saturday, February 24, 2024 1:09 AM
To: Ask Bjørn Hansen
Cc: nanog@nanog.org
Subject: Re: TFTP
On Feb 22, 2024, at 10:47, Javier Gutierrez wrote:Hi, I'm working on some DR design and we want to not only have this site as a DR but also performing some active/active for some of the services we hosts and I was wondering if someone had some experience with using anycast for TFTP or DHCP servi
The system Ask is describing is the traditional method of using anycast to
geographically load-balance long-lived flows. The first time I did that was
with FTP servers in Berkeley and Santa Cruz, in 1989.
I did a bigger system, also load balancing FTP servers for Oracle, their
public-facing d
> On Feb 23, 2024, at 20:32, William Herrin wrote:
>
>> The relay server `dhcplb` could, maybe, help in that scenario
>> (dhcplb runs on the anycast IP, the “real” DHCP servers on
>> unicast IPs behind dhcplb).
>
> Although they used the word "anycast", they're just load balancing.
The idea i
On Fri, Feb 23, 2024 at 6:34 PM Ask Bjørn Hansen wrote:
> The relay server `dhcplb` could, maybe, help in that scenario
> (dhcplb runs on the anycast IP, the “real” DHCP servers on
> unicast IPs behind dhcplb).
Although they used the word "anycast", they're just load balancing.
Devices behind a l
> On Feb 22, 2024, at 12:52, Thomas Mieslinger wrote:
>
> It becomes tricky for DHCP if a location has the same cost to more than
> one anycast Node. For this case we have setup a DHCP nodes in two
> datacenters using different local-preferences to simulate a failover
> active/passive setup.
Th
Others have addressed some of the issues, but one easy win for DHCP (which is
otherwise a PITA to make redundany in *any* way) is to (a) not block ICMP
anywhere, including on the client devices, and (b) have the DHCP ping before
assignment. That’s not always on by default, and it’ll eliminate ~
I do NTP, DHCP, TFTP, DNS, HTTP anycast.
NTP, DNS and HTTP with ECMP, TFTP and DHCP as active/active on a per
Datacenter Basis.
These are small Datacenters with less than 50k Servers each.
In every datacenter an anycast node is active and the router just
chooses the shortest path.
It becomes t
On Thu, Feb 22, 2024 at 10:47 AM Javier Gutierrez
wrote:
> I was wondering if someone had some experience with using anycast for TFTP
> or DHCP services?
Hi Javier,
Anycast for TFTP is more or less the same as anycast for TCP-based
protocols: it has corner cases which fail and fail hard, but o
14 matches
Mail list logo