gufw-developers team mailing list archive

["D. Charles Pyle" <dcharlespyle@xxxxxxx>]

They are a range of private IPs (192.168.0.1-192.168.0.100) and the port
is 5950.  The VNC server is VMWare Player, running Windows XP
Professional for a few apps that absolutely will not run on Linux or in
WINE.  I used the advanced settings to do it.  I also tried the
preconfigured and simple rules, too.  Nothing worked to allow access
unless I set the setting at the top to allow incoming traffic or
completely turn off the firewall.  Once the connection is established, I
can turn it back on or reset the control to deny or reject and will
still be able to use VNC.

** Attachment added: "Screenshot of current rules in place."
   https://bugs.launchpad.net/gui-ufw/+bug/1443203/+attachment/4374609/+files/Screenshot%20from%202015-04-13%2020%3A42%3A22.png

-- 
You received this bug notification because you are a member of Gufw
Developers, which is subscribed to Gufw.
https://bugs.launchpad.net/bugs/1443203

Title:
  GUFW blocks all incoming VNC connections even if rules allow

Status in Gufw:
  New

Bug description:
  I am having a problem with GUFW.  I have it set to block incoming
  connections from everything.  I then set rules to allow incoming
  connections from a VNC client on my local network to a VMWare Player
  VNC setup but no matter what I do with those rules, I cannot connect
  to the VNC server on my machine unless I change the setting for my
  profile to Allow for everything.  Making and applying rules has no
  effect if the "Incoming" setting at the top of the application is set
  to Deny or Reject.

  The only other option is to turn off the firewall entirely for a
  moment for the VNC client to connect, and then turn it back on again
  once a connection is established.  Allowing all incoming connections
  for even a few moments just to use VNC on one port is a security risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gui-ufw/+bug/1443203/+subscriptions