[
https://issues.apache.org/jira/browse/CLOUDSTACK-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857718#comment-15857718
]
ASF subversion and git services commented on CLOUDSTACK-9770:
-------------------------------------------------------------
Commit 01e78f980bb75cce29e5c78046f33b13b1d65a67 in cloudstack's branch
refs/heads/master from [~rajanik]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=01e78f9 ]
Merge pull request #1929 from ustcweizhou/VR-missing-route
[4.9] CLOUDSTACK-9770: fix missing ip routes in VRIn network VR, the routes to
current subnets are missing in corresponding ip route Table.
It is a typo in commit 6749785caba78a9379e94bf3aaf0c1fbc44c5445
In VPC VR, it works fine.
* pr/1929:
CLOUDSTACK-9770: fix missing ip routes in VR
Signed-off-by: Rajani Karuturi <rajani.karut...@accelerite.com>
> Virtual router / Network regression since 4.9.1.0 with public interface eth2
> ----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9770
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9770
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Virtual Router
> Affects Versions: 4.10.0.0, 4.9.2.0, 4.9.1.0
> Environment: CloudStack with advanced network installation
> Reporter: Milamber
> Priority: Critical
> Labels: regresion
> Fix For: Future
>
>
> I found a (possible) bug introduce by CLOUDSTACK-9339 [1] (Pull Request
> PR1659 [2]) on CloudStack Advanced network installation.
> Since this changes (9339), the public network's route on eth2 (public
> interface) in VR is missing.
> Before on VR, we have sometimes like:
> ip route show table Table_eth2
> 212.217.2.0/24 dev eth2 table Table_eth2 scope link
> default via 212.217.2.1 dev eth2
> ...
> where 212.217.2.0/24 is the public network and 212.217.2.1 the default
> gateway.
> After with 4.9.1.0+ the ip route command shows only:
> default via 212.217.2.1 dev eth2 proto static
> throw 10.230.1.0/24 proto static
> throw 169.254.0.0/16 proto static
> (missing route for public network)
> The changes 9339 introduce the iptables connmark to add 0x2 mark on ip
> packets from internal VMs IP and an ip rule to use the Table_eth2 network
> table for these ip packets.
> So if another machine into the public network try to reach a virtual machine
> inside CloudStack using their public IP, the packets's travel is:
> source_machine--> VR (de-NAT) --> VM_inside_CS --> VR (NAT+using Table_eth2)
> --> default_public_gateway --> source machine
> The issue is if the default_public_gateway refuse to forward IP packets with
> the source IP and destination IP in the same network (often when the gateway
> is a firewall), then the connection between a machine into public network is
> not possible with all VM behind the CS virtual router.
> The correct network path for the packet must be:
> source_machine--> VR (de-nat) --> VM_inside_CS --> VR (NAT+using Table_eth2)
> --> source machine (directly because on public network)
> To fix the issue (workaround), just execute this command on the virtual
> router:
> ip route add dev eth2 table Table_eth2212.217.2.0/24
> Please note: this issue isn't visible on CloudStack upgrade installation from
> anterior version of 4.9.1.0+ until you decide to restart with clean up the
> network in CS.
> What is the best way to fix this bug?
> Thanks
> [1] https://issues.apache.org/jira/browse/CLOUDSTACK-9339
> [2] https://github.com/apache/cloudstack/pull/1659
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
