On 28/05/14(Wed) 16:15, Martin Pieuchot wrote:
> On 26/05/14(Mon) 15:17, Martin Pieuchot wrote:
> > On 26/05/14(Mon) 08:03, Kenneth Westerback wrote:
> > > [...]
> > >
> > > dhclient used to create such routes but that was removed as useless so
> > > I'm not sure why we want/need to add them back.
On 28 May 2014 10:18, Kenneth Westerback wrote:
> On 28 May 2014 10:15, Martin Pieuchot wrote:
>> On 26/05/14(Mon) 15:17, Martin Pieuchot wrote:
>>> On 26/05/14(Mon) 08:03, Kenneth Westerback wrote:
>>> > [...]
>>> >
>>> > dhclient used to create such routes but that was removed as useless so
>>>
On 28 May 2014 10:15, Martin Pieuchot wrote:
> On 26/05/14(Mon) 15:17, Martin Pieuchot wrote:
>> On 26/05/14(Mon) 08:03, Kenneth Westerback wrote:
>> > [...]
>> >
>> > dhclient used to create such routes but that was removed as useless so
>> > I'm not sure why we want/need to add them back. I'm no
On 26/05/14(Mon) 15:17, Martin Pieuchot wrote:
> On 26/05/14(Mon) 08:03, Kenneth Westerback wrote:
> > [...]
> >
> > dhclient used to create such routes but that was removed as useless so
> > I'm not sure why we want/need to add them back. I'm not a routing
> > table guru so perhaps this is differ
On 26/05/14(Mon) 08:03, Kenneth Westerback wrote:
> [...]
>
> dhclient used to create such routes but that was removed as useless so
> I'm not sure why we want/need to add them back. I'm not a routing
> table guru so perhaps this is different in some way.
We want it back to be able to tell if an
* Kenneth Westerback [2014-05-26 14:05]:
> dhclient used to create such routes but that was removed as useless so
> I'm not sure why we want/need to add them back. I'm not a routing
> table guru so perhaps this is different in some way.
there is a broad difference between "the kernel does it alwa
On 26 May 2014 06:10, Martin Pieuchot wrote:
> Diff below changes the behavior of the kernel to add a route for every
> new IPv4 address, when it is configured on an interface. Actually
> such route is created the first time a program tries to resolve it.
> That's why with this diff you don't se
Diff below changes the behavior of the kernel to add a route for every
new IPv4 address, when it is configured on an interface. Actually
such route is created the first time a program tries to resolve it.
That's why with this diff you don't see the "cloned" flag:
-10.3.3.2 00:00:24:cc: