Paul,

      Here's one site that gives a step-by-step (note this is assuming you are coming in from a Linux/Unix system - my previous answer was specifically for Putty):

http://www.tecmint.com/ssh-passwordless-login-using-ssh-keygen-in-5-easy-steps/

73,
Eric

WB6PYK

Well, I personally had no luck getting failsafe mode. But, on a long shot I did a 30/30/30 on the router. It rebooted saying the router needed to be set-up, then used  root for user name and what I though I set the password at. The mesh gods blessed me and it work.

So now I'm updating it to bbhn and then I'll start playing with the other router.

Thanks, for the help again

Jason Hopkins

KF4PMY

I just tried this as well.  Same results.  I can SSH in but I have to supply the root login and my node's password every time.  I would like to be able to SSH into the node without knowing the password.

I'm not familiar with linux and just starting out with BBHN and networking in general.  Any SSH tips?

73,

Paul WA2ZE

You haven't done it! Just reset stuff in failsafe mode or tftp firmware back to the router.

OK now I've done it!! I was setting up PuTTy and tried to use it to get to one of my mesh nodes. Well, now, I can't log into the node to setup anything. PuTTy tells me that I have the wrong password. When I go in on localnode:8080, same problem. Tried to telnet to it with no luck (It's a WRT54GS ver2). Is there something else, or should Ii make it a practice target?

Hi Ron, One other statement that I should have added to the end of my last post was that it is the port number (1723) that is important and must remain the same from one end of the tunnel to the other, even though the IP's can change as the tunnel passes through routers etc.

If you want to try something that is very useful when getting your mesh network tunneling operational; try forwarding ports 8080 and 1978 inside the meshnode. On the Setup/Port Forwarding screen, setup port forwarding for Interface:Both, Type:Both, Outside Port:8080, LAN IP:localnode, LAN Port:8080.

Now you can be anywhere (even in a Tim Hortons) and access your node via this "internet back door" by using the URL from DynDNS port 8080. If you know the node password you can even access the Setup screen and reboot the node.

If you also do port forwarding (to localnode) on port 1978, then you can also see the OLSR screen. Again use the DynDNS URL with port "1978/all".

73

Hi Ron, like I said, I'm no expert but my understanding of how the tunneling scripts work is like this:

I could start by saying that my computer I'm typing this on has an IP (from my internet router) of 192.168.2.15 - so how can I be on the "internet" with this IP?

Take a look at my document in the S51tun file for ve3rrd-shack. This node is configured for 3 separate tunnels and in the section called # IP handling, there are several variables which are used to store the IP's (both public and LAN). For example ip0 stores the IP for port eth0.1 which is the WAN port of the mesh node (and in my case will have an IP of 192.168.2.36 /24). Variable ip1 stores the public/external IP for node ve3rrd-portable1 (which was obtained from my DynDNS account).

Now if you look at the section # Tunnel to ve3rrd-portable1.ham-radio-op.net, the first line adds tun1 with a local (node WAN port) IP of variable ip0 and a remote (external/public) IP of variable ip1.

So the IP's used in the node (192.168.70.1, 192.168.80.1 etc) are only to keep track of things inside the node, and the IP's used by my internet router (192.168.2.36, 192.168.2.15 etc) and only to keep track of things inside the internet router. The tun1, tun2 etc. GRE tunnel connections (via port 1723) are from my internet router's external/public IP to the external/public IP of the node at the other end.

Hope I got that correct. 73

I'm still confused and need help with explaining what subnet mask to use in our Internet routers. Al-VE3RRD mentions that his router issued his mesh an IP 192.168.2.36 subnet mask 255.255.255.0. This means that the router is issuing IPs in range of one class C network: #2 (X.X.2.X). So how is traffic on the tunnel IP 192.168.80.1 & 192.168.80.2 get routed out of the Internet router when it's on a different class C network: X.X.80.X. The Internet router is only going to handle traffic on it's own X.X.2.X. network. Hence, why I thought the Internet router's subnet mask needed to be changed to 255.255.0.0 to handle this. Johan's document makes no mention of what IP his Internet router is issuing, only that it's a  static IP,  so I couldn't determine if his Wan IP is the located on the same tunnel class C network of X.X.1.X.

Or should  I make the deduction that GRE 47 protocol handles this?

We've also downgraded our tunnel routers to V0.43 and unfortunately, one got bricked during the downgrade. Luckily we had a spare at the other and and got it configured. Thanks for being patient during my learning curve.

I agree that is strange. But I have seen a straight "ad-hoc" connection to a mesh node's SSID work intermittently. I suspect that OLSR did not come up and that might be what you have and why no nodes are showing. Can you ping everything on your mesh? Or just the strongest neighbor?

It might be useful to see a screen shot of the Routes and Settings tabs in OLSR Switch as well as the output from route -print and ipconfig /all.

You can write me at kv4pc@qsl.net if you would rather not share with the everyone.

73;

Bob KV4PC

OK, now here's where it gets WEIRD.   I am connected to the BBHN node  and have FULL internet access with DNS working just fine. (yes my mesh is normally internet connected)

The odd thing is, the OLSR Switch shows no nodes at all....

What the heck??

Look at this screen shot.

Attachments
 bbhnw5lmm.jpg [190 KB] ::

Hi,

I have import project HSMM-PI for RasberryPI  to my UBUNTU linux on laptop and it is look working scanning and configuration. I will try to use this on my latop to connect with my WRT54 HSMM.

I have attached screendump from HSMM-Linux on my UBUNTU

73 Waldek sp2ong

Attachments
 hsmm-linux.jpg [70 KB] ::

FWIW, i did a presentation on BH last month at the WTARS meeting.  We got at least two stock routers flashed for Madison County ops that evening, we would have got a 0.4.3 upgraded if the op had remembered his password. 

OFDM is permitted on 70 cm because it is an "Image Emission".

[From http://www.ntms.org/802.11/ARRL Board of Directors 2005.doc ]

OFDM Can Be Classified as an Image Emission

John Stevensen, KD6OZH in 2005 began development of a HSMM Orthogonal Frequency Division Multiplexing (OFDM) Modem that will allow Radio Amateurs to have all –mode voice, text, data, and video (i.e., multimedia) high-speed digital communications on the VHF, UHF and SHF bands. Alpha testing of the OFDM modem was done in Texas using an ATV channel in the 70cm band operating in a digital “image mode” coined Amateur Digital Video (ADV).

In a January 2005 report to the ARRL board of directors, the HSMM Technology Task Force submitted the following concept as basis for such a 70 cm OFDM modem capable of Amateur Digital Video.

The 70 cm band is ideal for HSMM and, using the following interpretation of FCC regulations, we should be able to use OFDM modems with an occupied bandwidth up to 9 MHz (at least) on the 70 cm band. HSMM would be classified as an image emission type. This interpretation also allows 6 kHz (or more) bandwidth OFDM modems on the MF and HF amateur bands.

In 47 CFR 97.315 the emission type "image" is defined as including "emissions having B as the first symbol; 7, 8 or 9 as the second symbol; W as the third symbol".

In 47 CFR 2.201 (c) (2) a first symbol of B defines the type of modulation of the main carrier as an "emission in which the main carrier is amplitude-modulated (including cases where sub-carriers are angle-modulated) with independent sidebands". The OFDM modem fits this description as it has a central carrier with multiple subcarriers in the upper and lower sidebands that are angle (phase) modulated. In 47 CFR 2.201 (d) (5) a second symbol of 7 indicates that the nature of the signals modulating the main carrier are "two or more channels containing quantitized or digital information". 47 CFR 2.201 (d)(2) and (3) indicate that time-division multiplex is excluded for a single channel so the time division multiplex inherent in HSMM communications creates two or more channels. In 47 CFR 2.201 (e) (8) a third symbol of W indicates that the type of information to be transmitted is "a combination of the above" and that includes (4) "facsimile", (5) "data transmission, telemetry and telecommand", (6) "telephony" and (7) "television". HSMM fits this definition as it includes data, speech and image components.

In 47 CFR 97.305 "a station may transmit the following emission types on the frequencies indicated, as authorized to the control operator, subject to the standards specified in 97.307(f) of this part". The following table includes the "image" type for all bands and references 47 CFR 97.307 (f) (2) for the 160 m through 1.25 m bands but does not reference it for the 70 cm through 1 mm bands.

This is the only restriction on the image emission type and states that "the total bandwidth of an independent sideband emission (having B as the first symbol), or a multiplexed image and phone emission, shall not exceed that of a communications quality A3E emission". I can't find a definition for "communications quality" but it seems to be taken as 3 kHz on the MF and HF bands.

Thus OFDM modems using 6 kHz or less should be authorized on 225 MHz and below and OFDM modems with no bandwidth restriction on 420 MHz and above. If the emission must fit within the bandwidth used by existing analog image communication devices, that bandwidth would be 9 MHz for DSM AM ATV with a 4.5 MHz sound subcarrier.

Hi all, looks like I'll be checking in on this forum along with following the Western KY folks on Facebook.

Here in Martin (Weakley County) TN, I have six BHv1 nodes set up.  I have two "robo-cams" that can go online as advertised services so remote users can control pan and tilt, and the gateway "service" node has a NAS with two 32G USB drives attached for filesharing.  The gateway also has a RasPBX with 3-digit internal dialing and a Google Voice trunk for PSTN access when online.  Outside inbound callers reach an auto-attendant which offers single-digit access to a particular node, each node has voicemail that can take a message when busy or unattended/offline.  When no internet connection to the gateway is available the PBX will act as a simple intercom for the phones at each node.

Antenna-wise, I currently have two 8dBi and three 12dBi mast-mount omnis, along with a 7dBi mag mount for a "mobile rover".  For a straight-line hop deployment, I have four 14dBi "backfire" yagis and four 24dBi parabolics.  Of course the antennas can be mixed & matched as the incident requires.

Power is through buck converters so theoretically I can put 8-24VDC into the PowerPole inputs and get a stable 12V or 5V out to the hardware.  I still keep the AC wall-warts labeled and in the bag if needed.

Although everything has been tested inside using the stock ducks, nothing is outside and "live" at this time.  I'm in a rural area where the trees are taller than the buildings and I haven't found anyone yet that's willing to offer 300' tower real estate for a $20 router. 

Field-expedient masts and coax will be my final purchases, got to get through the holidays first.

73!

Anyone who understands mesh radios can connect to our networks. As radio amateurs we are not allowed to use cryptographic means to secure the OLSR protocol which is the only method I am aware of available.