Github user remibergsma commented on the pull request:

    https://github.com/apache/cloudstack/pull/1352#issuecomment-173005222
  
    `cloud-early-config` now logs:
    
    ```
    Not setting up route of RFC1918 space to 192.168.22.1 befause 192.168.23.2 
is RFC1918..
    ```
    
    Routes are not set as expected:
    ```
    root@v-85-VM: # route -n
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
    0.0.0.0         192.168.23.1    0.0.0.0         UG    0      0        0 eth2
    169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
    192.168.22.0    0.0.0.0         255.255.255.0   U     0      0        0 eth1
    192.168.23.0    0.0.0.0         255.255.255.0   U     0      0        0 eth2
    ```
    
    And when it has a real public ip a route is set to the internal gw. That 
functionality still works and didn't change.
    
    ```
    Setting up route of RFC1918 space to 192.168.22.1 
    ```
    
    Routes are setup now:
    ```
    root@v-1357-VM: # route -n
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
    0.0.0.0         x.y.227.1       0.0.0.0         UG    0      0        0 eth2
    10.0.0.0        192.168.22.1    255.0.0.0       UG    0      0        0 eth1
    169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
    172.16.0.0      192.168.22.1    255.240.0.0     UG    0      0        0 eth1
    192.168.0.0     192.168.22.1    255.255.0.0     UG    0      0        0 eth1
    192.168.22.0    0.0.0.0         255.255.255.0   U     0      0        0 eth1
     x.y.227.0      0.0.0.0         255.255.255.0   U     0      0        0 eth2
    ```


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to