|
hi
i solved the problem by just adding an ipchain-rule:
ipchains -A forward -j MASQ -p udp/tcp -s 192.168.10.0/24 -d 0.0.0.0/0
53
you can modify the 0.0.... part to point to a specific dns. important is
then the netmask /32, not /0. but port 53 for dns. start with porotocol
udp, which works most of the time. tcp is used for larger packets, so
you'll have to add these two protocols. of course, a nameserver must be
specified on the internal servers .. ;-)
but be carefull. running the rc.lvs_nat script flushes all the ipchains!
clemens
Kim Le wrote:
>
> Hi All,
>
> I am able to get LVS up and running using NAT. However I am having small
> problem that hope any of you can help.
>
> To have LVS NAT work for my setup, the server's default gateway need to be
> LVS backend IP address. I configured default gateway using linuxconf but it
> didn't work (didn't see default entry in route table, sync_ack packet going
> out).
>
> I tried: route add default gw my_lvs_address
> and could not see route tabble anymore when I typed route.
>
> I am able to statically configure gateway for on individual client address
> as:
> route add client_address gw lvs_address (this one work)
>
> Have any of you experienced default gateway problem before ? I appreciate
> any help.
>
> Kim
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
