<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:fw@strlen.de" title="Florian Westphal <fw@strlen.de>"> <span class="fn">Florian Westphal</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - interface wildcard in variables causes Error: Byteorder mismatch: expected big endian, got host endian"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1253">bug 1253</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>fw@strlen.de
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - interface wildcard in variables causes Error: Byteorder mismatch: expected big endian, got host endian"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1253#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - interface wildcard in variables causes Error: Byteorder mismatch: expected big endian, got host endian"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1253">bug 1253</a>
from <span class="vcard"><a class="email" href="mailto:fw@strlen.de" title="Florian Westphal <fw@strlen.de>"> <span class="fn">Florian Westphal</span></a>
</span></b>
<pre>(In reply to Ian Kumlien from <a href="show_bug.cgi?id=1253#c0">comment #0</a>)
<span class="quote">> if you do:
> define $interfaces = {
> tun*,
> lo
> }
>
> and then using that variable:
> iifname $interfaces accept
>
> results in:
> Error: Byteorder mismatch: expected big endian, got host endian</span >
Yes, problem is that
iifname { "tun*", "lo" }
cotains a "*".
<span class="quote">> but if i do:
> iifname tun* accept
>
> it works.</span >
Yes, in this case we just do "iifname tun", with the difference that we compare
3 bytes instead of 4 (with a \0 character).
For the lookup case, we can't do it, as no cmp happens, we instead pass
the interface name as key to the set lookup function, i.e. the "*" will never
match, as we can't know that we only should lookup "tun", not e.g. "tun0" or
"veth1".
So, its likely we need to present a better error message rather than this
obscure followup error.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>