Mailing List Archive

-----Ursprüngliche Nachricht-----
Von: Simon Horman <horms@verge.net.au>
> Traditionally IPVS-NAT has worked in the form of destination-NAT,
> that is modifying the destination IP address to that of the real-server.
> This works well for in a wide range of circumstances.
>
> More recently Full NAT support was added. This modifies
> source IP address to that of the linux-director as well
> as the destination IP address to that of the selected real-server.

So the linux-director does not have to be the default-gw for the real-servers anymore with Full-NAT?

> An example of where full NAT may be useful is if a real-server wants to
> access a virtual service handled by the linux-director of the real-server.

Stefan

_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users@LinuxVirtualServer.org
Send requests to lvs-users-request@LinuxVirtualServer.org
or go to http://lists.graemef.net/mailman/listinfo/lvs-users

On Fri, Feb 01, 2013 at 08:18:27AM +0100, Stefan Bauer wrote:
> Dear IPVS Users & Developers,
>
> i followed with much interest the development of IPVS. Thank you for this great piece of software.
>
> Previosly there was a new method introduced - called FullNAT. I can not find much documentations about the differences between NAT and FullNAT.
>
> May i ask you please to point me in the right direction or provide some more informations?
>
> All i found was some docs in Chinese.

Traditionally IPVS-NAT has worked in the form of destination-NAT,
that is modifying the destination IP address to that of the real-server.
This works well for in a wide range of circumstances.

More recently Full NAT support was added. This modifies
source IP address to that of the linux-director as well
as the destination IP address to that of the selected real-server.

An example of where full NAT may be useful is if a real-server wants to
access a virtual service handled by the linux-director of the real-server.

_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users@LinuxVirtualServer.org
Send requests to lvs-users-request@LinuxVirtualServer.org
or go to http://lists.graemef.net/mailman/listinfo/lvs-users

-----Ursprüngliche Nachricht-----
Von: Simon Horman <horms@verge.net.au>
> > So the linux-director does not have to be the default-gw for the real-servers
> anymore with Full-NAT?
>
> Return packets still need to travel through the linux-director

Sure, but this is done automatically as by the SRC-NAT, the real-servers will automatically send the answer to the source back. No need for the real-servers, to have the director as default-gw setup - correct?

Stefan

_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users@LinuxVirtualServer.org
Send requests to lvs-users-request@LinuxVirtualServer.org
or go to http://lists.graemef.net/mailman/listinfo/lvs-users

-----Ursprüngliche Nachricht-----
Von: Simon Horman <horms@verge.net.au>
> > > So the linux-director does not have to be the default-gw for the
> real-servers anymore with Full-NAT?
> >
> > Return packets still need to travel through the linux-director
> > as the Full-NAT as the address translations need to be reversed.
>
> Sorry, I missed your point. As the return packets will be addressed
> to the linux-director I think that you are correct and that a
> default (or other) route via the linux-director should not be necessary.

Thank you. now i have the last piece of puzzle ;)

Stefan

_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users@LinuxVirtualServer.org
Send requests to lvs-users-request@LinuxVirtualServer.org
or go to http://lists.graemef.net/mailman/listinfo/lvs-users

On Fri, Feb 01, 2013 at 08:42:25AM +0100, Stefan Bauer wrote:
> -----Ursprüngliche Nachricht-----
> Von: Simon Horman <horms@verge.net.au>
> > Traditionally IPVS-NAT has worked in the form of destination-NAT,
> > that is modifying the destination IP address to that of the real-server.
> > This works well for in a wide range of circumstances.
> >
> > More recently Full NAT support was added. This modifies
> > source IP address to that of the linux-director as well
> > as the destination IP address to that of the selected real-server.
>
> So the linux-director does not have to be the default-gw for the real-servers anymore with Full-NAT?

Return packets still need to travel through the linux-director
as the Full-NAT as the address translations need to be reversed.

> > An example of where full NAT may be useful is if a real-server wants to
> > access a virtual service handled by the linux-director of the real-server.
>
> Stefan
>
> _______________________________________________
> Please read the documentation before posting - it's available at:
> http://www.linuxvirtualserver.org/
>
> LinuxVirtualServer.org mailing list - lvs-users@LinuxVirtualServer.org
> Send requests to lvs-users-request@LinuxVirtualServer.org
> or go to http://lists.graemef.net/mailman/listinfo/lvs-users

_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users@LinuxVirtualServer.org
Send requests to lvs-users-request@LinuxVirtualServer.org
or go to http://lists.graemef.net/mailman/listinfo/lvs-users

On Fri, Feb 01, 2013 at 05:05:51PM +0900, Simon Horman wrote:
> On Fri, Feb 01, 2013 at 08:42:25AM +0100, Stefan Bauer wrote:
> > -----Ursprüngliche Nachricht-----
> > Von: Simon Horman <horms@verge.net.au>
> > > Traditionally IPVS-NAT has worked in the form of destination-NAT,
> > > that is modifying the destination IP address to that of the real-server.
> > > This works well for in a wide range of circumstances.
> > >
> > > More recently Full NAT support was added. This modifies
> > > source IP address to that of the linux-director as well
> > > as the destination IP address to that of the selected real-server.
> >
> > So the linux-director does not have to be the default-gw for the real-servers anymore with Full-NAT?
>
> Return packets still need to travel through the linux-director
> as the Full-NAT as the address translations need to be reversed.

Sorry, I missed your point. As the return packets will be addressed
to the linux-director I think that you are correct and that a
default (or other) route via the linux-director should not be necessary.

> > > An example of where full NAT may be useful is if a real-server wants to
> > > access a virtual service handled by the linux-director of the real-server.
> >
> > Stefan
> >
> > _______________________________________________
> > Please read the documentation before posting - it's available at:
> > http://www.linuxvirtualserver.org/
> >
> > LinuxVirtualServer.org mailing list - lvs-users@LinuxVirtualServer.org
> > Send requests to lvs-users-request@LinuxVirtualServer.org
> > or go to http://lists.graemef.net/mailman/listinfo/lvs-users

_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users@LinuxVirtualServer.org
Send requests to lvs-users-request@LinuxVirtualServer.org
or go to http://lists.graemef.net/mailman/listinfo/lvs-users