If you want to use just linux SSH, you need to do it:

ssh -p 2222 node-name-or-ip-address

Hi Pete,

As I understand the HSMM-MESH firmware, it does not operate in a way that changes it from a part 15 device to a part 97 device. The device is using power output that is available to both part 15 and part 97 devices. Furthermore, the frequencies are also available to part 15 and part 97 devices. The operator of the device can choose to operate under part 97 rules by increasing the output power via an amplifier or using higher gain antennas.

If my understanding is correct, than an operator of a HSMM-MESH devices does not need to use a callsign for the SSID unless he/she chooses to operate under part 97 rules by increasing power and/or gain.

My supposed "understanding" is what prompted my original post. I want to make sure I really understand how the HSMM-MESH device operates and that I don't violate any FCC rules. With that in mind, please correct me if I am wrong.

Thanks,

AC7BR

I am new to hsmm-mesh.  I followed the irc server installation instructions successfully until I got to the server configuration section.  I've never done ssh before, so I just jumped in and tried to connect via a terminal window (Ubuntu 10,04 LTS) and ssh (ssh 172.27.0.1).  I get a "Connection refused" error.  After reading some of the OpenWRT docs, I tried putty, with the same results.

I need some assistance with making a telnet or ssh connection to the hsmm router.  I have the PC attached to one of the router's LAN ports.

Thanks for any assistance with this aggravating problem.

Regards,

Dale.  KG5LT

I have my .ssh/id_rsa.pub file installed on several mesh nodes. From my linux laptop, I can ssh into any of the nodes, and it succeeds without asking for a password. But, if I try to ssh again, from a mesh node into another mesh node, it does query for password, i.e. it appears that ssh-agent forwarding is not working.

After Google searching, I see that dropbear version 0.52 is supposed to support ssh-agent forwarding, but there may have been a bug which was fixed in 0.53, and 0.55 is the latest version. The dropbear included in hsmm-mesh 0.4.2 is version 0.50. I also found http://wiki.openwrt.org/inbox/replacingdropbearbyopensshserver which suggests using openssh-server instead of dropbear.

Is a prebuilt binary of dropbear 0.55 available? Should I try to build it? Should I try using openssh-server? Any other suggestions or information?

- John AC6SL

Hi Pete,

The issue of sending a call sign really doesn't have any effect on Part 15 vs Part 97 operation in my opinion. A part 15 user can pick absolutely any SSID that they wish, including an amateur radio call sign to which they have no claim. There is nothing in any part of the FCC regulations that prohibits such use. The fact that this is used to facilitate our need to identify a Part 97 device is incidental to the discussion unless you could prove that the Part 15 person used it for a nefarious purpose to gain access to your station.

To the best of my knowledge. when using an access point that has been flashed with the HSMM-MESH firmware, the channel to frequency correlation is not changed from that of a standard consumer Part 15 device. While it is true that Amateur Radio operators have a primary allocation for channels 1-6, I don't think you will find any sympathy from the FCC for a complaint that a Part 15 device is associating with your Part 97 device. Consider the huge commercial pressure that would be brought on the FCC if they started making such rulings. There is plenty of prima facia evidence, in my opinion, that the FCC is heavily swayed by commercial influences in such cases.

We must also consider that the FCC could actually come back and site that under 97.3(a)(13) that you as the control operator are responsible for proper operation of your Part 97 station and that you have not taken the necessary steps to protect your station from Part 15 devices - particularly since you should reasonably be aware of the potential "interference". They could further point to 97.219(d)(1) and say that you are equally accountable for all messages passed since you didn't authenticate the other "station". A more precedent FCC response could be that in fact your are not operating a Part 97 device but instead it is a Part 15 device for the reasons sited in my earlier post.

The good news is that very few, if any, home users will have installed the OLSR software in their AP. This is the essential code that makes the HSMM_MESH work as a mesh AP instead of a normal AP. Without this installed in their AP, your HSMM_MESH AP won't even recognize their AP. So there is some protection built in through this level of obscurity. If OLSR were to become popular, then a better authentication scheme for HSMM-MESH would probably need to be deployed to meet the authentication requirement of 97.219(d)(1). I say this because simply having a call sign in the SSID of an OLSR enabled AP probably doesn't meet a reasonable test of authentication in that scenario.

- Glenn DJ0IQ and W9IQ

If you have the netbook in DMZ, that means all ports NOT forwarded elsewhere will go to the Netbook.

Then to advertise, on the right side, give it any name you want (this will be seen by others), if it is a web service or something a link could get them to, you click the LINK checkbox, then the next field would be for FTP or HTTP or IRC, (the protocol for that link).

Then after 'unchangeable-node-name:' you put in the port number that service uses (web/http is port 80, FTP is 21, ssh is 22, etc), then if necessary, you can put a direct path to whatever.

for example on mine that I have the IRC server installed:

IRC   (check)   irc  ://K5KTF-USB:    6667    {blank}

which then puts a link named IRC on the mesh status page for that node. When someone on my mesh clicks that link, it automatically opens their IRC client (I use mIRC) and starts the chat session.

 73

KTF

Has anyone built any DIY antenna's?  If so can you post some pictures, hints, prints etc......

Help! I'm very new to this, but absolutely fascinated with the HSMM-Mesh. Here is my scenario:

I have three nodes all running and seeing each other. So far just using three as a proof of concept before I talk others into getting involved. On Node A I want to have a dedicated netbook hosting pictures, programs and files for Node B and Node C to use.  I installed an IP camera and probably more luck than skill got it working across all Nodes. The netbook is proving to be more challenging. So far the Current DHCP Leases has acknowledged my netbook and I see a host name " EeeMINI", IP Adress of 172.27.0.5, and a MAC Address.  I added it to the DHCP Address Reservation.  I then added the "EeeMINI" to the DMZ Server field by the drop down menu. 

This is where I hit a brick wall. How do I advertise the "EeeMINI" to the other Nodes? How do I fill the Port Forwarding fields or do I leave it blank?  How do I fill the Advertised Services fields?  Not sure how to fill the URL field.  Do I have to drill down to the exact location on the hard drive where the files will be located?

I see another topic string on DMZ Server, but just can't make out what to do next. 

Thanks,

Pete