All,

What I am trying to do is set up a Bullet M2HP such that I can specify the LAN IP rather than have the firmware do it for me.

I am integrating the thing into a comm van and I don't want to have to re-engineer the network.

I did try NAT mode which let's me do what I want in terms of the LAN IP but pretty well cripples everything else (show services, etc).

I do have a Cisco router and a Cisco Switch in the van but that really seems like overkill.

I'd appreciate your thoughts.

BTW, the receiver in that Bullet M2 is hot!  Goodness.

Chuck

WB6YOK

NAT mode is going to be your best bet unless you can re-number.

The mesh network needs to be thought of as a mini-internet.

Unless your devices can be on the assigned range generated by the device you need to do some form of NAT just like you would need to do to hook the com-van up to the internet.

The NAT can be either done on the BBHN node, or on a downstream router from the BBHN node (treating the node just like you would an internet provider)

Switching to NAT shouldn't change anything other than the fact that  some services will not work unless you put passthrough entries on the PORTS page for any services you want to run locally and they will be referenced to your node name to access.  This is how the mesh was ran by default up till version 1.0.0.

Using anything outside of the ranges assigned could cause unforseen routing issues across the board.