<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 - Services list is confusingly different from the /etc/services"
   href="https://bugzilla.netfilter.org/show_bug.cgi?id=1236">1236</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Services list is confusingly different from the /etc/services
          </td>
        </tr>

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

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

        <tr>
          <th>Hardware</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

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

        <tr>
          <th>Severity</th>
          <td>normal
          </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>robin@mccorkell.me.uk
          </td>
        </tr></table>
      <p>
        <div>
        <pre>When specifying services by their string form (e.g. "domain" to refer to port
53), an internal service mapping is used (services.c in the source) rather than
the system services database at /etc/services (well, via nsswitch). This
internal service mapping is much smaller than /etc/services, and differs in the
names of some services. This makes it extremely confusing when writing rules.

I'm reporting this as a bug, not as an enhancement, since I think it's a severe
usability issue.

Context:

I've used iptables for a few years, and I wanted to make the switch to nftables
to unify IPv4 and IPv6 configuration. A lot of the syntax is great, a
significant improvement on iptables; but the one thing that stands out badly is
the service mapping. As a new user of nftables, I expect the service mapping to
be identical to /etc/services, and not have a custom, incomplete and
incompatible service list.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are watching all bug changes.</li>
      </ul>
    </body>
</html>