From: Nicholas Lee <nic-lists@plumtree.co.nz>
To: Christian Wicke <xen.christian@safersignup.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Networking problems with debian packages
Date: Sat, 5 Mar 2005 10:15:49 +1300 [thread overview]
Message-ID: <20050304211549.GA18627@stateless> (raw)
In-Reply-To: <200503032214.44684.xen.christian@safersignup.com>
On Thu, Mar 03, 2005 at 10:14:44PM +0100, Christian Wicke wrote:
> > > But I still cannot ping to the domU. After
> > > # xm create -f speedyU.conf
> > > ifconfig shows an interface vif1.0, but nowhere anything with 192.168.5.
> > > (I configured my domU to 192.168.5.2)
> >
> > vif1.0 is just the p-t-p link for the tun device on the host side.
> >
> > Set the ip address in the guest on eth0.
>
> I think I did:
> speedyU:~# ifconfig
> eth0 Link encap:Ethernet HWaddr AA:00:00:75:E8:9F
> inet addr:192.168.5.2 Bcast:192.168.5.255 Mask:255.255.255.0
> # ifconfig vif1.0 192.168.5.1 pointopoint 192.168.5.2 up
> xen-br0 Link encap:Ethernet HWaddr 00:00:E2:7D:84:FA
> inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.255
I think you are confused. Trying to use a routed setup with a bridged
configuration.
Please send though 'brctl show xen-br0'. However I suspect you need to
think like this.
In the bridged setup xen-br0 acts in two ways. As a virtual interface on
the host machine taking over the eth? role of provide an NIC interface
to the application layer. Second, as a virtual switch which other
interfaces on the host can plug into.
vif1.0 should have no IP in a bridged setup. It should only be connected
to the xen-br0 bridge. Packets from eth0 in domU go though the tun p-t-p
tunnel and hit the xen-br0 bridge. So eth0 on domU should be on the same
sbunet as xen-br0 on domO.
Try
ifconfig eth0 addr:192.168.1.100
on domU.
I haven't tested this myself, but I assume in a routed setup vif1.0 and
eth0 are more like two networks cards with a crossover. In this case
you'd ignore the 'pointopoint' part of the configuration for vif1.0.
'ifconfig eth0 192.168.5.2' and 'ifconfig vif1.0 192.168.5.1' would
probably be sufficent. Nicholas
Nicholas
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-04 21:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 11:13 Networking problems with debian packages Christian Wicke
2005-03-03 11:37 ` Leigh Brown
2005-03-03 12:58 ` Christian Wicke
2005-03-03 18:48 ` Nicholas Lee
2005-03-03 21:14 ` Christian Wicke
2005-03-04 21:15 ` Nicholas Lee [this message]
2005-03-05 9:12 ` Christian Wicke
2005-03-05 9:19 ` Nicholas Lee
2005-03-03 16:26 ` Christian Wicke
2005-03-03 17:44 ` Adam Heath
2005-03-04 16:16 ` B.G. Bruce
2005-03-03 14:45 ` Gerd Knorr
2005-03-04 21:22 ` Nicholas Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050304211549.GA18627@stateless \
--to=nic-lists@plumtree.co.nz \
--cc=xen-devel@lists.sourceforge.net \
--cc=xen.christian@safersignup.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.