On Tue, Aug 10, 2021 at 2:39 AM Neale Ranns wrote
>
>
> Again: GCP does this. Calico for K8s (the most used K8s CNI plugin) does
> this. Its basically the direction Cloud is going in the generic.
>
>
>
> Ah well, that’s different, if all the cool kids are doing it, then it must
> be the right
From: Ed Warnicke
Date: Monday, 9 August 2021 at 16:16
To: Neale Ranns
Cc: otr...@employees.org , artem.glazyc...@xored.com
, vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] memif: failed: no source address for egress interface
On Mon, Aug 9, 2021 at 7:40 AM Neale Ranns
mailto:ne
On Mon, Aug 9, 2021 at 7:40 AM Neale Ranns wrote:
>
>
> i would argue the contrary, not subnetting (i.e. using /32) is not a valid
> approach to subnetting.
>
Again: GCP does this. Calico for K8s (the most used K8s CNI plugin) does
this. Its basically the direction Cloud is going in the gener
Neale,
/32s on interfaces that talk to other things are actually getting to be the
standard in Cloud. GCP uses /32s in their VMs exclusively. Calico uses
/32s on on Pod interfaces. Its a common use case.
Ed
On Mon, Aug 9, 2021 at 3:03 AM Neale Ranns wrote:
>
>
> Hi Artem,
>
>
>
> I think th
On 09/08/2021 10:15, "otr...@employees.org" wrote:
> I think that is telling you not to use /32 address on interface for which you
> expect there to be connected peers.
> From an IP networking perspective, if you want two peers to be connected on
> an interface, they need to be within the same
> I think that is telling you not to use /32 address on interface for which you
> expect there to be connected peers.
> From an IP networking perspective, if you want two peers to be connected on
> an interface, they need to be within the same subnet, so use a /31.
For p2p links there are actual
Hi Artem,
I think that is telling you not to use /32 address on interface for which you
expect there to be connected peers.
>From an IP networking perspective, if you want two peers to be connected on an
>interface, they need to be within the same subnet, so use a /31.
/neale
From: vpp-dev@l
