[
https://issues.apache.org/jira/browse/CLOUDSTACK-9494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512515#comment-15512515
]
Advertising
Murali Reddy commented on CLOUDSTACK-9494:
------------------------------------------
[~ustcweiz...@gmail.com] Sorry missed your comment.
Yes, i did run into issue.
To start with, 'from all lookup' to the device specific routing table does not
make sense, as there will be ip rules, to explicitly choose routing table based
on 'fwmark'.
Control traffic which is not marked was getting up looked up through the device
specific routing table as well due to 'from all lookup' rule. Prior to 4.6, we
had rules to throw the traffic [1] which was not to be routed by the device
specific routing table.
If you use 'default via' in the device specific routing table, then control
traffic getting routed wrongly.
[1]
https://github.com/apache/cloudstack/blob/4.5/systemvm/patches/debian/config/opt/cloud/bin/ipassoc.sh#L122
> VR ip rules has 'from all lookup' device specific routing table
> ---------------------------------------------------------------
>
> Key: CLOUDSTACK-9494
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9494
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Murali Reddy
> Assignee: Murali Reddy
> Priority: Critical
> Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0
>
>
> From 4.6, VR has IP rules like e,g
> "from all lookup table Table_eth2"
> Device specific table should be used for all the traffic. When we have route
> 'default via gateway' route in the device specific routing table , traffic
> gets routed wrongly on different interface.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
