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

[Xen-users] xen 2.0.7 without any physdev eth on dom0

To: "Xen-Users" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] xen 2.0.7 without any physdev eth on dom0
From: "Mathias Diehl" <md@xxxxxxxxxxxxx>
Date: Tue, 28 Feb 2006 18:49:01 +0100
Delivery-date: Tue, 28 Feb 2006 17:38:59 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi List,

after lot's of trial and error I setup three internal networks for LAN, LAN2
and DMZ. All domU's can connect to each other. My two ethernet devices are
passed to a domU.

Well, so far - so good...

But: After all this "netwrking" I did the following:

created another dummy in dom0

        ifconfig dummy4 192.168.3.130 up
        brctl addif brLAN dummy4

Interface came up but ping from domU to dom0 remaind quiet (no tcpdump
output).

Then I tried to activate arp

        ip link set dummy4 arp on

and tcpdump -i brLAN told me "arp who-has 192.168.3.130 tell 192.168.3.1"

Any idea what small detail I missed?

I'm feeling quite close to a solution - but the last step....

btw, there's actually no firewall software running yet (as I'm installing
offline). So any connection should be possible for now.

On my dom0 the "ip r" is:

        192.168.3.0/24 dev dummy4 proto kernel scope link src 192.168.3.130

iptables -L is completely empty

and /proc/sys/net/ip4/ip_forward is "0"

Any idea what small detail I'm missing???

cheers,

mat


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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] xen 2.0.7 without any physdev eth on dom0, Mathias Diehl <=