[
https://issues.apache.org/jira/browse/CLOUDSTACK-9244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107359#comment-15107359
]
ASF GitHub Bot commented on CLOUDSTACK-9244:
--------------------------------------------
Github user DaanHoogland commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1352#discussion_r50168987
--- Diff: systemvm/patches/debian/config/etc/init.d/cloud-early-config ---
@@ -1166,6 +1166,9 @@ setup_storage_network() {
}
setup_system_rfc1918_internal() {
+ public_ip=$ETH2_IP
+ [ "$ETH2_IP" == "0.0.0.0" ] && public_ip=$ETH1_IP
--- End diff --
shouldn't line 1195 begone, then? I think it does the same
> Wrong IP routes added to SystemVM when Public IP is in RFC-1918 space
> ---------------------------------------------------------------------
>
> Key: CLOUDSTACK-9244
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9244
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: SystemVM
> Affects Versions: 4.7.0
> Environment: Centos7 Host
> Reporter: Aerts Nick
>
> Even when a public ip is within RFC-1918 space routes to this ip space are
> getting added to the routing table of the systemvm.
> Example routing table:
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 0.0.0.0 10.0.12.254 0.0.0.0 UG 0 0 0 eth2
> 10.0.0.0 10.0.10.254 255.0.0.0 UG 0 0 0 eth1
> 10.0.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
> 10.0.12.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
> 172.16.0.0 10.0.10.254 255.240.0.0 UG 0 0 0 eth1
> 192.168.0.0 10.0.10.254 255.255.0.0 UG 0 0 0 eth1
> This causes the systemvm to be unreachable from within the 10.0.0.0/8 address
> range
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
