marionnet-dev team mailing list archive

[Simon Baev <simonbaev@xxxxxxxxx>]

Hello All,

Background:
--
I'm trying to run Marionnet in LTSP environment (ltsp.org) installed
on top of Lubuntu 12.10 (Ubuntu + LXDE) with  several thin-terminals
(http://www.disklessworkstations.com/1700-series-thin-clients.html).
This LTSP server is virtualized in VMware ESXi but it should play any
difference.

Setup:
--
1. The LTSP server has IP 168.18.104.142 and latest version of
Marionnet installed using the script.
2. A thin-terminal utilizes PXE boot, gets IP address from the same
LAN, i.e. 168.18.104.128/25 and starts LDM session to LTSP server
3. As soon as LDM session gets authenticated on LSP server it
(thin-terminal) starts X session so I can run Marionnet on it. In
console of the thin-terminal I can see the value of DISPLAY which is
set to <IP of the thin-terminal>:7
4. When I create new project in Marionnet with at least one host and
start up the project, it adds a NIC (one per each Marionnet's host)
with IP address set to 172.23.0.254/255.255.255.255 so I assume it is
sort of P2P tunnel between hosting machine and a host within Marionnet
environment.
5. Once Marionnet's host started I can check the value of its DISPLAY
which is set to 172.23.0.254:0
6. When I try to start wireshark in Marionnet's host I'm getting error:
-----------8<----------
Xlib: connection to "172.23.0.254:0.0" refused by server
Xlib: No protocol specified

(wireshark:5075) Gtk-WARNING **:cannot open display: 172.23.0.254:0
-----------8<----------
7. I assumed that having DISPLAY set to <IP of thin-terminal>:7 on
hosting site may require setting DISPLAY from within Marionnet's host
to 172.23.0.254:7 but it doesn't fix the problem. Actually it fixes
(removes) the first part of the error message related to refused
connection, so the new error message looks like:
-----------8<----------
(wireshark:5076) Gtk-WARNING **:cannot open display: 172.23.0.254:7
-----------8<----------
8. I tried to run marionned not from a thin-terminal but on LTSP
server directly (VMware vSphere Client connected to ESXi hypervisor)
and similar setup works fine out of the box. The only difference is
the value of DISPLAY on LTSP which is now :0 (used to be <IP of
thin-terminal>:7)

Is there any way to workaround this issue, i.e. to let wireshark start
within LDM session running on a thin-terminal?

Thanks.

--
Simon