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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080423061538.GB3946@ff.dom.local>
Date:	Wed, 23 Apr 2008 06:15:38 +0000
From:	Jarek Poplawski <jarkao2@...il.com>
To:	Stephen Hemminger <stephen.hemminger@...tta.com>
Cc:	Ben Hutchings <bhutchings@...arflare.com>,
	Kieran Mansley <kmansley@...arflare.com>,
	Stephen Hemminger <shemminger@...tta.com>,
	netdev@...r.kernel.org
Subject: Re: LRO/GSO interaction when packets are forwarded

On Wed, Apr 23, 2008 at 06:00:18AM +0000, Jarek Poplawski wrote:
> On 23-04-2008 01:01, Stephen Hemminger wrote:
> ...
> >>>> First off, no hardware should ever do LRO on non-local packets. If the
> >>>> hardware isn't smart enough to do this, I guess the bridge code to have
> >>>> an API to turn it off. IP should also turn it off if ip_forwarding
> >>>> is enabled on that device.
> 
> Could you explain this more? (I can't see any obvious reason why
> forwarding between local networks should differ here from bridging?)

...and the second question: is only ip_forwarding flag checking right
way to disable something destined for local packets?
 
Jarek P.
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ