TwoDomainNetwork has to be public. 
It also depends on what the service VMs are and of what type. 

Regards
-Harshad


> On Nov 19, 2015, at 9:27 PM, Vigneshwaran R <[email protected]> 
> wrote:
> 
> Any Idea on this ?
> 
> 
> 
> Thanks,
> --Vignesh
> 
>> On Thu, Nov 19, 2015 at 3:49 PM, Vigneshwaran R <[email protected]> 
>> wrote:
>> Hi All,
>> 
>> With contrail GUI I have created the service chaining flow like ( 
>> OneDomainNetwork --> svc1 --> svc2 --> TwoDomainNetwork ). From GUI this 
>> functionality is working fine. If I need to connect some external IP to the 
>> OneDomainNetwork to forward all packets from external laptop to OneDomain VM 
>> through service VMs, How can I proceed ?? (I have created the virtual 
>> gateway (vgw1) on compute node for the communication between board and 
>> virtual VMs.) 
>> 
>> From external laptop, traffic comes to eth1 interface of the compute node. 
>> From here how to forward all the traffics to OneDomainNetwork (VM). I have 
>> tried iptables commands but that's not helping. On ( eth0/vhost0 ) interface 
>> of the same compute node public IP is connected for internet access & other 
>> IP access
>> 
>> Expected Result : 
>> 
>> External Laptop --> Board (Compute Node) --> OneDomain VM --> svc-1 --> 
>> svc-2 --> TwoDomain VM (it has Public access)
>> 
>> All traffics from external laptop should follow the above topology.
>> 
>> i) All traffics from external laptop will come to board, since I have set 
>> eth1 address of board as gateway to external laptop
>> ii) But all traffic from board is not going through service chaining flow 
>> even if I set the gateway as OneDomainNetwork. When im pinging it is 
>> directly reaching the VM without the service chain flow through vgw. 
>> 
>> So, how can I set a gateway, so that all traffic from eth1 interface will go 
>> to the initial VM (OneDomain) which I have launched and follow the service 
>> chaining flow ??
>> 
>> Can anyone please help me on this ??
> 
> _______________________________________________
> Dev mailing list
> [email protected]
> http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
_______________________________________________
Dev mailing list
[email protected]
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

Reply via email to