Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. RFC: multipath routing for services and sessions (Dragos Tatulea)
----------------------------------------------------------------------
Message: 1
Date: Mon, 14 Mar 2016 18:20:59 +0100
From: Dragos Tatulea <[email protected]>
To: [email protected]
Subject: RFC: multipath routing for services and sessions
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Hello,
We've been working recently on adding a few features to ConnMan for
Multipath TCP. However, most features are not related to Multipath TCP
and they could be useful in upstream. Please let me know what is of
interest from the list below:
* Per service multipath routing: This is a per service flag that
allows the installation of a multipath table for a service.
Something in the lines of:
$> ip rule
0: from all lookup local
32763: from 10.10.3.2 lookup 283
32764: from 10.10.2.2 lookup 281
32765: from 10.10.1.2 lookup 279
32766: from all lookup main
32767: from all lookup default
$> ip route show table 283
default via 10.10.3.1 dev vethc3
10.10.3.0/24 dev vethc3 scope link
There are 3 services above with multipath routing on.
There's also a generic switch to turn it on by default in all
services.
* Multipath routing support for sessions: Each session contains a list
of services that are added automatically if they have the multipath
option set and they are considered connected. For all those services,
fwmark + src ip rules are created to the service multipath routing
table. It would look like this:
$ ip rule
0: from all lookup local
32760: from 10.10.1.2 fwmark 0x10000 lookup 261
32761: from 10.10.3.2 fwmark 0x10000 lookup 265
32762: from all fwmark 0x10000 lookup 65536
32763: from 10.10.3.2 lookup 265
32764: from 10.10.2.2 lookup 263
32765: from 10.10.1.2 lookup 261
32766: from all lookup main
32767: from all lookup default
The default service is not added to this list. But it has the
default rule (32762).
It's also possible to modify the list via the DBus API.
* Flow Selectors: this is a fancy name for per session 5 tuple
iptables rules. A 5 tuple contains: source/destination ip,
protocol (tcp|udp), source/destination port. Fields can also be
omitted. 3 rules would look like this:
$ iptables -t mangle -L
...
Chain connman-OUTPUT (1 references)
target prot opt source destination
MARK tcp -- 11.11.11.11 22.22.22.22 tcp spt:1111 dpt:2222 MARK set 0x10000
MARK all -- 33.33.33.33 44.44.44.44 MARK set 0x10000
MARK udp -- anywhere anywhere udp spt:7777 dpt:8888 MARK set 0x10000
...
Currently these tules are only added to the output chain. But that can
be made more flexible.
These work as/in tandem with policy descriptors. The idea is to bind
a certain kind of traffic to a session. However, you don't necessarily
need a policy file for them. They can be set via the session API too.
Would these features be interesting for upstream ConnMan? If yes, I'd
gladly split the current patches [1] into per feature patch sets and
send them here. Please let me know.
[1] - https://github.com/endocode/connman/tree/work
Thanks
--
Dragos Tatulea
Software Developer @ Endocode AG
[email protected]
Endocode AG, Br?ckenstra?e 5A, 10179 Berlin
+49 30 1206 4472 | [email protected] | www.endocode.com
Vorstandsvorsitzender: Mirko Boehm
Vorst?nde: Dr. Thomas Fricke, Sebastian Sucker
Aufsichtsratsvorsitzende: Alexandra Boehm
Registergericht: Amtsgericht Charlottenburg - HRB 150748 B
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 5, Issue 16
**************************************
