epoptes team mailing list archive
-
epoptes team
-
Mailing list archive
-
Message #01119
[Bug 1549467] Re: Standalone client is not showing in epoptes
Hi, Alkis, you're welcome!
Thank you for the fixes! Amount of ram is now detected correctly.
But still info() fails on that router-client. According to routing table 'server' is accessible through interface tun0. But tun interfaces do not have MAC address, therefore info() fails with "ERROR: Empty MAC". Please check the output:
ip link show dev tun0
6: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 100
link/none
maybe we should use
MAC=`ip a|awk '/ether/{print $2;exit}'`
as a fallback? Anyway, client is uniquely identified with any of the MACs it has.
--
You received this bug notification because you are a member of Epoptes
Developers, which is subscribed to Epoptes.
https://bugs.launchpad.net/bugs/1549467
Title:
Standalone client is not showing in epoptes
Status in Epoptes:
Fix Committed
Bug description:
Hello,
I have two clients (172.22.21.128 and 172.22.21.129).
Systems is almost identical Lubuntu 14.04 except that one box is also a router.
I do epoptes-client from both clients with the same output:
* Epoptes-client connecting to 172.22.11.20:789...
...done.
Command line is not complete. Try option "help"
Also on the server I run: netstat -tp | grep 789
tcp 0 0 ts.ad.aris-omsk.ru:789 172.22.21.129:33903 ESTABLISHED 26304/python
tcp 0 0 ts.ad.aris-omsk.ru:789 172.22.21.128:34489 ESTABLISHED 26304/python
Client 172.22.21.129 appears in epoptes console, client 172.22.21.128
does not whatever I do.
I'm sorry. I don't know how to debug this. Could you help me please.
To manage notifications about this bug go to:
https://bugs.launchpad.net/epoptes/+bug/1549467/+subscriptions
References