Guru, we tried with a single client and did not see the source port translation
happening. As you suggested, we will try it with parallel connections and let
you know what we observe.
Thanks
On 11/6/17, 7:19 PM, "ovs-dev-boun...@openvswitch.org on behalf of Guru Shetty"
<ovs-dev-boun...@openvswitch.org on behalf of g...@ovn.org> wrote:
I guess, I did not read the original question carefully. I would imagine
that we do port based SNATting, otherwise there would be conflicts. Have
you tried doing parallel connections with the same src port but different
source IP address?
On 6 November 2017 at 19:12, Guru Shetty <g...@ovn.org> wrote:
> We don't have that feature.
>
> On 6 November 2017 at 18:53, Ritesh Rekhi <ritesh.re...@nutanix.com>
> wrote:
>
>> Hi Guru,
>>
>> Thx for the reply , load balancer can change the dest port if directed to
>> a single ip.
>>
>> The use case we are looking for is PAT where a whole subnet can go to
>> internet using same IP .
>>
>> Thx
>> Ritesh
>>
>> Sent from my iPhone
>>
>> On Nov 6, 2017, at 5:56 PM, Guru Shetty
<g...@ovn.org<mailto:g...@ovn.org>>
>> wrote:
>>
>> You can use load-balancer with a single destination to achieve port
>> NAtting.
>>
>> On 6 November 2017 at 16:39, Manoj Sharma <manoj.sha...@nutanix.com<mail
>> to:manoj.sha...@nutanix.com>> wrote:
>> Hi Guru, Mickey,
>>
>> Does OVN currently support PORT based SNAT? By looking at the code in
>> ovn/lib/actions.c, it seems to be doing only IP based NAT.
>> Can you please confirm?
>>
>> This is the NAT table entry:
>>
>> ovn-nbctl lr-nat-list R1
>>
>> TYPE EXTERNAL_IP LOGICAL_IP EXTERNAL_MAC
>> LOGICAL_PORT
>> snat public_ip
192.168.1.0/24<https://urldefense.proofpoint.com/v2/url?u=https-3A__urldefe&d=DwIGaQ&c=s883GpUCOChKOHiocYtGcg&r=9SN4tlEcxQzh-CvuC81YSi9I6ERNBOWQbg-05pnXlNw&m=1h3810lD3pTH_ZsKxW6X0ojF5Ml3hg3Rs98quXdqd9I&s=ObcM8PNKhIOLpRiDQfI2TGHkxfYOfAtZgU0iSadaZls&e=
>> nse.proofpoint.com/v2/url?u=http-3A__192.168.1.0_24&d=
>> DwMFaQ&c=s883GpUCOChKOHiocYtGcg&r=tS71hH9ZpgeYuaCp3UYeWhphNU
>> WUM294zNruMiZ86oA&m=MhrEKKl6awcvFeJUEtRr9oLd3f74WvM1H-
>> 28zF00BCM&s=j2p_B4NvYyNR4YDDV-vQSn997P7OtyALvQoKeBpjfoM&e=>
>>
>> When a VM in subnet
192.168.1.0/24<https://urldefense.proofpoint.com/v2/url?u=https-3A__urldefe&d=DwIGaQ&c=s883GpUCOChKOHiocYtGcg&r=9SN4tlEcxQzh-CvuC81YSi9I6ERNBOWQbg-05pnXlNw&m=1h3810lD3pTH_ZsKxW6X0ojF5Ml3hg3Rs98quXdqd9I&s=ObcM8PNKhIOLpRiDQfI2TGHkxfYOfAtZgU0iSadaZls&e=
>> nse.proofpoint.com/v2/url?u=http-3A__192.168.1.0_24&d=
>> DwMFaQ&c=s883GpUCOChKOHiocYtGcg&r=tS71hH9ZpgeYuaCp3UYeWhphNU
>> WUM294zNruMiZ86oA&m=MhrEKKl6awcvFeJUEtRr9oLd3f74WvM1H-
>> 28zF00BCM&s=j2p_B4NvYyNR4YDDV-vQSn997P7OtyALvQoKeBpjfoM&e=> sends
>> traffic to physical network, the source IP is getting translated to the
>> “public_ip” but source port is left unchanged.
>>
>> Thanks
>> Manoj
>>
>> _______________________________________________
>> dev mailing list
>> d...@openvswitch.org
>>
https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddev&d=DwIGaQ&c=s883GpUCOChKOHiocYtGcg&r=9SN4tlEcxQzh-CvuC81YSi9I6ERNBOWQbg-05pnXlNw&m=1h3810lD3pTH_ZsKxW6X0ojF5Ml3hg3Rs98quXdqd9I&s=j707BMgxWnEQq52pyTGGi6tbxqiILliFfeX6BERVxdg&e=
>>
>
>
_______________________________________________
dev mailing list
d...@openvswitch.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddev&d=DwIGaQ&c=s883GpUCOChKOHiocYtGcg&r=9SN4tlEcxQzh-CvuC81YSi9I6ERNBOWQbg-05pnXlNw&m=1h3810lD3pTH_ZsKxW6X0ojF5Ml3hg3Rs98quXdqd9I&s=j707BMgxWnEQq52pyTGGi6tbxqiILliFfeX6BERVxdg&e=
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
