[X2Go-Dev] Traffic Shapping

[Mike Gabriel]

Hi Helmer, hi Stefan,

On Do 05 Apr 2012 20:10:22 CEST Stefan Baur wrote:

>> maybe i'm seeing it bad, but it seems that when
>> connected to a rdp server inside a x2gosession both the traffic when
>> watching a youtube video and transfering a 16MB file arrive at the same
>> port, in my case both connection when watched with iftop are receiving
>> all traffic at my port 33349 and being transmitted at :44126 server
>> port. Is this normal ?
>
> That is something that Heinz, Alex and Mike will probably be able to  
> answer better than me, but my gut feeling says that's expected  
> behavior.

The SSH connecting process does this... (c) stands for client  
functionality, (s) stands for server functionality:

  o set up a master connection (normal ssh login, so to say), from X2Go client
    (c) to X2Go server (s).
  o over this master connection: set up one port forwarding tunnel for nxproxy
    (c) -> x2goagent (s) connection (graphics port)
  o over this master connection: set up one reverse port forwarding tunnel for
    audio stream. Applications in the X2Go session (c) can contact the
    client-side audio daemon (s).
  o over this master connection: set up one reverse port forwarding tunnel for
    SSHFS file/folder sharing. from within the X2Go session you can mount (c)
    client-side folder resources (s) via SSHFS

All the above named traffic can be listened to if you eavesdrop on the  
client/server port pair of the master SSH connection.

Hope that helps!

Greets,
Mike





-- 

DAS-NETZWERKTEAM
mike gabriel, dorfstr. 27, 24245 barmissen
fon: +49 (4302) 281418, fax: +49 (4302) 281419

GnuPG Key ID 0xB588399B
mail: mike.gabriel at das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.x2go.org/pipermail/x2go-dev/attachments/20120406/0f1b7a8e/attachment.pgp>