Airport Config Utility not port fowarding to 10.100.x.x

[MediaScape]

I can't get Airport Extreme Configuration Utility to allow port forwarding to a 10.100.1.1 IP address? I see that it can forward to a 10.0.x.x IP but couldn't find a solution for the 10.100.x.x.
I need to forward port 2198 & 2199 to a DLink DIR-628 router (IP addr:10.100.1.1) that I've setup within the Airport Extreme network. I've set this "nested" network to control a Niles audio system via an Elan Home Controller to get iPad control of the audio system (complicated story since the Niles/Elan integration and setup is a little kludgy but needs the setparate network and managed switch to get control).
Any help would be greatly appreciated.

[cpragman]

Per the internet addressing scheme, the address ranges 10.0.x.x and 192.168.y.y are considered "private", for your use within your own network. The address you want to use (10.100.x.x) does not fall within this "private" range. If your router is refusing to let you map to this address, it is probably trying to protect you from screwing up the internet. That address would correspond to some "external" address out on the internet somewhere, for which you are not the owner.

[MediaScape]

A little more info:
I need to forward port 2198 & 2199 to a DLink DIR-628 router (IP addr:10.100.1.1) that I've setup within the Airport Extreme network.
I've setup this "nested-DLink" network to control a Niles GXR 16 zone whole house audio system (that uses the 10.100.0.x range of IP address for ip control of it's devices <i.e. touch screens, remotes, etc.). An Elan Home Controller allows iPad control of the Niles audio system network, and I need the port forwarded so an iPad can communicate “down” to the nested network to control the audio system.
The Elan/Niles/iPad/Dlink network setup has been tested as is and works great. Now just need to allow iPad to talk to the nested DLink network when it's using the WiFi of the Airport Extreme network; thus, the need to forward the port to the DLink network in the Airport Extreme. (complicated story because the Niles/Elan integration, and setup, needs the separate network and a managed switch to get control and not interfere with the other networks).

[trevor]

Quote: Originally Posted by cpragman Per the internet addressing scheme, the address ranges 10.0.x.x and 192.168.y.y are considered "private", for your use within your own network. The address you want to use (10.100.x.x) does not fall within this "private" range.

Not true. The private address range that you're both referring to is 10.0.0.0 to 10.255.255.255. 10.100.x.x is within the private address range.

Cite: RFC 1918 is the document that sets the standards for IPv4 private address ranges. It says:

Quote: Originally Posted by RFC 1918 3. Private Address Space The Internet Assigned Numbers Authority (IANA) has reserved the following three blocks of the IP address space for private internets: 10.0.0.0 - 10.255.255.255 (10/8 prefix) 172.16.0.0 - 172.31.255.255 (172.16/12 prefix) 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

Trevor