Hallo, oh I see now ... Thin client is running on server, only screen is transferred to thin client monitor so epoptes makes connection to the same host as running ... OK, correct. Then, as you said, 172. net is missing. OK.
Regards, Robert Wolf. BTW: I have to write this: GREAT Work! I have tested epoptes last thursday and it is stable, working without any problem and so easy and clean design, so I could make our local changes, although I have no idea about Python and/or PyGTK. Some of these changes I could provide here, e.g. studentDemo (streaming one student to other students and teacher). When I have more time, I try to contact developers if my changes can be usefull. -- You received this bug notification because you are a member of Epoptes Developers, which is the registrant for Epoptes. https://bugs.launchpad.net/bugs/937820 Title: Incorrect IP for x11vnc -allow option Status in Epoptes: Confirmed Bug description: Hallo, there is typo in the code of _broadcastScreen() self.vncserver = subprocess.Popen(['x11vnc', '-noshm', '-nopw', '-quiet', '-viewonly', '-shared', '-forever', '-nolookup', '-24to32', '-rfbport', str(self.vncport), '-allow', '127.,192.168.,10.,169.254.' ]) in file /usr/lib/python2.6/dist-packages/epoptes/ui/gui.py. This list should be list of private ranges 192.168.X.X, 10.X.X.X and 172.X.X.X, but there is "127." instead of "172." written. In the network 172.X.X.X will not broadcast screen. Regards, Robert Wolf. To manage notifications about this bug go to: https://bugs.launchpad.net/epoptes/+bug/937820/+subscriptions -- Mailing list: https://launchpad.net/~epoptes Post to : [email protected] Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
