jwise@draga.com said:
> the services table is _at least_ as useful for identifying  services
> floating by on the network as it is for local servers, and that
> implies that a criteria broader than ``used on NetBSD'' is a good
> idea. 

Fwiw, I just had a situation where having too many known ports
gets annoying. netstat on a linux box:

tcp        0      0 iff974.if:kyoceranetdev iffkw103.iff.kfa-j:2082 ESTABLISHED
tcp        0      0 iff974.iff.kfa:startron zel621:twsdss           ESTABLISHED
tcp        0      0 iff974.if:kyoceranetdev iffkw103.iff.kfa-j:2083 ESTABLISHED
tcp        0      0 iff974.iff.kfa:startron iffkw103.iff.kfa-j:2086 ESTABLISHED
tcp        0      0 iff974.if:kyoceranetdev iff253-a:35963          ESTABLISHED
tcp        0      0 iff974.iff.kfa:startron iffkw103.iff.kfa-ju:eli ESTABLISHED
tcp        0    208 iff974.iff.kfa-juel:ssh zel459:lnvpoller        ESTABLISHED
tcp        0      0 iff974.if:kyoceranetdev zel621:pxc-ntfy         ESTABLISHED
tcp        0      0 iff974.iff.kfa-juel:ssh iff253-a:34909          ESTABLISHED
tcp        0      0 iff974.iff.kfa:startron iff253-a:35957          ESTABLISHED
tcp        0      0 iff974.iff.kfa-juel:ddt zel101:6000             ESTABLISHED
tcp        0      0 iff974.iff.kfa-juel:ssh zel743.zel.kfa-ju:32828 ESTABLISHED

All portnames except "ssh" are nonsense.

$ wc /etc/services
   9622   37972  417925 /etc/services

(A config file which port ranges to decode could help. Per-host or per user...
I'm in doubt whether this is worth the complexity.)

best regards
Matthias