Airport Port Mapping Limit?

Most routers have a similar limit. I know my Linksys can only forward 20 ports.

I'd never have believed it...

is there a workaround? Is this the reason for using a dedicated box for network routing?

Okay, so it's time for me to ask the stupid question:

Why would the average person need to forward twenty or more ports?

On my router I have two ports open for outside world access: 23 & 80. Port 23 is forwarded to a Quadra 700 running NetBSD and port 80 is forwarded to a PM9500 that I'm using as a webserver.

Let me see if I can figure this out:

A hotline server would require two ports.
A webserver would require one port. (Possibly more, but usually one)
An FTP server requires one port, I believe.
Online games could require a port or two.
.
.
.
Telnet requires just a single port.

Okay, so what could you possibly be doing that would require 20 or more ports to be forwarded?

EDIT: Okay, I just checked my router's forwarding abilities, and it's capable of the following:

Concurrently forward on 15 specific ports.
Concurrently forward on 10 specific port ranges.

So, I can forward a seemingly unlimited number of ports with my router. Assuming that a large number of ports within a given range should be forwarded to a specific IP address, I'm sitting pretty. I can forward 10 port ranges of any size, and 15 single ports concurrently. Not too shabby at all.

lessie... I got 3 OS X boxen, 2 are headless, wanna be able to ssh to any of them... a netbsd box, gotta ssh to that, an XP box (necessity) so... I don't even wanna touch that, gotta have 3389 and 6100 open for that, one of the OS X boxes is an anonymous ftp server, so there's 2 more ports... ah... screw it... heres my export file:
20---------10.0.1.201---------20
21---------10.0.1.201---------21
22---------10.0.1.201---------22
26---------10.0.1.7------------22
28---------10.0.1.2------------22
30---------10.0.1.5-----------22
32---------10.0.1.10----------22
80---------10.0.1.201---------80
311---------10.0.1.201--------311
554---------10.0.1.7----------554
625---------10.0.1.201--------625
687---------10.0.1.201--------687
1989---------10.0.1.201-------80
3283---------10.0.1.2---------3283
3389---------10.0.1.3---------3389
5900---------10.0.1.2---------5900
5988---------10.0.1.2---------5988
6100---------10.0.1.3---------6100
8008---------10.0.1.5---------80
8080---------10.0.1.201-------80

I've got some ports mapped there I don't use much... so at some point I need to do a little house cleaning...

Hmm, interesting. However, doesn't Apple's Airport allow you to forward port ranges?

For example:

I see from your exports file that you're forwarding ports 20,21, and 22 to IP address 10.0.1.201. If you were able to forward a port range, you could forward port 20 to 22 to 10.0.1.201 and save yourself two port forwarding slots.

I notice that you have some redundancy there too. Especially with port 80 on IP 10.0.1.201.

Edit:

Errata
I state above that forwarding a port range would save you two forwarding slots, in actual fact, it will save you three.