Christian, > Christian Huitema wrote: > I don't quite get the point on the handling of > incoming connections The way I understand UPNP is that it will allow the automation (meaning, no manual config of the NAPT box) of: Server1: 192.168.1.10:80 <-> x.y.z.t:81 Server2: 192.168.1.11:80 <-> x.y.z.t:82 Server3: 192.168.1.12:80 <-> x.y.z.t:83 [x.y.z.t is the global public address] In DNS you publish: x.y.z.t server1.example.com x.y.z.t server2.example.com x.y.z.t server3.example.com and you access the servers by: http://server1.example.com:81 http://server2.example.com:82 http://server3.example.com:83 But what would be _really_ cool is if you could do this: Server1: 192.168.1.10:80 <-> x.y.z.t:80 Server2: 192.168.1.11:80 <-> x.y.z.t:80 Server3: 192.168.1.12:80 <-> x.y.z.t:80 ** and ** have the UPNP box select the proper NAT association based on the requests. In DNS you would still publish: x.y.z.t server1.example.com x.y.z.t server2.example.com x.y.z.t server3.example.com _BUT_ you could access the servers by: http://server1.example.com http://server2.example.com http://server3.example.com That's were the coolness is; no stinkin' port number. As mentioned earlier there are some dirty ways to do it (hard state piggied back on DNS requests) and less dirty (!= clean) (decapsulate http host headers). Michel.