gufw-developers team mailing list archive

[Aaron <lafeyette.management@xxxxxxxxx>]

Hi, again.

Did as you suggested.  No joy.  See attached.

(note:  First three images show the configuration you suggest being set
up.  The forth item, 9.png shows my attempt to ssh to the remote host I
have just set up in the previous steps.  (Black command-line to left.)  You
can see the failed SSH attempt at the top, and below it, I did ifconfig to
prove that my IP is, indeed, on the 155.41.0.0/16 network.

A./


On Fri, Apr 10, 2015 at 10:16 AM, costales <1441850@xxxxxxxxxxxxxxxxxx>
wrote:

> > I forgot to mention that I tried that as well.  The result was that the
> > firewall blocked ssh completely, even from 155.41.0.0/16.  But I will
> try
> > it again and let you know.  When I tried it, I think I was blocking both
> > UDP and TCP.  Should I go that route this time as well?
>
> TCP is enough, but try with both anyway :)
> Be careful and set it as the rule in the top (with the Insert field).
> Cheers!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1441850
>
> Title:
>   Gufw "Advanced" configuration does not really work.
>
> Status in Gufw:
>   New
>
> Bug description:
>   Regarding GUFW as available for Ubuntu 14.04 and later (14.04.2 LTS)
>
>   When trying to configure GUFW to block all access to a server EXCEPT
>   that originating on our internal network (which is somewhat open to
>   the public), GUFW simply throws an error, claiming ERROR: Wrong number
>   of arguments.
>
>   Under the ADVANCED tab, I was trying to specify that ssh requests
>   coming in from our internal class B network, XXX.YYY.0.0/16 should be
>   allowed in on port 22.  To do this, I specified the IP address of the
>   network in the FROM field, and the PORT in the TO field, leaving the
>   PORT in the from field unfilled in and the IP address in the TO field
>   blank.
>
>   All I get is an error placed in the log:  ERROR: Wrong number of
>   arguments.
>
>   This tells me nothing useful.
>
>
>   However, in the older version of Gufw, version 12.04.1,  (as is
> available with Ubuntu 12.04), this same configuration technique works
> perfectly.)
>
>   So far, the only way around this seems to be to manipulate the
>   underlying UFW directly, but that is not very easy as the command-line
>   configuration is, shall we say, rather less than intuitive (as in
>   "needlessly arcane, finicky, non-standard and complex")
>
>   Of course, however, rules applied to UFW directly cannot be modified
>   or even looked at from Gufw.  Worse, if I copy a rule that
>   approximates what I want, then try to modify it, Gufw deletes the
>   original rule, claims to have added the new one, but examination of
>   the log reveals that the modified rule has failed, so it ends up
>   stripping both the original copied rule and the modified one.  I would
>   have expected to be shown the error and the original rule that I
>   copied left there, unchanged.  Evidently, however, the actual error-
>   checking only occurs AFTER the rule was copied and modified, rather
>   than before attempting to modify.  Not good.
>
>   An inexperienced systems administrator could very well be fooled into
>   thinking the changed rule worked when, in fact, it did not, so no
>   error message is displayed.  Busy systems admins don't always think to
>   check the log, especially if the log is known to not provide very much
>   useful or helpful information.  "ERROR: Wrong number of arguments." is
>   definitely in the category of "not very useful or helpful."
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gui-ufw/+bug/1441850/+subscriptions
>


-- 
The truth is out there...somewhere....getting wet in the rain....


** Attachment added: "6.png"
   https://bugs.launchpad.net/bugs/1441850/+attachment/4371612/+files/6.png

** Attachment added: "7.png"
   https://bugs.launchpad.net/bugs/1441850/+attachment/4371613/+files/7.png

** Attachment added: "8.png"
   https://bugs.launchpad.net/bugs/1441850/+attachment/4371614/+files/8.png

** Attachment added: "9.png"
   https://bugs.launchpad.net/bugs/1441850/+attachment/4371615/+files/9.png

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

Title:
  Gufw "Advanced" configuration does not really work.

Status in Gufw:
  New

Bug description:
  Regarding GUFW as available for Ubuntu 14.04 and later (14.04.2 LTS)

  When trying to configure GUFW to block all access to a server EXCEPT
  that originating on our internal network (which is somewhat open to
  the public), GUFW simply throws an error, claiming ERROR: Wrong number
  of arguments.

  Under the ADVANCED tab, I was trying to specify that ssh requests
  coming in from our internal class B network, XXX.YYY.0.0/16 should be
  allowed in on port 22.  To do this, I specified the IP address of the
  network in the FROM field, and the PORT in the TO field, leaving the
  PORT in the from field unfilled in and the IP address in the TO field
  blank.

  All I get is an error placed in the log:  ERROR: Wrong number of
  arguments.

  This tells me nothing useful.

  
  However, in the older version of Gufw, version 12.04.1,  (as is available with Ubuntu 12.04), this same configuration technique works perfectly.)

  So far, the only way around this seems to be to manipulate the
  underlying UFW directly, but that is not very easy as the command-line
  configuration is, shall we say, rather less than intuitive (as in
  "needlessly arcane, finicky, non-standard and complex")

  Of course, however, rules applied to UFW directly cannot be modified
  or even looked at from Gufw.  Worse, if I copy a rule that
  approximates what I want, then try to modify it, Gufw deletes the
  original rule, claims to have added the new one, but examination of
  the log reveals that the modified rule has failed, so it ends up
  stripping both the original copied rule and the modified one.  I would
  have expected to be shown the error and the original rule that I
  copied left there, unchanged.  Evidently, however, the actual error-
  checking only occurs AFTER the rule was copied and modified, rather
  than before attempting to modify.  Not good.

  An inexperienced systems administrator could very well be fooled into
  thinking the changed rule worked when, in fact, it did not, so no
  error message is displayed.  Busy systems admins don't always think to
  check the log, especially if the log is known to not provide very much
  useful or helpful information.  "ERROR: Wrong number of arguments." is
  definitely in the category of "not very useful or helpful."

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