Yes, your network should be bi-directional. -- Yakov Zhdanov, Director R&D *GridGain Systems* www.gridgain.com
2015-05-20 14:51 GMT+03:00 Isaeed Mohanna <[email protected]>: > Hi, > As i understood the AddressResolver will allow me to map internal ip > address to external up addresses, however my problem is more vpn related > than ignite i guess since my remote machines cannot access the local ones, > but the local ones can access the remote, so there is no true binding to > make, maybe if i make my VPN network bidirectional then it will work since > ip addresses will be accessible. > Thanks for the help, > Isaeed Mohanna > > On Wed, May 20, 2015 at 12:52 PM, Yakov Zhdanov <[email protected]> > wrote: > >> You can configure AddressResolver. Please >> see org.apache.ignite.configuration.IgniteConfiguration#getAddressResolver >> >> --Yakov >> >> 2015-05-20 9:17 GMT+03:00 Isaeed Mohanna <[email protected]>: >> >>> Hi, >>> I have an Ignite cluster running on Cloud network, I have VPN setup to >>> connect to those machines from my local network. >>> I need to run an ignite client node from my local network throught VPN, >>> however when i start the client node it cannot identify the running >>> cluster >>> on my cloud network and starts a new cluster. >>> I am using TcpDiscoverySpi with TcpDiscoveryVmIpFinder = 10.0.0.2, >>> 192.168.0.2. >>> 192 is the local network, 10 is the cloud network, i can access the 10* >>> machines from 192* through VPN but not the other way around. >>> Is it possible to configure ignite client node with this setup over VPN >>> or i >>> should look for an alternative approach? >>> Best Regards, >>> Isaeed Mohanna >>> >>> >>> >>> -- >>> View this message in context: >>> http://apache-ignite-users.70518.x6.nabble.com/Ignite-Client-Node-over-VPN-tp334.html >>> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >>> >> >> >
