** Changed in: ufw (Ubuntu)
       Status: Triaged => In Progress

** Changed in: ufw (Ubuntu)
     Assignee: (unassigned) => Jamie Strandboge (jdstrand)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1204579

Title:
  ufw doesn't support concurrent updates

Status in ufw:
  Fix Committed
Status in ufw package in Ubuntu:
  In Progress
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged
Status in ufw source package in Disco:
  In Progress
Status in ufw package in Debian:
  New

Bug description:
  On a server under Ubuntu 12.04 I automatically update firewall rules and I 
unfortunately noticed that if 2 rules are processed at the same time it leads 
to an inconsistent result between iptables and ufw status.
  In fact it can be reproduced using the python script in attachment.

  Before executing this script I didn't have any rules matching the ip 
192.168.254.1 on my computer.
  After a launch iptables takes into acount 464 rules.

  sudo iptables -L -n | grep 192.168.254.1 | wc -l
  464

  It should be 500 rules but the script stressed a lot my system and all rules 
can't be processed by iptables
  sudo ./test_ufw_threads.py
  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.
  [...]

  Anyway, ufw stores only the last updates (in /lib/ufw/user.rules):

  sudo ufw status
  État : actif

  Vers Action Depuis
  ---- ------ ------
  192.168.254.1 1234/tcp     ALLOW       192.168.46.9
  192.168.254.1 1234/tcp     ALLOW       192.168.22.10
  192.168.254.1 1234/tcp     ALLOW       192.168.32.10
  192.168.254.1 1234/tcp     ALLOW       192.168.5.10
  192.168.254.1 1234/tcp     ALLOW       192.168.43.9
  192.168.254.1 1234/tcp     ALLOW       192.168.40.10
  192.168.254.1 1234/tcp     ALLOW       192.168.46.10
  192.168.254.1 1234/tcp     ALLOW       192.168.48.10
  192.168.254.1 1234/tcp     ALLOW       192.168.42.10
  192.168.254.1 1234/tcp     ALLOW       192.168.43.10

  So I can't delete other rules using ufw, I had to directly use iptables.
  In this case I can only delete 10 rules using ufw.
  Could you please handle some kind of lock?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to