Hi,

Ok I have setup my laptop with linux UBUNTU and OLSR v0.6.6.1 to connect with my WRT54G HSMM Nodes. I have use part of code www HSMM-PI project to show status on my laptop UBUNTU via port 8080 like on WRT54. All working very well and now I can use in my home laptop with WIFI to connect HSMM Network.

I have attached screen dump from my HSMM-Ubuntu status 

73 Waldek

Attachments
 hsmm-linux2.jpg [127 KB] ::
 hsmm-linux3.jpg [69 KB] ::

Really makes sense Johan, thanks. I, know nothing about VPN, and a bit about networking, so I got confused with the different Class C IPs used for the tunneling. Hence, I why I need to read up on GRE protocol and VPN.

At the moment, both routers are still not pinging the other Tunnel IP (192.168.80.1) on one and (192.168.80.2) on the other. I've been running parts of the scripts manually on both mesh routers which deal with assigning and checking IPs within the mesh router and with the IP check at millhill.org server.

Both mesh routers are properly configured, as far as I can tell, responding with the proper IPs on the right Interfaces. The WAN IPs on both mesh routers are updating the DynDNS server correctly after 5 minutes, when I manually put an incorrect IP in DynDNS. So that works fine.

The next thing I will focus on is both Internet router Firewalls. I will be putting both mesh router IPs in the DMZ of the Internet router and see how they react. Hopefully, it's just one or both routers blocking GRE or Port 1723.

Looking at the log files on my Internet router (Internet Sessions) I can see my router sending out a GRE request from my DHCP assigned WAN IP of the mesh router (192.168.1.101) to the outside WAN IP of the remote Internet router (which is listed correctly on DynDNS server). I see nothing in the System Activity log file accept for the mesh DHCP IP assignment.

Next item, to check the logs of the remote Internet router to see what's happening there.

Ron,

The IP addresses for tunneling has nothing to do with the other interfaces except that it will be internally routed through the mesh and through the GRE tunnel.

Seen from a routing perspective you actually must use IP addresses on different subnets to make routing work.

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.