HostMapping

back to http://scratchpad.wikia.com/wiki/Sasecurity

TableOfContents

* HostOutages * HostMapping1 * VpnIntermeshTunnels * HostMapAndTcpDump * HostAndPortMapping

Hostmapping and StaticIp
See BroadUnblock

Hostmapping and StaticIp
See UnblockNode

MAKE CLIENT IP ADRESS STATIC. StaticIp Make a client meshbox static for purpose such HostMapping a WAN address to it.

Two routes to a gateway
{{{ What happens when there are two equi-distant routes to a gateway? Is it fairly new? If so the reason I can't find it would it be cos were on b25 build 7X (I think)? I take it if you lock to Gateway it stays locked even if that gateway goes down? Or will it search somewhere else of that gateway fails?

you'll probably see some route flap as conditions change over time. For situations where this is a problem (e.g. host mapping), use the "lock to gateway" or "prefer gateway" function.

=
========= If a repeater has a route to gateway A at 3 hops distant, and another route to gateway B also at 3 hops, which one will be used for the repeater's default route? Does AODV/MeshAP use something like signal strength as a tiebreaker? Or is it random?

=
============================= I have had to do something not too dissimilar with a bus information system, where they wanted to control the remote PC's within the mesh. If you are on Skype, you are welcome to give me a call - jonathan_roper - we can post back the success story back to the list once we get it working.

I'm finally getting an idea of what is wanted with the network that has been installed here on the motorway. However, I am not sure that we can offer what is being requested. Let me see if I can express this:

There are 28 meshboxes installed over about 10 miles of road above variable speed limit signs. The internet arrives at various points using fibre across the network, giving us 6 gateways.

At the moment each gateway has a public internet address given by dhcp.

On the same switch is a server, with a static address of 10.1.44.101

On each ethernet port of the mesh nodes sit something called a PLC, which I haven't quite worked out - but I think is part of the sign mechanism. These have static addresses in the same range as the server. They need to be able to chat with the server, and the server needs to be   able to see them. At the moment this is not allowed.

How is the best way to make this happen? I am not sure if we can get to   these PLC's to change their addresses as they're installed on a motorway which, for obvious reasons, is difficult to get to.

Is host mapping the best way to go? I know we can kick 10.1.44.18, for example, to a computer on node 15 say, but if that node thinks it is   already that address is that going to work, or does it have to be in the same range as the meshbox? Can you reverse hostmap too, so that the PLC can see what it thinks is it's server. The effect we need is as if all the boxes were plugged into the same switch?

Is there a way to change the eth address from 192.168.x.x to 10.1.44.x   on the meshboxes and then switch on cross mesh networking?

=
======== }}}