<html>
    <head>
      <base href="https://bugzilla.netfilter.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Using wildcard interface names in an anonymous set fails on big endian"
   href="https://bugzilla.netfilter.org/show_bug.cgi?id=1059">1059</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Using wildcard interface names in an anonymous set fails on big endian
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>nftables
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>ppc
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>other
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>major
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P5
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>nft
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>pablo@netfilter.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>magnus.oberg@westermo.se
          </td>
        </tr></table>
      <p>
        <div>
        <pre>I'm running on a PPC platform, big endian.

I'm getting this error at run-time:

/var/run/nftables.rules:10:6-12: Error: Byteorder mismatch: expected big
endian, got host endian
     iifname { "vlan1", "vi-vlan1_*" } ip daddr 33.44.5.6/32 ip protocol 6 tcp
dport 222 accept
     ^^^^^^^

It appears when using a wildcard interface string in an inline set.

The error is raised in byteorder_conversion() called from
expr_evaluate_relational() in evaluate.c.
Inside the OP_LOOKUP case, row 1232.

The string should in host byte order, but that is not expected for the lookup
(due to the prefix_expr_alloc()?)</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are watching all bug changes.</li>
      </ul>
    </body>
</html>