I'm trying to comment an existing ufw firewall rule, but I can't find the exact command

I can easily add a rule with comment like:

sudo ufw allow in on eth0 to any port 80 comment 'test'

But how do I comment an existing rule?

4 Answers 4


If you add exactly same rule, then the existing rule gets overwritten and comment is updated there.


recyber@linux:~$ sudo ufw allow from to any port 1234 comment "Comment"

Rule updated
  • Tested under ubuntu 18.04, existing rule skipped even when comment was applied. Oct 3, 2019 at 6:51
  • 1
    For the record, comment was added in version 0.35
    – Joril
    Dec 2, 2019 at 21:24
  • 1
    Note that insert and prepend options cannot be used when updating a rule. ufw will complain with "Skipping inserting existing rule". Mar 26, 2020 at 18:18

According to ufw man page, there is no way how to edit existing rules in-place.

Here are your options:

A) Delete, and then recreate your rule with comment

B) Use ufw app profiles to define a service, then use description section for your comment.


I know this is a grave dig, but needing to do this myself lead to a much easier answer, so when someone else looks for this, they may benefit.

This lead to a quick investigation of adding a faux rule with comment 'foo', and then investigating the /etc/ufw/user.rules file...

Rule: ufw deny from to any comment foo


### tuple ### deny any any any in comment=666f6f
-A ufw-user-input -s -j DROP

Notice the "comment=666f6f"

So it does not take a rocket scientist to recognize this is hex 66=f&6f=o&6f=o

Using the same model for other rules, I prepended them with comment= and viola!

Hope it saves someone else the vast amount of time it saved me :-)

Edit: Glad someone else found it useful, as well, if anyone struggles with the conversion....

echo -n "foo" | od -A n -t x1 | sed 's/ //g'

returns 666f6f, just substitute your own comment.

This uses echo to get the string to od which allows you to output the data in other number formats, then sed to parse out the spaces.

Note: Comments WITH spaces, the spaces will become hex 20 in od output before sed. So you do not have to account for them with something like regex as we anticipate the output to be hex, and know a space char will never be valid in what we want.

  • Confirmed to work on Raspbian 10, ufw version 0.36! Persists after ufw reload and reboots. By far the easiest way to go. Hoping ufw provides an official command for adding comments to existing rules though. I wouldn't edit critical config files like this by hand on a production system if I could help it. Jun 2 at 18:15

In my installation ufw 0.36 on Ubuntu 18.04 ufw does not update rules, you will need to delete and recreate a rule. As ufw denies everything inbound by default and you open ports as needed. I assume it also does this in other versions too so you may not have your own deny rules to consider but if you do, the numbering may be important to you so you can do the following.

An example with comment.

ufw status numbered
ufw delete <rule number>
ufw insert <old rule number> allow from <IP address> to any port <port or service (ssh smtp imap etc...> comment '<your comment>'
ufw reload
ufw status

This should place the rule back exactly where it was which might be important to your rule configurations for example if you have a blanket deny rule you will want your allow rule before it. If you do not need to do this just omit the insert from the commands and the replacement rule will be appended.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.