cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Yadav (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-590) Incorrect Network Gateways Assigned to System VMs
Date Thu, 21 Mar 2013 05:47:14 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608664#comment-13608664
] 

Rohit Yadav commented on CLOUDSTACK-590:
----------------------------------------

Yes, this is related to devcloud; we've two interfaces host only (the 192.168.56.x) and nat
(10.0.x.x); it's not really critical but the way devcloud was configured, will see if that
can be fixed. One of my agenda for next week is to refactor the devcloud veewee scripts/definitions
and create a build job, let me try if I can fix this.
                
> Incorrect Network Gateways Assigned to System VMs
> -------------------------------------------------
>
>                 Key: CLOUDSTACK-590
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-590
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, Network Devices, Xen
>    Affects Versions: 4.1.0
>         Environment: Ubuntu 12.04.1, Xen 4.1 running on VirtualBox 4.2.4
>            Reporter: John Burwell
>            Assignee: Rohit Yadav
>            Priority: Critical
>
> When configuring a network with a DNS on a different network, CloudStack creates an incorrect
route for system VMs.  Using the following network configuration, a route between 10.0.3.2
and 192.168.56.1 is incorrectly created:
>    * Management Network: 192.168.56.100-192.168.56.149 gw 192.168.56.1 dns 10.0.3.2
>    * Guest Network: 10.0.3.200-10.0.3.220 gw 10.0.3.2 dns 10.0.3.2
> This configuration will produce the following route table on the SSVM:
> root@s-5-TEST:~# route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 10.0.3.2        192.168.56.1    255.255.255.255 UGH   0      0        0 eth1
> 10.0.3.0        *               255.255.255.0   U     0      0        0 eth2
> 192.168.56.0    *               255.255.255.0   U     0      0        0 eth1
> 192.168.56.0    *               255.255.255.0   U     0      0        0 eth3
> link-local      *               255.255.0.0     U     0      0        0 eth0
> default         10.0.3.2        0.0.0.0         UG    0      0        0 eth2
> It appears that CloudStack assumes a route between 192.168.56.1 and 10.0.3.2 based on
the DNS configuration.  This assumption is false, and not explicitly specified in the configuration.
 CloudStack should defer to the router to make the this topology function.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message