Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: iptables (Ubuntu Impish)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
And s390x =(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1949603
Title:
iptables-save -c shows incorrect counters with iptables-nft
Status in iptables package in
The newly enabled autopkgtest appears to regress on i386 =/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1949603
Title:
iptables-save -c shows incorrect counters with
Hello Andrea, or anyone else affected,
Accepted iptables into impish-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iptables/1.8.7-1ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: iptables (Ubuntu Impish)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1949603
Title:
iptables-save -c shows
This bug was fixed in the package iptables - 1.8.7-1ubuntu4
---
iptables (1.8.7-1ubuntu4) jammy; urgency=medium
[ Andrea Righi ]
* Fix counters with iptables-nft and add a test case (LP: #1949603)
- d/p/9005-iptables-nft-fix-Z-option.patch
* Enable iptables selftest in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: iptables (Ubuntu Impish)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
** Changed in: iptables (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1949603
Title:
iptables-save -c shows incorrect
@arighi suggests used to be installed when one used to provide "needs-
suggests" restrictions or some such, but that got deprecated, so no
suggests are not getting installed by default.
However, we have a multi year MIR to seed and install nftables by
default let me check the status of that
New debdiff with the enabled autopkgtest test case. (I'm assuming the
Suggests: packages are installed when we run autopkgtest, so I'm not
doing anything special to install nftables).
** Patch added: "iptables-nft-fix-counters-v2.debdiff"
Alright I figured out why the tests were failing, simply nftables wasn't
installed in my test environment. I see that nftables is reported in the
Suggests: list.
@xnox IIRC we are installing all the suggests when we run the autotest,
is it correct?
--
You received this bug notification because
@xnox interestingly enough 2 tests are failing with nft and 1 test in
legacy running `./run-tests.sh --host`:
W: [FAILED] ././testcases/ipt-restore/0004-restore-race_0: expected 0 but
got 1
...
I: legacy results: [OK] 49 [FAILED] 1 [TOTAL] 50
W: [FAILED]
In addition to the changelog versions it seems to me that the debdiff is
potentially a bit missleading:
1) the shell testcases are not executed neither during build, nor during
autopkgtest. As they seem to need root, it would be nice to add
autopkgtest that would do:
cd iptables/tests/shell;
The proposed patch looks ok.
The version numbers are interesting. Impish release is at
1.8.7-1ubuntu2, and impish upload 1.8.7-1ubuntu3 got only published
into Jammy.
So the correct version numbers to use will be ubuntu4 for jammy and 2.1
for impish, I will correct that for SRU.
--
You
** Description changed:
+ [Impact]
+
Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
is always failing. Initially I thought it was a kernel issue, but
debugging further I found that the reason is that with Impish we're
using iptables-nft by default instead of
** Changed in: iptables (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: iptables (Ubuntu Jammy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1949603
Title:
iptables-save -c shows incorrect counters with iptables-nft
Status in iptables
The debdiff in attach seems to solve the problem.
Without this fix applied:
$ sudo ./tools/testing/selftests/net/xfrm_policy.sh
PASS: policy before exception matches
FAIL: expected ping to .254 to fail (exceptions)
...
With this fix applied:
$ sudo ./tools/testing/selftests/net/xfrm_policy.sh
FYI, I've tested the latest iptables from
https://git.netfilter.org/iptables/ and the test passes also with
iptables-nft.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
19 matches
Mail list logo
