Re: RIF/VRF overflow in spectrum and reporting errors back to user

2017-10-10 Thread Ido Schimmel
On Tue, Oct 10, 2017 at 09:23:48AM -0600, David Ahern wrote: > On 10/9/17 3:31 AM, Ido Schimmel wrote: > >> Can NETDEV_UP be ignored for the inetaddr notifier if it is handled by > >> the validator notitifer? > > > > Yes. The case where we get a NETDEV_DOWN for an address delete and then > > a NET

Re: RIF/VRF overflow in spectrum and reporting errors back to user

2017-10-10 Thread David Ahern
On 10/9/17 3:31 AM, Ido Schimmel wrote: > Hi David, > > On Sun, Oct 08, 2017 at 02:10:33PM -0600, David Ahern wrote: >> Jiri / Ido: >> >> I am looking at adding user messages for spectrum failures related to >> RIF and VRF overflow coming from the inetaddr and inet6addr notifier >> paths. The key

Re: RIF/VRF overflow in spectrum and reporting errors back to user

2017-10-09 Thread Ido Schimmel
Hi David, On Sun, Oct 08, 2017 at 02:10:33PM -0600, David Ahern wrote: > Jiri / Ido: > > I am looking at adding user messages for spectrum failures related to > RIF and VRF overflow coming from the inetaddr and inet6addr notifier > paths. The key is that if the notifiers fail the address add need

RIF/VRF overflow in spectrum and reporting errors back to user

2017-10-08 Thread David Ahern
Jiri / Ido: I am looking at adding user messages for spectrum failures related to RIF and VRF overflow coming from the inetaddr and inet6addr notifier paths. The key is that if the notifiers fail the address add needs to fail and an error reported to the user as to what happened. Earlier this yea