Add the ability to specify hub ip addresses in Hub Mesh

[baconphonemail]

My wife is a medical traveler so we are 'on the road' most of the time for now. I built a road warrior network for our travel location and have an IPSec tunnel running between the two sides. So both my C8pro at home and C7 can talk to each other using a private ip addresses. However they are on two subnets, 10.6.0.? and 10.6.1.? Right now I'm using API calls to do things like sync switches and such between the two.

So I'm asking for the ability to enter the IP address's of the counter part hub in the Hub Mesh feature in order to take advantage of the hub mesh instead of the discreet use of the api calls.

[bertabcd1234]

You could see if this endpoint to set Hub Mesh peers works:

Hub mesh wrong IP

There's an endpoint to set initial hub mesh peers. Now that the issue surfaced again, I'll probably add the to the UI as well. http://hubs.ip.address.here/hub/advanced/setInitialHubMeshPeers?192.168.1.2,192.168.1.3, with comma separated IP address list as a query string. It should say "done" when list is updated. The list takes effect when hub mesh is restarted next time. http://hubs.ip.address.here/hub/advanced/setInitialHubMeshPeers?none resets the list. http://hubs.ip.address.here/hub/adv…

However, if the two subnets aren't in the same broadcast domain (and they might not be if discovery isn't working in the first place), I'm not sure that Hub Mesh would work either way.

[baconphonemail]

Ahh thank you, that worked like a charm... The two hubs found each other no problem..