11 Apr
2014
11 Apr
'14
12:02 p.m.
On Fri, Apr 11, 2014 at 8:32 AM, Bart Kus <me(a)bartk.us> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On 4/11/2014 8:16 AM, Don Fanning wrote:
Right, I can see in Hamwan's case if you were closer to Seattle you would
route through Seattle and if you were closer to Corvallis, you'd route
there. But in the larger scale of things with 44net, are you proposing
that anycast be utilized throughout 44net?
On Thu, Apr 10, 2014 at 11:29 PM, Bart Kus
<me(a)bartk.us> wrote:
Can you make the database change to configure 44.24.221.1 as the gateway
Can you describe what you would accomplish by utilizing anycast in the
44net case? I'm not seeing a viable end goal in this direction.
It allows our microwave network to remain connected to the rest of AMPRnet
as long as we have at least 1 ISP that isn't dead. The microwave network
peers with the Internet at 2 different points at present, but more points
will come in the future. It's a robustness improvement in the face of
partial failures, like in a natural disaster when an ISP's fiber gets torn
or their building collapses.
> for
> 44.24.240.0/20?
>
> Why don't you just use another ipv4 address as the tunnel endpoint ?
You can even use the /30 you are using to BGP with your upstream isp
since those will surely be in a different subnet.
The goal is anycast. My ISP's local subnet is not portable to my other
ISP,
and so on.