<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - iptables fails to parse interface wildcard "-i +" correctly"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1702#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - iptables fails to parse interface wildcard "-i +" correctly"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1702">bug 1702</a>
from <span class="vcard"><a class="email" href="mailto:thomas.strangert@emblasoft.com" title="thomas.strangert@emblasoft.com">thomas.strangert@emblasoft.com</a>
</span></b>
<pre>(In reply to Phil Sutter from <a href="show_bug.cgi?id=1702#c2">comment #2</a>)
<span class="quote">> I can neither reproduce this with current HEAD nor v1.8.7 tag. Is this a
> downstream issue? I see you're facing the problem with
> iptables-1.8.7-1ubuntu5.1, can you try to reproduce with a vanilla build?
>
> Also, you could try calling:
>
> valgrind --leak-check=full iptables -A INPUT -i + -d 192.168.1.10 -j DROP
>
> It should report garbage data read and give some
> details as to where/why it happens.</span >
I noticed it when I moved to a Ubuntu 22.04 LTS from 20.04 LTS, all using
native/standard distro/downstream builds I suppose.
I have reported the bug to Ubuntu as well, so I hope that they can do the
"flavored" tests. I don't have the servers/setup/bandwidth to go much deeper
that I'm already in at.
Ubuntu bug report:
<a href="https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2033663">https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2033663</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>