netdev - Re: tipc: MTU discovery

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: <20130305141824.GG15384@eerihug-hybrid.ki.sw.ericsson.se>
Date:	Tue, 5 Mar 2013 15:18:24 +0100
From:	Erik Hugne <erik.hugne@...csson.com>
To:	Sebastian Pöhn <sebastian.poehn@...glemail.com>
CC:	netdev@...r.kernel.org, jon.maloy@...csson.com,
	allan.stephens@...driver.com
Subject: Re: tipc: MTU discovery

On Tue, Mar 05, 2013 at 01:43:29PM +0100, Sebastian Pöhn wrote:
> State Messages larger than 1500 which as used for the MTU negotiation
> do not appear in the TIPC stack. But I am able to seen them entering
> the correct device.
> Because of that no reply with the correct max_packet field set can be
> send and the negotiation will always end up at 1.5k.
> 
> So my questions are:
> # Is TIPC meant to detect and use the MTU larger than 1.5k?
Yes, it should probe and detect MTU's up to ~66k

> # Why are the packets not passed to the TIPC stack?
TIPC just registers itself as a handler for ETH_P_TIPC through dev_add_pack.
If link mtu probes >1.5k are not passed to TIPC, it sounds to me that the NIC driver
is to blame. What NIC type and kernel version are you running?

Do you see any packet drops in ethtool statistics?

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