[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] network (NAT?) problem



Markus,

You say the routing of packets between dom2 and dom0 doesn't work as intended - can you elaborate on this, i.e. where do packets get to, do you see them if you tcpdump eth1 and eth0 in dom1?

Do you have any IP tables rules in dom0 that would affect packets on xen-br1?

Can you post the following for all domains:
 - iptables details (both nat and filter tables)
 - routing tables
 - ifconfig
 - cat /proc/sys/net/ipv4/ip_forward

And brctl show for dom0.

Thanks,

James

Markus Lude wrote:
Hello,

my current network setup looks like the following:

    dom2-eth0 (172.30.1.22) netmask /24
        |
        | xen-br1 (no ip)
        |
    dom1-eth0 (172.30.1.21) netmask /24
    dom1-eth1 (172.30.0.21) netmask /24
        |
        | xen-br10 (172.30.0.1) netmask /24
        |
      dom0
        |
        | xen-br0 (normal IP)
        |
       eth0 (same IP as xen-br0)
        |
        |
       LAN

Basically I want to route all traffic between dom0 and dom2 through dom1.
This does work as intended.
I further would like to have access to the LAN from dom1 and dom2 through
NAT in dom0. It works for dom1, but not for dom2. The addresses of packets
from dom2 were not changed (noticed with tcpdump -n -i eth0 in dom0).

In dom0 NAT is set up with:
  iptables -t nat -A POSTROUTING -s 172.30.0.0/16 -o xen-br0 -j MASQUERADE

If I leave out the -s parameter nothing changes.

I'm running debian sarge in all doms and xen-2.0.6.

Any suggestions? What am I missing?

Regards,
Markus Lude


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

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.