WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] nating the bridge

* Lars Wilke wrote:
> i have now a working domU which is bridged into the dom0.
> I have set as gateway the bridge device. So far this works
> i can access the domU from the dom0 (for example using ssh
> or http). The access from domU into dom0 works, too.
> But i can not get a working NAT setup to route the traffic
> from domU into the internet.
> I tried a few variants, switching of tx checks on the
> ethernet device, disabling connection tracking via NOTRACK
> target of iptables etc.
>
> IP forwarding is enabled in the kernel and via echo 1 /proc/...
> all no luck. So i ask you is there somewhere a document
> detailing a debbuging of such an behavour or something like that?
> I looked around for quite a while and tried some howtos, but
> nothing could help to get that beast working.

The ebtables documentation explains at least partially this behaviour.
The traversal of the packages changes when a bridge comes into play.
So i switched to the nat scripts. These works insofar as i can now
ping the world from inside a domU. But things like traceroute and
dns lookups won't work now. These tools just "hang", though a ping
send to my DNS server gets a reply as expected.

I use the standdard MASQ and FORWARD rules setup by the nat scripts.
Has anybody an idea how i could debug this any further?

thanks

   --lars

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

<Prev in Thread] Current Thread [Next in Thread>