[Xen-users] Xen and kernel NAT

["Debunk it" <debunkers@xxxxxxxxx>]

Hello,

I'm using my dual homed server not only as a Xen server (currently
with dom0 and dom1) but also as a NAT host. I have an NFS server
attached to eth1 of the Xen server with a crossover cable. Eth0 of the
Xen server has a public IP. I have static assignment for the internal
network (eth1) on the private block 10.1.1.0/24.

My goal is to use the Xen server's dom0 as a NAT host so my NFS server
can access the net (to run debootstrap amongst other things).

NAT'ing works only when I *disable the two bridges* on dom0. I have
two bridges: one on eth0 and the other on eth1. I would like to know
if there are any special PRE/POST routing rules that need to be
inserted before this setup works.

An odd behavior that I've seen is that when I ping an internet host
from the NFS server (10.1.1.0/24) traffic flows out through
Xen.server.eth1 (default gw) and then into vif0.0 (xenbr0's veth0) as
opposed to eth0.

Here are my simple NAT/FRWD rules that only work when the bridges are
brought down:
/sbin/iptables -t nat -I POSTROUTING -o eth0 -j MASQUERADE
/sbin/iptables -A FORWARD -i eth0 -o eth1 -j ACCEPT
/sbin/iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT

I appreciate your help on this. I'm running an unmodified Xen kernel
downloaded from xen.org. LMK if you need additional info.

Thanks all.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users