gufw-developers team mailing list archive

[costales <1401885@xxxxxxxxxxxxxxxxxx>]

Hi Jean! How are you? :)

In the Log tab I see this message: "ERROR: Bad source address". 
Reviewing your screenshot, your "From IP" is this "192.168.168.56.0/24", it's a wrong IP, you set 2 times the "168" :) With this IP "192.168.56.0/24" is working for me.

> allowing all TCP/UDP communication IN is not possible with Gufw

Yes, it has to work, just add a rule with "Protocol = Both" and
"Direction = IN". Do you have a screenshot when you can't add it? :)

> displaying/editing some ufw rules is not possible within gufw

Yes, it's right. When you add a rule in Gufw, I'm store how that rule is
for the comment, edit... I want to say, a rule from ufw is complicate to
rebuild its command. Then, you can't edit ufw rules, I'm sorry.

Best regards Jean!

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

Title:
  Allowing all UDP/TCP traffic in

Status in Gufw:
  New

Bug description:
  Environment: Ubuntu 14.10 - Gufw 14.10.1
  ------------------

  The configuration is basic: 
  - Incoming: Deny
  - Outgoing: Allow
  - Routing: Allow

  Now, suppose you need to allow internal communication, for example all
  incoming UDP/TCP traffic from a VirtualBox VM on vboxnet0 sitting on a
  particular subnet, 192.168.56.0/24 is used here.

  Using Gufw to implement this simple setup does NOT work (UDP
  communication is still blocked - TCP configuration is not shown):
  https://drive.google.com/file/d/0B5fXyIn0-GDFbUpMaW0zVTlqYUE/view?usp=sharing

  However, using ufw allows us to attain our goal:
  ufw status
  Status: active

  To                         Action      From
  --                         ------      ----
  192.168.56.1 1:65535/tcp   ALLOW       192.168.56.0/24
  192.168.56.1 1:65535/udp   ALLOW       192.168.56.0/24

  This simple configuration allows all UDP/TCP communication in from
  192.168.56.0/24 towards the host servers.

  The problem is: it is not possible to use Gufw to make that setup, and
  once it is done through ufw CLI, it is not possible to display or edit
  it within Gufw.

  As a summary:
  --------------------
  - allowing all TCP/UDP communication IN is not possible with Gufw (have I missed something?) 
  - displaying/editing some ufw rules is not possible within gufw (have I missed something?)

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