On Tue, 5 Sep 2017 10:47:11 +0200 Martin Pieuchot wrote:
> On 04/09/17(Mon) 14:53, Gerhard Roth wrote:
> > Hi Martin,
> >
> >
> > On Mon, 4 Sep 2017 14:18:50 +0200 Martin Pieuchot wrote:
> > > On 04/09/17(Mon) 13:10, Gerhard Roth wrote:
> > > > Hi,
> > > >
> > > > I noticed a problem with the
On 04/09/17(Mon) 14:53, Gerhard Roth wrote:
> Hi Martin,
>
>
> On Mon, 4 Sep 2017 14:18:50 +0200 Martin Pieuchot wrote:
> > On 04/09/17(Mon) 13:10, Gerhard Roth wrote:
> > > Hi,
> > >
> > > I noticed a problem with the routing table that is easy to reproduce: put
> > > multiple IPs on the same
Hi Martin,
On Mon, 4 Sep 2017 14:18:50 +0200 Martin Pieuchot wrote:
> On 04/09/17(Mon) 13:10, Gerhard Roth wrote:
> > Hi,
> >
> > I noticed a problem with the routing table that is easy to reproduce: put
> > multiple IPs on the same carp interface:
>
> Great bug analysis, however returning EAG
On 04/09/17(Mon) 13:10, Gerhard Roth wrote:
> Hi,
>
> I noticed a problem with the routing table that is easy to reproduce: put
> multiple IPs on the same carp interface:
Great bug analysis, however returning EAGAIN for every route update is a
no go if you have a big routing table like BGP full f
Hi,
I noticed a problem with the routing table that is easy to reproduce: put
multiple IPs on the same carp interface:
# ifconfig em0
em0: flags=8843 mtu 1500
lladdr 00:0a:e4:31:9d:6e
index 1 priority 0 llprio 3
groups: egress
media: Ethernet autoselect (100baseTX
