Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Outgoing ports on clients should be configurable #6845

Closed
jerrinot opened this issue Nov 24, 2015 · 2 comments

Comments

Projects
None yet
3 participants
@jerrinot
Copy link
Contributor

commented Nov 24, 2015

Right now clients always use ephemeral ports for outgoing connections.

There should be a way to force using specific port numbers - we already have this ability in member configuration.

@jerrinot jerrinot added this to the 3.7 milestone Nov 24, 2015

@sancar

This comment has been minimized.

Copy link
Member

commented Nov 24, 2015

Duplicate Enhancement request closing this one. And setting old one to 3.7
see #6350

@sancar sancar closed this Nov 24, 2015

@mukul4u2005

This comment has been minimized.

Copy link

commented Apr 27, 2016

Hi All

I am excited about this feature, just I want to confirm one more thing like I was thinking to use the endpoint security on server side at map level. Can we able to define the ip with port number in security configuration on server side ?

<map-permission name="test" principal="dev"> <endpoints> <endpoint>127.0.0.1:5704</endpoint> </endpoints> <actions> <action>put</action> <action>create</action> <action>read</action> <action>remove</action> </actions> </map-permission>
Please suggest about that.

Thanks
Mukul

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.