This sounds like server load balancing based on URL NAT does not generally get applied by URL.
You might look at the Linux Virtual Server project. http://www.linuxvirtualserver.org/ On 10/4/07, Jeff Stockett <[EMAIL PROTECTED]> wrote: > I was wondering how hard it might be to make vyatta handle something like > this? The scenario is a hosting environment, and rather than running all the > virtual hosts on one server, my customer wants each hoster to have their own > VM running on one of multiple VM servers NATed behind a single public IP. > > I can envision some new rule keywords being required - something like: > > set service nat rule 10 destination port-name http > set service nat rule 10 inside-address-by-host-header "www.hoster1.com" > address 10.0.0.4 > set service nat rule 10 inside-address-by-host-header "www.hoster2.com" > address 10.0.0.4 > set service nat rule 10 inside-address-by-host-header "www.hoster3.com" > address 10.0.0.5 > set service nat rule 10 inside-address-by-host-header "www.hoster4.com" > address 10.0.0.5 > ... > > This would be very useful given the popularity/versatility of virtualization > these days. Thoughts? Where would one go about looking in the code to > implement a feature like this and how hard might it be? > _______________________________________________ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > _______________________________________________ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
