netdev - 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-next>] [day] [month] [year] [list]

Date:	Tue, 5 Mar 2013 13:43:29 +0100
From:	Sebastian Pöhn <sebastian.poehn@...glemail.com>
To:	netdev@...r.kernel.org
Cc:	jon.maloy@...csson.com, allan.stephens@...driver.com
Subject: tipc: MTU discovery

I am trying to run TIPC over a link with a MTU higher than standard
1500 (actually 2k or more).

I have a Ethernet Device configured with this MTU and an overlying
VLAN with the same MTU. Link Layer looks ok, as MTU sized ICMP traffic
is sent and received unfragmented.

TIPC does not discover the higher MTU, it always keeps at 1500.
Smaller ones (1.4k) are detected correctly.

Doing some deeper investigation into the TIPC stack leaded to this observation:
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?
# Why are the packets not passed to the TIPC stack?
--
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