Re: Introduce if_rtrequest()

2015-10-25 Thread Martin Pieuchot
On 25/10/15(Sun) 18:06, Ossi Herrala wrote: > On Sun, Oct 25, 2015 at 09:58:00AM +0100, Claudio Jeker wrote: > > On Sat, Oct 24, 2015 at 06:22:10PM +0200, Martin Pieuchot wrote: > > > On 24/10/15(Sat) 18:01, Martin Pieuchot wrote: > > > > > As a side effect arp_ifinit() can now die since every Eth

Re: Introduce if_rtrequest()

2015-10-25 Thread Ossi Herrala
On Sun, Oct 25, 2015 at 09:58:00AM +0100, Claudio Jeker wrote: > On Sat, Oct 24, 2015 at 06:22:10PM +0200, Martin Pieuchot wrote: > > On 24/10/15(Sat) 18:01, Martin Pieuchot wrote: > > > As a side effect arp_ifinit() can now die since every Ethernet driver > > > initialize if_rtrequest in ether_if

Re: Introduce if_rtrequest()

2015-10-25 Thread Claudio Jeker
On Sat, Oct 24, 2015 at 06:22:10PM +0200, Martin Pieuchot wrote: > On 24/10/15(Sat) 18:01, Martin Pieuchot wrote: > > Revamping the network stack design continue here at u2k15... > > > > This times it's about the L2 resolution mechanism plugged into the > > routing table. While discussing with A

Re: Introduce if_rtrequest()

2015-10-24 Thread Martin Pieuchot
On 24/10/15(Sat) 18:01, Martin Pieuchot wrote: > Revamping the network stack design continue here at u2k15... > > This times it's about the L2 resolution mechanism plugged into the > routing table. While discussing with Alexander we figured out that > the actual ifa_rtrequest() is always called

Introduce if_rtrequest()

2015-10-24 Thread Martin Pieuchot
Revamping the network stack design continue here at u2k15... This times it's about the L2 resolution mechanism plugged into the routing table. While discussing with Alexander we figured out that the actual ifa_rtrequest() is always called with a valid ``ifp''... So this diff change this functio