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-devel

Re: [Xen-devel] [PATCH] Add default netmask to vif-nat

To: James Dykman <dykman@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Add default netmask to vif-nat
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Fri, 9 Dec 2005 10:32:07 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 09 Dec 2005 10:33:02 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <OF6E8C33D9.94A31432-ON852570D1.00702119-852570D1.0071B44E@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <OF6E8C33D9.94A31432-ON852570D1.00702119-852570D1.0071B44E@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Thu, Dec 08, 2005 at 03:41:53PM -0500, James Dykman wrote:

> If vif-nat is passed an IP address "10.1.1.27" instead of "10.1.1.27/16", 
> bits is an empty string. This causes a syntax error on 
> line 89 while setting intmask, and another "Hotplug scripts not working" 
> error.
> 
> This patch adds a default value, though a case can be made for removing 
> intmask, vif_int, netmask, and network since they
> don't seem to be used for anything.

Well if they aren't used for anything, let's get rid of them!

It looks like they were needed when we were using ifconfig to bring up the
interface, but since we are now manually adding the routing information using
"ip route", then we don't need them.

Could you submit a patch removing the cruft, making sure that
ip="10.1.1.27/16" and ip="10.1.1.27" both work?  Thanks.  I don't think that
the former is meaningful in the vif-nat topology, but for backwards
compatibility it would be good if both forms worked.

Thanks,

Ewan.

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

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