← Back to team overview

epoptes team mailing list archive

[Bug 937820] Re: Incorrect IP for x11vnc -allow option


Hi Robert and thank you for reporting this bug!

Indeed we need to allow the range - too. Maybe a better idea would be to detect the current ip range of the network and allow only this.
The 127. range though is needed because that's what the thin clients use to connect to the server.

** Changed in: epoptes
   Importance: Undecided => Low

** Changed in: epoptes
       Status: New => Confirmed

** Changed in: epoptes
     Assignee: (unassigned) => Fotis Tsamis (phantomas)

You received this bug notification because you are a member of Epoptes
Developers, which is the registrant for Epoptes.

  Incorrect IP for x11vnc -allow option

Status in Epoptes:

Bug description:

  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.


  Robert Wolf.

To manage notifications about this bug go to: