Hello William!
An ARP Controller to compose a L2 Cluster solution seems a good Idea to a
begging...
(I would include ND)
I will try to think a bit on that...
Any suggestions are welcome.
Em qui., 1 de jul. de 2021 às 16:06, William Herrin
escreveu:
> On Thu, Jul 1, 2021 at 11:05 AM Douglas
Maybe a spine and leaf architecture could work for you.
You could install 1 server per leaf or more. I believe this could achieve
high-availability and load-balancing at layer 2.
There is a kind of layer 3 overlay, but for the hosts this is transparent and
it feels like a real pure
Douglas Fischer wrote:
Yes... It probably solves my issues on a v6 only world.
No, not at all.
I'm afraid you don't understand what your issues are.
At least, neither L2 or L3 anycast has anything to do with
high reliability because reachability to a server and
availability of the server
Not all have implemented it yet. But if you haven't. You were supposed to
implement some kind of robo calling mitigation plan (Or atleast certify
that you have one). At $dayjob we're fully deployed (inbound and outbound).
I received my first ever STIR/SHAKEN signed (iPhone Check mark, highly
Mark,
iputils-ping on linux seems to behave the same for quite some time...
[z@tyl][~] % host ns0
ns0.spirit.net.au has address 27.113.240.197
ns0.spirit.net.au has IPv6 address 2403:3600:8002::100
[z@tyl][~] % ping ns0
PING ns0(2403:3600:8002::100 (2403:3600:8002::100)) 56 data bytes
64
* mark@tinka.africa (Mark Tinka) [Fri 02 Jul 2021, 16:02 CEST]:
I just noticed (although it appears to have come in version 13.0) that
FreeBSD's "ping" app now defaults to IPv6, i.e., no need for ping6:
Yes, this broke some of my home network monitoring. Sadly there is no
'ping4' in the
Hello Masataka!
Yes... It probably solves my issues on a v6 only world.
But unfortunately, in this scenario there is IPv4 also, and to make me cry
alone in the bathroom there are some IPv4 only...
So, I will need to provide some solution that covers IPv4 also.
Em qui., 1 de jul. de 2021 às
Hi all.
I just noticed (although it appears to have come in version 13.0) that
FreeBSD's "ping" app now defaults to IPv6, i.e., no need for ping6:
https://www.freebsd.org/cgi/man.cgi?query=ping=8=html
Does anyone know whether other *nix systems are doing this now?
My Mac (Catalina) still
On 7/2/21 16:22, Niels Bakker wrote:
Yes, this broke some of my home network monitoring. Sadly there is no
'ping4' in the system, you have to add -4 to the commandline to return
to the common BSD behaviour.
This is a good point, as it's the same reason I discovered this today. A
Any suggestions for local purchase of a mpo fiber cleaner near equinix
London ld5?
Much appreciated
On 7/2/21 16:12, Patrick Cole wrote:
Mark,
iputils-ping on linux seems to behave the same for quite some time...
[z@tyl][~] % host ns0
ns0.spirit.net.au has address 27.113.240.197
ns0.spirit.net.au has IPv6 address 2403:3600:8002::100
[z@tyl][~] % ping ns0
PING ns0(2403:3600:8002::100
People who are actually interested in this subject are well advised to
read this thoroughly because it equally applies to SIP spam with a
system far less complex and far fewer gaping security holes as STIR.
https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-hu.pdf
Mike
On
I just noticed (although it appears to have come in version 13.0)
that FreeBSD's "ping" app now defaults to IPv6, i.e., no need for
ping6:
* ra...@psg.com (Randy Bush) [Fri 02 Jul 2021, 18:48 CEST]:
pola breakage. especially fun if you have tools which run on both
sides of the koolaid.
On
> On 2 Jul 2021, at 01:04, Douglas Fischer wrote:
>
> Answering suggestions in advance:
As others have pointed out, what you’re describing isn’t anycast, nor anything
directly to do with high availability.
There are multiple well-understood frameworks which can be used to do what
you’re
This is an automated weekly mailing describing the state of the Internet
Routing Table as seen from APNIC's router in Japan.
The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG
TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG.
Daily listings are sent to
> I just noticed (although it appears to have come in version 13.0) that
> FreeBSD's "ping" app now defaults to IPv6, i.e., no need for ping6:
pola breakage. especially fun if you have tools which run on both sides
of the koolaid.
randy
---
ra...@psg.com
`gpg --locate-external-keys
> Someone from please contact me offlist.
>
> Thanks.
>
>
You want to appear on their cart00ney site?
Regards
Fun part is that just because it's a telnyx number with a checkmark, it
doesn't mean the call came from Telnyx, just that the call came from a
carrier that gave the call attestation A. As the carrier, we can see who
signed the call (it's an x509 certificate, signed by the STI-PA, with
the
On 7/1/21 1:05 PM, Paul Timmins wrote:
On 7/1/21 3:53 PM, Keith Medcalf wrote:
And this is why this problem will not be solved. The "open relay" is making money from processing
the calls, and the end carrier is making money for terminating them. Until fine(s) -- hopefully millions of
19 matches
Mail list logo
