<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Services list is confusingly different from the /etc/services"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1236#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Services list is confusingly different from the /etc/services"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1236">bug 1236</a>
from <span class="vcard"><a class="email" href="mailto:pablo@netfilter.org" title="Pablo Neira Ayuso <pablo@netfilter.org>"> <span class="fn">Pablo Neira Ayuso</span></a>
</span></b>
<pre>(In reply to Robin McCorkell from <a href="show_bug.cgi?id=1236#c2">comment #2</a>)
<span class="quote">> While adding more standard services to the list would help, and the ability
> to define custom services is useful, it misses the point.
>
> As a new user of nftables coming from an iptables world, when I see a
> service name (e.g. 'domain') I expect that to be identical to /etc/services
> - as soon as there is *any* incompatibility I get frustrated. The service
> list used by nft should be /etc/services, not some custom internal table.</span >
iptables-save doesn't use service names, and this is the prefered way to
save/restore/display rulesets these days.
<span class="quote">> As long as a custom internal table is used, there will always be issues.
> Just use the system-provided services database via nsswitch.</span >
These service lists are inconsistent under /etc/services from vendor to vendor,
hence moving one ruleset policy using service names from one linux vendor to
another may break.
I understand there's is a mind shift from iptables users, we're aiming to have
a self-contained scripting language in nftables.
I think defining variables for custom services should be good enough.
If there's any service name clearly wrong or default/standard list of services
is missing anything important, we can make patches for this too, let us know if
that is the case :-)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>