Re: Requesting comments on Multi-routing table usage

2008-07-18 Thread Ian Smith
On Thu, 17 Jul 2008, Julian Elischer wrote: > Julian Elischer wrote: > > Ian Smith wrote: > >> On Thu, 17 Jul 2008, Julian Elischer wrote: > >> > The current code in -current will add a new interface to all > >> > FIBs. [..] > >> Yes in addition to 'setfib N command' it would be likely usef

Re: Requesting comments on Multi-routing table usage

2008-07-17 Thread Julian Elischer
Julian Elischer wrote: Ian Smith wrote: On Thu, 17 Jul 2008, Julian Elischer wrote: > The current code in -current will add a new interface to all > FIBs. Consider yanking/reinserting cardbus NICs as one source of fun. > So for example when you add a gre interface irt shows up everywhere.

Re: Requesting comments on Multi-routing table usage

2008-07-17 Thread Julian Elischer
Ian Smith wrote: On Thu, 17 Jul 2008, Julian Elischer wrote: > The current code in -current will add a new interface to all > FIBs. Consider yanking/reinserting cardbus NICs as one source of fun. > So for example when you add a gre interface irt shows up everywhere. > > This behaviour is

Re: Requesting comments on Multi-routing table usage

2008-07-17 Thread Ian Smith
On Thu, 17 Jul 2008, Julian Elischer wrote: > The current code in -current will add a new interface to all > FIBs. Consider yanking/reinserting cardbus NICs as one source of fun. > So for example when you add a gre interface irt shows up everywhere. > > This behaviour is probbaly correct fo

Requesting comments on Multi-routing table usage

2008-07-17 Thread Julian Elischer
The current code in -current will add a new interface to all FIBs. So for example when you add a gre interface irt shows up everywhere. This behaviour is probbaly correct for the base NICs on the system when you boot, but it is probably wrong in other cases. For example, when mpd makes tunnel