Hello,
I am experiencing this on 6.8, fully syspatched.
root@R1():~ # uname -a
OpenBSD R1 6.8 GENERIC.MP#4 amd64
The problem is that R1 sends updates with MED set to 0 even though I expect
it not to be. Upon reviewing a tcpdump pcap taken at R2, the MED attribute
is not even included in said upd
On Thu, Jan 28, 2021 at 12:41:29PM +0100, open...@kene.nu wrote:
> Hello,
>
> I am experiencing this on 6.8, fully syspatched.
>
> root@R1():~ # uname -a
> OpenBSD R1 6.8 GENERIC.MP#4 amd64
>
> The problem is that R1 sends updates with MED set to 0 even though I expect
> it not to be. Upon revie
In my case MED is changed with + on every eBGP hop. I use it to
calculate the total MED over several hops to decide the best path from a
latency point of view.
My intention with listing the advertised prefix from R1 was to show that
there is a MED present. As per the tcpdump I did, the MED attribu
On Thu, Jan 28, 2021 at 02:51:33PM +0100, open...@kene.nu wrote:
> In my case MED is changed with + on every eBGP hop. I use it to
> calculate the total MED over several hops to decide the best path from a
> latency point of view.
>
> My intention with listing the advertised prefix from R1 was to
Hello Claudio,
Thank you for the clarification. Your suggestion works splendidly.
On Thu, Jan 28, 2021 at 3:12 PM Claudio Jeker
wrote:
> On Thu, Jan 28, 2021 at 02:51:33PM +0100, open...@kene.nu wrote:
> > In my case MED is changed with + on every eBGP hop. I use it to
> > calculate the total M
5 matches
Mail list logo
