Hi,

You cna install OpenBCM software whre you have typical BBS with W0RLI forward via telnet to other AX.25 Packet Radio BBS.  OpenBCM have SMTP/POP3 server and NNTP server. You can get access to OpenBCM via http web browser to read and post or use Mail client like Thunderbird to read and post to OpenBCM via NNTP reader or via SMTP.

I have use OpenBCM on my Raspberry PI and working very nice and I have forwarding with other (stil exist) Packet Radio BBS and local users can connect to my system use different way

http://sp2ong.ampr.org:9080

or via NNTP/SMTP/POP3 via Mail client

You can download OpenBCM from http://dnx274.org/baybox/pages/download.html

73 Waldek sp2ong

scratch that sorry ... I guess I need to pick up a M2 ...

I have a pair of Airgrid M5 (can't remember if they're HP or not) but I'm on a business trp and won't return home till Saturday... will post the board.info stuff here when I get home.

I have a request on the 5GHz Stuff.  Can you set the channel up at around 5.910 GHz 20MHz wide... reason, I live near Eglin AFB and they've asked us to avoid transmitting between 5.65 and 5.90 GHz... I'm probably ok at 5.850 and higher but I'd like to avoid if possible.

Roger that, When I get home I'll investigate , will be Saturday night or Sunday.

Thanks for the quick reply.

Hello Tom,

We are still looking for board.info files from M5 devices in order to add them to the supported device list and bring official support to the 5ghz band.

Please see: http://www.broadband-hamnet.org/hsmm-mesh-forums/view-postlist/forum-37-ubnt-firmware/topic-759-help-us-gather-info-on-ubnt-devices.html#ccbp3366

At the moment the user interface doesn't make any accommodation for the difference between 2.4 and 5.8ghz bands.

If you have a chance to submit the board.info file it would go towards adding support for your device into the next build for both your use and others.

Wondering if anyone has built a mesh-only NNTP presence. NNTP is well suited for decentralized group messaging, Everyone could have a NNTP server OR there could be 1 or 2 on each local mesh area.  NNTP is scalable, distributed and decentralized and for this reason I think it would work well on the mesh.

I've built an email (SMTP/IMAP4) server and NNTP server on a Raspberry Pi and attached it to one of my two nodes.  I do believe we could port a couple of the ham radio related usenet groups onto the mesh, but I've chosen NOT to at this point because I really don't want to rely on the public internet.  Currently have just a few local newsgroups created on it but there are just test articles in the message base.

Anyone else want to try to try and give this a whirl to see if it really makes sense or not? I'm willing to build some IP tunnels through the internet to other mesh areas if there is other interest.

Tom:

Drop me a line at kv4pc at qsl dot net and I will give you the scoop.

73;

Bob KV4PC

Hello Darryl, Bob,

Trying to gauge how much interest there is in mesh in your area. Two reasons... First is my Mom lives in Pulaski, TN not too far away from Huntsville and when I make trips up there I might bring so gear with me to test to see if my portable node would join the mesh when we go to Huntsville... Second, I'm trying to get people interested in my neck of the woods (Panhandle of FL) and there doesn't seem to b a lot of interest. I think I have a couple of takers but we'll see as I assemble stuff...

How did your meeting go on the 30th?

I'm working to roll out Mesh in my area of the NW Florida Panhandle, already have a pair of Linksys configured but also have a pair of Ubiquity Airgrid M5s... Can't remember if I have HP versions of these, but both the Airgrid M5 and Airgrid M5 HP have 32MB SDRAM and 8MB Flash, so I'm going to try to load up the firmware when I get home... I'm currently on a business trip but will attempt to flash this weekend and report back.

73 de n2xu

Tom Cardinal/MSgt USAF (Ret)/BSCS, Security+

Mesh Any One???

The 2014 Utah VHF Society Swap Meet!

 
The 2014 UVHFS swapmeet will be held at the same location as the 2013 swap meet - the Davis County Fair Grounds Building #2

See .gif for map                      DE AF7J

Attachments
 Davis_Fairgrounds_UVHFS_map1.gif [46 KB] ::

Thanks Paul!

The distribution you noted is the one I installed.

I'll work on the rest of your suggestions now.

I appreciate your patience with old guys like me.

73

Fred

Where can I find the RaspberryPi-Asterisk FreePBX Distro that you mentioned?
http://www.raspberry-asterisk.org/documentation/

"Could not Contact Boot Service" Loading App App=Sip.ld Both phones have NO dial tone and " url call is disabled " displays when off hook.
That happens because the phone is trying to contact a boot server for provisioning. This can be reset in the setup menu when the phone is first booting up.

Manual configuration of the phones:
http://www.3cx.com/sip-phones/manually-configure-polycom-soundpoint/ If you cannot see a WebGUI, you will need to upgrade your phone to the latest compatible firmware and BOOTROM too (see the belows).

FTP Server for Files:
You will need to grab the newest firmware and config settings from http://downloads.polycom.com/voice/voip/sip_sw_releases_matrix.html. Place them on the server, and point the phone (configured from setup when the phone is booting) to the FTP server address. It'll help if you could also glance over the Administrator manual for the Polycom devices.

Same rules apply: http://www.broadband-hamnet.org/hsmm-files/ip-phone-files/183-polycom-ip-601-files.html

Hopefully this will get you pointed in the right direction.

Aha DNS suffix setting, That did the trick.

Many Thanks

Rob

Thank you!  I got it back....finally. 

I followed the instructions inserted in your post for "Manual Configuration" as far as setting the IP Address and netmask manually.  (did a search on google to find out how to manually change those).

Then using the second article you hyperlinked to in your response, (ie., connecting a computer to the LAN port on the access point, and then connecting the mesh-node to access point with a CAT 5 via the LAN ports).  Then I was able to pull up the "lost" mesh node and get into it and change it back from an Access Point to a Mesh Node.  At that point, I thought everything was ok.  It wasn't - I had to go back and change the IP Address / Netmask back from the "static" setting to "obtain IP Address Automatically".

I did a search on "How to Assign a Static IP Address" and got instructions on how to do that. 

Took me a few hours to get it - but its done.  Won't do THAT again.  Thanks.

Hello Rob,

Well I am partial to linux myself so you will not see me argue with that suggestion.

the search root is also known as dns suffix.

Navigate to your network connection > properties > tcp/ip v4 > properties > advanced > dns > edit the suffix list or set the default suffix to local.mesh. (DHCP usually does this for you hence why you need to do this manually )

From doing a quick google search for, "HSMM-MESH Access Point," here are the first two returns:

• http://www.broadband-hamnet.org/section-blog/36.html?start=5
• http://www.broadband-hamnet.org/section-blog/36.html

Also, from the help file on the mesh node there is a nifty section that talks about just this:
Mesh Access Point considerations

When a device is configured in Mesh Access Point mode it is essentially 'transparent'. You are going through the device to reach a mesh node, and there is no need to get to the device unless you wish to change its configuration. When the time comes to reconfigure a device in this mode be aware that it is not running its own DHCP server because that is the job of the mesh node it is connected to. You will need some other way to configure your computer's network interface. There are two ways to do this:

• Manual configuration
  Connect only your computer to the LAN port. Set your IP address to 172.27.0.100 and your netmask to 255.255.255.0. No other settings are needed.
• Automatic configuration
  You will need another mesh node that is using NAT mode on its LAN, and using the default LAN IP address of 172.27.0.1. Both of these are required, otherwise this method will not work. Connect both your computer and the LAN of the Mesh Access Point to the LAN of the mesh node.

In this mode the default IP address on the LAN port is 172.27.0.2. After one of the above steps you should be able to send your browser to http://172.27.0.2:8080/. If you used automatic configuration you should also be able to go to http://localap:8080/. Like the name "localnode", an automatically generated name exists called "localap" which is set to the localnode address plus one, but only when the node LAN mode is set to NAT. If you changed the default IP address of a Mesh Access Point you will have to modify these instructions accordingly.

Help!

I switched my Mesh Node to "Standard Access Point" within the "Basic Setup".  Couldn't get it to work so I attempted to connect to my node to switch it back to "Mesh Node" using the "http://localnode.8080" entry and it doesn't work. I tried http://<callsign>.8080 as well and that didn't work either.

How do you get back into Mesh Node from Standard Access Point?  Is it permanently stuck in "Standard Access Point" mode now?

Yes it seems windows will fail on the first dns and not even try the second one!

I tried swapping the DNS order but that did not help, I cannot find anywhere in the network settings to put the 'local.mesh'.

This morning I booted into Ubuntu 13, added the node DNS, added the route and i can also add the 'local.mesh' into the 'search domains' setting which i can't find on windows, i was able to connect via the host names within a few minutes.

I might just use linux, much easier!

73

Rob