netdev - Re: [PATCH] make TLLAO option for NA packets configurable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091002105351.0fbde9c2@nehalam>
Date:	Fri, 2 Oct 2009 10:53:51 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Octavian Purdila <opurdila@...acom.com>
Cc:	David Miller <davem@...emloft.net>, cratiu@...acom.com,
	netdev@...r.kernel.org
Subject: Re: [PATCH] make TLLAO option for NA packets configurable

On Fri, 2 Oct 2009 01:19:47 +0300
Octavian Purdila <opurdila@...acom.com> wrote:

> On Thursday 01 October 2009 22:37:40 you wrote:
> > From: Stephen Hemminger <shemminger@...tta.com>
> > Date: Thu, 1 Oct 2009 11:56:11 -0700
> > 
> > > On Thu, 1 Oct 2009 21:39:32 +0300
> > >
> > > Octavian Purdila <opurdila@...acom.com> wrote:
> > >> On Thursday 01 October 2009 21:14:50 you wrote:
> > >> > Probably this should be a per interface property rather than per
> > >> > namespace.
> > >>
> > >> In our case, where we have lots of interfaces active, it would be nice
> > >> to have the per namespace property as well.
> > >
> > > The ipv6 control infrastructure already has that option. If you changed
> > > your patch to use a per-interface control then there would be:
> > >
> > >   /proc/sys/net/ipv6/conf/all/force_tllao
> > 
> > Right, this would work a lot better.
> > 
> 
> Here is v3 which also updates Documentation/networking/ip-sysctl.txt.
> 
> Thanks,
> tavi
> 
> 

This is good although I would have shortened the name.


-- 
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html