epoptes team mailing list archive

[Alkis Georgopoulos <1549467@xxxxxxxxxxxxxxxxxx>]

Google says it's possible to assign a MAC address to a tun interface,
but since it's not there by default (as tun operates on level 3),
sure, let's fallback to the first MAC address found as you proposed.

I wanted to prefer the one that epoptes is using to connect to the server, because if we select the "first" one, it might not be the same between reboots of the same client, confusing the epoptes UI user.
Another idea could be to *sort* the available MAC addresses before selecting the first one of them...

Thanks again Alek, fix committed in
http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/514.

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