netdev - [PATCH 0/4] Make tcp-metrics source-address aware

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]

Message-Id: <1387109444-1104-1-git-send-email-christoph.paasch@uclouvain.be>
Date:	Sun, 15 Dec 2013 13:10:40 +0100
From:	Christoph Paasch <christoph.paasch@...ouvain.be>
To:	netdev@...r.kernel.org
Cc:	David Miller <davem@...emloft.net>,
	Eric Dumazet <eric.dumazet@...il.com>,
	Julian Anastasov <ja@....bg>
Subject: [PATCH 0/4] Make tcp-metrics source-address aware

Currently tcp-metrics only stores per-destination addresses. This brings
problems, when a host has multiple interfaces (e.g., a smartphone having
WiFi/3G):

For example, a host contacting a server over WiFi will store the tcp-metrics
per destination IP. If then the host contacts the same server over 3G, the 
same tcp-metrics will be used, although the path-characteristics are completly
different (e.g., the ssthresh is probably not the same).

The same holds for the fast-open cookie. The server will generate a cookie
based on our source-address. So, if we contact the same server with another
source-IP we should request a new cookie.

This patchset makes tcp-metrics source-address aware (Patch 1 and 2).

Patches 3 and 4 handle the interface to "ip tcp_metrics". When deleting a
metric based on the destination-IP, all entries will be removed (Patch 3).
Further, a new attribute is added, so that the source-IP can be exposed to
"ip tcp_metrics" (Patch 4).

Note:
"ip tcp_metrics show ADDRESS" will only display the first element among
the entries for the specified destination-IP. It probably would be better to
show all entries for the specified IP. However, I do not see how to achieve 
this without fundamentally changing the netlink-API for the tcp-metrics.

Suggestions are very welcome.

Christoph Paasch (4):
  tcp: metrics: rename tcpm_addr to tcpm_daddr
  tcp: metrics: Add source-address to tcp-metrics
  tcp: metrics: Delete all entries matching a certain destination
  tcp: metrics: Dump info of the source-address in netlink-reply

 include/uapi/linux/tcp_metrics.h |   2 +
 net/ipv4/tcp_metrics.c           | 111 ++++++++++++++++++++++++---------------
 2 files changed, 71 insertions(+), 42 deletions(-)

-- 
1.8.3.2

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