StaticIp

other notes
* IpaddressTomeshbox * BroadUnblock

Clients with a staticIP can only roam within the same subnet.

DHCP and Static IP
DHCP mesh assignmentBR No, you are looking at it the wrong way round. The meshbox is plugged into your ethernet network, and will pick up an IP address via DHCP if you have a DHCP server, or you can decide upon what IP address it has and configure the meshbox with that static IP address. The meshbox routes between the two ranges, not your network. As far as  your network is concerned, all traffic is with the IP address of the meshbox ethernet interface.

from ["DHCP"]

Public IP address
{{{ I suspect by Static IP address you mean a Public IP address. To get this to work efficiently, you need to point the Public IP address (Internet Address) into a Static IP address in the mesh. Each IP address is unique within a mesh, based on the Cell ID. Therefore, if the client has a static IP address, he will be stuck with communicating with the node in the same subnet, thus he should not be able communicate at IP level with any other node.

Local Static IP (192.168.x.x)

If you assign a client a static IP, can they still roam to another AP in their vacinity? I know they will not have internet, but will a static IP keep someone from switching AP's?

At the lower level (MAC) it does not lock him to an AP.

If a stronger signal on the same SSID comes along, then the client will switch to the stronger signal, which can be frustrating, particularly if the user flips between two nodes of broadly equal signal strength, as they get issued a new IP address each time if they are on DHCP, which means short periods of no access. Setting the Client Roaming to Manual helps alleviate this problem, as does careful choice and positioning of antenna, but when the computer is first switched on, you do not have control over which node to connect to on Windows.

Naturally, if the client flips to another node, with a static IP address, then he will lose connectivity.

I seem to remember a posting many months ago, whereby a mesh operator was putting all his nodes on different SSID's so that the client could decide which one to connect to, then using the Mesh with any SSID to make the mesh work, however this brings in a whole other set of issues.

Local Static IP (192.168.x.x) Sorry, I should have clarified more. No Public static ip involved. Only want to know if this locks him to AP?

This depends on how you set this up. I suspect by Static IP address you mean a Public IP address. To get this to work efficiently, you need to point the Public IP address (Internet Address) into a Static IP address in the mesh. Each IP address is unique within a mesh, based on the Cell ID. Therefore, if the client has a static IP address, he will be stuck with communicating with the node in the same subnet, thus he should not be able communicate at IP level with any other node.

If you assign a client a static IP, can they still roam to another AP in their vacinity? I know they will not have internet, but will a static IP keep someone from switching AP's?

=
This depends on how you set this up. I suspect by Static IP address you mean a Public IP address. To get this to work efficiently, you need to point the Public IP address (Internet Address) into a Static IP address in the mesh. Each IP address is unique within a mesh, based on the Cell ID. Therefore, if the client has a static IP address, he will be stuck with communicating with the node in the same subnet, thus he should not be able communicate at IP level with any other node. Hope this clarifies.

If you assign a client a static IP, can they still roam to another AP in their vacinity? I know they will not have internet, but will a static IP keep someone from switching AP's? }}}

ddf d
MeshAP - How to assign a static IP   	PDF   	Print Thursday, 13 May 2004

To establish static settings before you can connect to wiana:

Once booted, login on the console as root user (or SSH in as root) and create a file called /etc/STATIC

It is recommended to use the vi editor for this

create the file like so:

1.2.3.4 netmask 255.255.255.0 3.4.5.6  7.8.9.0

Where 1.2.3.4 is the IP address you want for the meshAP device and replace 255.255.255.0 with your local netmask and 3.4.5.6 with your gateway address. 7.8.9.0 is optional address for the static name server.

IMPORTANT - make sure you end the last line with a carriage return.

Once this is done, issue the command "reboot" and the system should come back up with the static address. You'll want to duplicate the same settings on the wiana management page for the meshap once registered. Issue the command "remotemanagement" to force a connection to wiana.

Configuring a static connection in wiana

Go to bottom right of management page to Core Settings

Enter values in the fields for:

static eth addr: static eth netmask: static eth gateway:

and optionally

static eth dns:

The values in the Wired local 192.168.: section are overridden by the static settings.