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/
Home Products Support Community News


Re: [Xen-devel] Creating Aliases in Domains - Solution?

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Creating Aliases in Domains - Solution?
From: Phil Carinhas <pac@xxxxxxxxxxxxxx>
Date: Sat, 13 Nov 2004 22:56:00 -0600
Delivery-date: Sun, 14 Nov 2004 05:23:17 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <20041112055703.GA31725@xxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-reply: ctlug@xxxxxxxxx
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <20041112055703.GA31725@xxxxxxxxxxxxxxxxxxx>
Reply-to: pac@xxxxxxxxxxxxxx
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6+20040722i
On Thu, Nov 11, 2004 at 11:57:03PM -0600, Phil Carinhas wrote:
>   FYI,
>   This may be known, but I discovered how to create an alias interface
>   for a domain. Using the same gateway as the primary nic
>   doesn't work for a Debian-stable xenU. Using the network number
>   the bridge IP, or the primary eth0 number seems to work ok:
> iface eth0 inet static 
>   address
>   netmask
>   gateway
> iface eth0:1 inet static 
>   address
>   gateway (or .18 which is the Xen0 ip)
>   netmask
  Sorry to respond to my own posting, but I need to correct something:

 The above statements about using the gateway ip in the aliased
interface are plain wrong. You should not have any gateway for 
an alias. The alias forms a bridge-like struct with the primary nic.
Having a bridge inside of a bridge can confuse routing.

 What I did find is that many of the aliased interfaces would not
be reachable from the outside without first pinging out. I tried
a number of things but I finally turned on STP in the bridging
code. That seemed to help. Now all my aliased interfaces are 
reachable without any special provision.

-Phil Carinhas
| Dr. Philip A. Carinhas       | pac(at)fortuitous.com   |
| Fortuitous Technologies Inc. | http://fortuitous.com   |
| Linux Networking & Security  | Tel : 1-512-351-7783    |

This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
Xen-devel mailing list

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