Sorry, I should have made it clear that my response was directed toward KE5SWU who asked the original question.  I see that you (KF7RMM) have other intentions for the 44 subnet.  If you have a 44 address, using it on the WAN side of a node is fine, but not having done that myself I do not know how that is done from an internet routing perspective.

73
ad5oo

If you feel you need to be absolutely sure that you're not interfering with ISM... the use of a spectrum analyser would be required to detect ANY signals in the area.   Then again, at the power levels we are generally working with, we'd be hard pressed to interfere with such equipment.

    -Rusty- 

First off, Wikipedia is the last place you want to turn to for quoting FCC rules and
reg's. Yes, I know it's "convenient" but not the definitive word.

Anyhow, if you'll read what I wrote I had no problem with the so-called channel -1
(then again, that would depend on your definition) but(!) you better check your
frequency tables for channel 14 which, according to the IEEE 802.11g standards,
clearly falls above the upper limit of the 13-cm allocation for amateurs (2450-MHz)
as well as the ISM band (2483.5-MHz) for the United States. Please explain how the
standard WiFi channel 14, available only in Japan and is centered on 2484-MHz, is
within the US Ham bands?  Even the low end is around 2472-MHz and still 22-MHz
ABOVE the highest frequency available in the 13-cm ham band.  If you have a different
definition of channel 14 please explain.

>The segment, 2.390 to 2.417 GHz, is domestically allocated amateur radio on a primary basis,

I don't think so since Part 97.303(e) which reads:

"Amateur stations receiving in the 33 cm band, the 2400–2450 MHz segment, the
5.725–5.875 GHz segment, the 1.2 cm band, the 2.5 mm band, or the 244–246 GHz
segment must accept interference from industrial, scientific, and medical (ISM) equipment."

Not sure how you can call that a primary allocation and your Wikipedia quote of 2400-2419 is not mentioned in the current Part 97.

-Rusty-

Thanks for your Reply.

"In the United States, the 13 cm band comprises frequencies in two segments stretching from 2.300 to 2.310 GHz, and from 2.390 to 2.450 GHz[2] The segment, 2.390 to 2.417 GHz, is domestically allocated amateur radio on a primary basis, while the remainder of the band is only available on a secondary basis.[1]" - http://en.wikipedia.org/wiki/13_centimeters

for more information see [1] http://transition.fcc.gov/oet/spectrum/table/fcctable.pdf

My understanding is as a license ham I am granted the right to use any device I want even if that device was released by the manufacturer to comply with part 15. As a license ham I am authorized to modify said device to make it comply with part 97. Channel "Negative 1" and Channel 14 both would fall under part 97.

With Channel "Negative 1" Falling into the frequency space that is reserved for Amateur radio as the primary user. This is why I see Channel Negative -1 Being the BEST? Channel for use in HSMM as the Primary users are Amateur Radio Operators and falls outside of part 15. Channel 14 is still desirable because it falls outside of part 15 although Amateur Radio Operators would be the secondary user.

If you have gone to the effort of being allocated a subnet within the 44.0.0.0/8 space and having made the arrangements with your ISP to have that traffic routed to you, then by all means set up your network to work in that manner.  Keep in mind though that you have taken on a lot of manual configuration and administration, and you are running what is essentially a private mesh.  Nobody else could come within RF range of your mesh and expect to have their node work with yours without it being pre-configured to do so.  HSMM-MESH is not intended to bring inbound Internet access to the mesh, nor is it intended to require nodes to have a specific manual configuration to be able to use the mesh.  Putting a mesh on 44 cannot meet those goals, and there are other mesh network implementations that would be better suited for this purpose.  If you believe that the HSMM-MESH firmware really is the best tool for your job, feel free to use it but please change your SSID along with all the other settings and software that will have to be modified to make a 44 mesh work.

73
ad5oo

It seems like the sweet spot is Channel -1 (2.402GHz) from 2.392GHz to 2.412GHz

and Channel 14 (2.484GHz) from 2.474GHz to 2.494GHz

What Freq/Channels do you use for your Mesh?

What Freq/Channels do you use for your Mesh?

First Answer

For the time being I am assuming I will not be putting anything outside of the private ip address ranges 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 onto HSMM-MESH, that being said the HSMM-MESH would be a isolated network. I don't see a need for NAT in an HSMM-MESH other then it would require less configuration.

I would rather have routing via OSPF routing tables and each node assigned its only private IP address space for devices be hide at. This would require assignment of IP address from some central authority and I do like the idea of wireless mesh nodes being compatible from different home areas with no IP address conflicts(mainly in the event of an Emergency). So the Central Authority could be a dynamic Server(s) or a national/global authority. I personally hate NAT. 

This authority is already in place for the 44.0.0.0/8 space, However that is for internet routable traffic, which would be highly use for in an emergency event. Almost as if the Node themselves could offer two modes of operation normal/private and emergency/public.

With maybe different Central Authority for both for national/global ip address assignment, one for private non-internet/normal mode and one for emergency/public internet mode.

I would also like to state that I am very open to my ideas being wrong, as far as I know it might already be done this way, most likely however it is done now is for a VERY GOOD REASON. At this point I am very much a outsider just starting to look into HSMM. 

How do you plan on handling your routing table? Who will you tunnel to on the 44.0.0.0/8 network so traffic is routing in both directions?