← Back to team overview

gufw-developers team mailing list archive

[Bug 1401885] Re: Allowing all UDP/TCP traffic in

 

I'm fine :) Thanks!

If I reproduce your first screenshot I'm getting this error: ERROR: Must specify 'tcp' or 'udp' with multiple ports
That is not a problem of interfaces, it's a problem that in ufw if you're using a port range, you have to add tcp and udp in split rules (both rule = tcp + udp rules).
I created a really simple rule with a port range, please see my attachment. That is returning an error too from ufw ;)

I'm not sure if I replied to all your questions :$ Please, ping me if not :) Be my guest!
Best regards Jean!


** Attachment added: "Screenshot - 131214 - 12:55:57.png"
   https://bugs.launchpad.net/gui-ufw/+bug/1401885/+attachment/4280236/+files/Screenshot%20-%20131214%20-%2012%3A55%3A57.png

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


References