ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Petar Shomov <pe...@activitystream.com>
Subject Re: Node discovery behind NAT
Date Tue, 16 Feb 2016 00:03:23 GMT
Hi Valentin,

Well, we can certainly work with this setup. Not ideal but usable ;) Will
look into doing something about UPnP to see if I can make the whole think a
bit more dynamic.

Thank you for your help!

Best regards,


On Thu, Feb 11, 2016 at 8:48 PM, vkulichenko <valentin.kulichenko@gmail.com>

> Hi,
> No, this socket can't be reused. And you're right, server's communication
> SPI can try to establish connection with the client (to port 47100 by
> default).
> If client is behind NAT, you can setup port forwarding on the router. You
> will also have to implement AddressResolver interface and provide it in
> IgniteConfiguration.setAddressResolver().
> For example, assume that server can access the router by IP and
> your
> laptop has address In this case the router should be able to
> forward to And address resolver should
> map to, so that the server node knows which address
> to
> use to connect to the client.
> Will this work for you?
> Actually, I think we should add proper routing for client nodes. This is a
> known issue, I will check if we already have a ticket for this.
> -Val
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Node-discovery-behind-NAT-tp2956p2965.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message