[jboss-jira] [JBoss JIRA] (JGRP-1441) Add external_addr for NATs

Bela Ban (JIRA) jira-events at lists.jboss.org
Fri Mar 23 04:20:47 EDT 2012


     [ https://issues.jboss.org/browse/JGRP-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bela Ban resolved JGRP-1441.
----------------------------

    Resolution: Done

    
> Add external_addr for NATs
> --------------------------
>
>                 Key: JGRP-1441
>                 URL: https://issues.jboss.org/browse/JGRP-1441
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>            Priority: Minor
>             Fix For: 3.0.9, 3.1
>
>
> When NATting between an internal and external network, we can use external_addr, e.g.
> <TCP bind_addr="127.0.4.4" bind_port="5000" external_addr="10.2.3.4".../>
> This means that the looopback address 127.0.4.4:5000 is going to be mapped to 10.2.3.4:5000.
> However, if the internal port is different from the external port, we don't support that.
> SOLUTION: add external_port, e.g.
> <TCP bind_addr="127.0.4.4" bind_port="5000" external_addr="10.2.3.4" external_port="6000" .../>
> Now we're mapping internal port 5000 to external port 6000.
> This needs to be done in TP, FD_SOCK, STATE_SOCK (check if there are more places where we create server sockets)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list