I have two node stations in operation,  W0AY-1 (resurrected  Linksys) and W0AY-2 (new Ubiquity AirGrid) up and running on 2.4 GHz Ch 1.  The two nodes can see each other and W0AY-2 located on my deck can see stations from the local mesh network.   But, as far as I can tell,  my W0AY-2 (air Grid) didn't join the local mesh.   Why?  Is it because my two nodes SSID as Broadband-Hamnet with version #  and the local mesh ids with an SSID of   HSMM-MESH?  I recall, I think perhaps incorrectly,  that the SSID's of all the mesh members must be the same?   If so,  I can't locate a way to change the SSID because the web interface automatically adds the version number.

Thanks for any help,

73 Larry  W0AY  in the Montana Wilderness

There is a section 97.311 Spread Spectrum (or bandwidth-expansion modulation emissions) which is designated for many bands including 70cm. This does give some precedence for 5MHz+ channels and other 802.11 protocols.

While bbhn may not have any direct control over the 802.11 low levels protocols used, SS is one of them. It seems unlikely that the 97.37(f)(6) intent would apply to 802.11 protocols, because all this language is around symbols at 1200/300 baud.

The ATV channels on 70cm are 6Mhz wide and also sets a precedence on bandwidth usage. Many of these folks are no doubt looking at bbhn and locally have already put a mesh node on the ATV tower.

My opinion is that experimenting with bbhn on 70cm is fully in the spirit of ham radio, BUT as long as the ATV and bbhn folks are talking, getting alone, and sharing the band, there would be opportunity. Let's not go throw up a node and trash a well established ATV used space (well, it's more like ATV will completely trash the low power bbhn).

Locally, Don KE6BXT is working to integrate a VOIP-video device with analog video feeds to bridge the traditional ATV repeater with the local mesh. ATV folks are drawn to video over bbhn...

Joe AE6XE

Yep! It DOES seem like this forum is becoming MY Blog . I forgot to mention that I'm still looking at Web mail as part of the Web page but that still needs to be evaluated. I need to determine if the various offerings have to be kept separate or if I can offer multiple services off a single server on a PI. Interesting project and my little MESH hasn't even gone public yet. Can't wait to register it. And yes, it is indeed "So far so good." My avoiding both Linux and Raspberry (because of Linux) was pretty much based upon a history of disappointments with Linux. It simply did not get along with ME. What the root cause was, I don't know. However, as I said, it's turning out to be much more fun than I anticipated. Howard W6IDS Richmond, IN

As noted, I don't see why it wouldn't run olsr (it would be a wifi card inside Linux same as any other), and even if it didn't support AdHoc it could be used in a AP style deployment for more cord instead nodes.

Big unknown to me is the licensing part.  Perhaps David will jump in as I've seen him talk about them in the past and provide some more information about the licensing for us, as noted it's an area I'm not sure on and have questions about,

I'm not going to say its possible or not as I have not ever had one of these cards in my hands.  The online quick datasheet is a little iffy on if it supports Adhoc mode, but assuming it does, it is an ath5k device which means Linux supports it and that you can build up a computer to run the BBHN protocol across it (Adhoc, OLSRD, etc)  but no build exists for it at this time (and it would be hard to make a dedicated build for it as it is a PCI card that can slip into any computer)

But assuming adhoc mode one should be able to do it I don't see why not.

The next question that crosses my mind is Part 97 licensing on the subject, I'm not going to render an opinion, I'm just going to say I'm not sure if its permitted or not as I've read conflicting information, enough to make me feel to say it needs to be researched more.

I will say i would LIKE it to be permitted as that can clear up some of the NLOS issues possibly better than the 900mhz band does and may open more options.

The parts I believe to be the relevent text from Part 97 is as follows for authorized transmissions on 70cm

Hello,

  Is it possible to run BBHN on 70cm using the Doodle Labs DL435-30 WiFi card?  The Mbps looks to be about 12 with a 5Mhz bandwidth.

--73 de Doug (N1OBU)

N4FWD, The full URL to connect to the ipCam likely requires more information. Here is a guess for your cam:

rtsp://IPC:554/live/play1.sdp (for trendnet TV-IP862IC cam, use play2.sdp, play3.sdp, ... for lower resolutions)

rtsp://IPC:554/live/ch00_0 (for Ubiquiti airCam, use ch01_0, ch02_0, ... for lower resolutions)

Joe AE6XE

Paul, you were correct about needing a second mesh node. As soon as I flashed another node and configured it, the service link appeared.

However, I am now experiencing what appears to be a DNS resolution issue. I uploaded a screen capture. Is there something configurable which I missed? Maybe on the laptop end of the link?

Background: the web browser is configured to start up the VLC program when a rtsp request is handed to it. A direct connection will produce a login request from the camera. Typing in the viewing account (no password) completes the transaction and video shows.

Attachments
 camera.png [35 KB] :: VLC is unable to resolve URL passed to it

Good catch Paul, thanks for the info.

BBHN->ticket:75 has been created for this.

Just found your post from May. I am in the Berkeley hills around 3500 meters NW of you. I have been working with some of the NALCO members to get a small demonstration network up throughout the city. The end goal is for emergency services, but there is no specific plan art the moment as to exactly what that means, or if it even falls under the NALCO umbrella.

I see your Wi-Fi node KJ6DZB_(B)NO more Open use from my station. But, the signal is pretty weak -72db. Right now I am running a Rocket-M2 and a dish antenna with BBHN 3.0.0.

If you have an interest in pursuing this effort let me know in a post or PM.

Richard

The release notes should be able to answer your inquiry.

Do note there is a difference between the M versions and non M versions (we only support the M series)

That link appears to be slightly out of date but it does list the NanoStation M2 Loco.

For the latest supported hardware list I suggest looking at the release notes (available from the firmware download page)

I know about your problem as I have experienced it multiple times before. In fact, I just got finished helping someone else out with this problem earlier. I have identified your problem: You have a one-node mesh. Solution:  The second you add another node to the mesh, the link will become visible for the rest of the network. Until that time happens, you can navigate manually by typing the the link you specified in the setup page in the address bar.