netdev - Re: Problems with tg3 driver after lowering the MTU

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]

Date:	Thu, 21 Jan 2010 15:27:23 +0000
From:	Ben Hutchings <bhutchings@...arflare.com>
To:	Szilveszter Ordog <slipszi@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: Problems with tg3 driver after lowering the MTU

On Thu, 2010-01-21 at 16:21 +0100, Szilveszter Ordog wrote:
> After the MTU is lowered (e.g. to 1420) on a tg3-driven interface,
> received packets larger than that (e.g. 1500 bytes) are silently
> discarded by the driver. Therefore the system doesn't send ICMP
> fragmentation-needed packets and the other side doesn't detect this
> condition.
> 
> Is this a known bug?

I don't believe this a bug.  Within a local network, MTU should be set
the same for all interfaces.  Routers that connect networks with
different MTUs will generate the fragmentation-needed message as
appropriate.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

--
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