Just got started with hsmm.  Western PA ARES held a recent install fest and we are very enthused about hsmm.

I've got a question...I'd like to make it easy for other users on the mesh to access an ftp server, so I'd like to advertise it in the mesh status.  Alas, I think I'm following all the steps in the documentation but I can't make the link for the advertised ftp service connect to the ftp server.

Specifics:

   - ftp server is proftpd on Ubuntu Linux.  I can connect through anonymous login both locally and from other machines on the mesh using the IP address of the Linux system.  I can also connect through web browsers on other machines by entering the URL ftp://10.183.250.3 and through old-fashioned ftp via command line.

   - Configured the service to advertise as ftp://W3YJ-2:21 .

   - Configured external to internal port forwarding on port 21.

   - Configured ftp server to run on port 21.

   - Enabled ports on ftp server for passive ftp.

This all sounds to me like it ought to work...what am I missing?

73,

Harry Bloomberg W3YJ

hbloomb@gmail.com

Do you have one or two BBHN nodes?

If you can hit the server from across the mesh via IP, then it sounds like a DNS issue.

Try, from the remote node/PC, ftp://W3YJ-2.local.mesh:21 (type it into a browser/ftp client)

If THAT works, then you need to go into the remote PC, into its networking settings, and add the domain "local.mesh"

In windows, go into Network Settings, Local Area Connection-Properties, Internet Protocol (or IPv4) Properties, Advanced button, DNS tab, and where it says APPEND THESE DNS SUFFIXES (IN ORDER) click ADD, then type in local.mesh and OK all the way out.

THEN try to hit the FTP again without the local.mesh in the URL.

---

When you guys get mesh nodes on Heinz Field, let me know so I can come visit to "inspect the nodes", preferably on a Sunday  ;-) ;-) . Ill wear my #83 Home jersey like I do every Sunday in the Winter ! 

73

Jim

K5KTF

Thanks for the responses.

First, the is a two mesh system, W3YJ-1 and W3YJ-2.  W3YJ-2 is the system with the ftp server and is running Ubuntu.  W3YJ-1 is attached to a Mac running OS X.

Second...both systems can ping w3yj-2.local.mesh by name, so it appears that DNS is working correctly.  However, I cannot ftp through this mesh node.  I've tried this from a web browser and from local ftp client.

Here's the interesting part.  I installed nmap on the Linux system attached to W3YJ-2, and here's the results of the portscan:

hpb@w3yj-Latitude-2120:~$ nmap w3yj-2.local.mesh

Starting Nmap 5.21 ( http://nmap.org ) at 2013-12-06 22:33 EST
Nmap scan report for w3yj-2.local.mesh (10.86.255.64)
Host is up (0.00061s latency).
rDNS record for 10.86.255.64: W3YJ-2.local.mesh
Not shown: 994 closed ports
PORT     STATE SERVICE
53/tcp   open  domain
2003/tcp open  finger
2004/tcp open  mailbox
2006/tcp open  invokator
2222/tcp open  unknown
8080/tcp open  http-proxy

Nmap done: 1 IP address (1 host up) scanned in 18.71 seconds

It looks to me like port 21 is not open on the mesh node that is advertising the service.  Also notice that I was able to portscan by using nthe name of the node.

Does this info help any?  Thanks!

No mesh nodes yet at Heinz Field.  I'm down there on Saturdays photographing University of Pittsburgh football...maybe I'll bring one next season.

I'm attaching a screenshot of how I have the services and port forwarding for node W3YJ-2 configured.  Maybe this will help.

Let's try that again...I don't the the attachment was posted.

Attachments
 mesh_config.png [94 KB] :: Screenshot of node configuration

Try doing an address reservation for the latitude, then after saving that, you should be able to go tot he mesh status with the Mac and you would see a bullet under -2 of whatever hostname you give the Latitude.

Then try and FTP to the bullet'd hostname, NOT the nodename.

When in X-Host Direct mode, you do not need to forward any ports, as Direct mode (default in 1.0.0 now) is what we used to call (and other routers call) DMZ mode, forwarding ALL ports FOR THAT SINGLE IP ADDRESS/HOSTNAME  to that machine.

You really only need port forwarding if you change the LAN mode to NAT (which was default in 0.4.3/previous releases of the firmware), and what I usually change all mine back to, since I am so used to it. But Dave wants everyone to get to learn and know the X-Host Direct mode way of doing things, its usually simpler.

So then, the advertised service would be " ftp://bullet'd hostname:21"

Sorry for the confusion, as I keep forgetting about the Direct mode being default now. Its only been 6 months..... :-)

Pitt is It !

KTF

This is hilarious...I had just discovered what you posted on my own and was about to post it myself!  So yes, this does work.  Attached is my new setup screen.  Thank you!

I gather you live in the Pittsburgh area?  How about sending me an email?  My email address is hbloomb@gmail.com.  Or you can call me on 443.45 PL 100 Hz.

One of my goals it to write some HSMM training materials for Western PA ARES as I've done for NBEMS.  This will certainly go into the training docs.

73,

Harry Bloomberg W3YJ

hbloomb@gmai.com

Attachments
 mesh-config_2.png [84 KB]

Hi Harry,

Glad you got it working!! Its a blast when it all works and you can do some really cool things over it.

Sending email with more details about my current (and future)  whereabouts... Dont want to bore the masses :-)

KTF

I've only recently loaded my mesh, but I believe you have to ADD the DHCP reservation. I see it there in your pic, but it has not been added yet. Click add then save and wait for the confirmation.

Also, I still have to add the port forwarding for IRC to work. The instructions posted here claim? that you do not have to add the port forwarding in BBHNv1. In order for my IRC to work I had to port forward.

"NOTE: I originally released this document prior to v1.0.0 of the BBHN firmware and unaware of the change in default mode to 5-host Direct (formerly DMZ).  Should your node be currently using 1, 5, or 13-host Direct mode (or similar DMZ mode of previous releases) then you are done!  There's no need to "pop" holes in the firewall.  "

Also, the IRC will not file transfer when internet is active because the IRC will use various other ports (Chatzilla ngircd 20.2) that the computer internet connection uses. I'm using an Ethernet dongle to access localnode but I have also used the LAN port on the localnode for internet. Just cant file transfer with internet access enabled.

If anyone has any insight on how to IRC file transfer withOUT internet and node to localnode  BBHNv1 using ngircd/Chatzilla Thanks. I can see both nicks, but the transfers end up on the server sometimes.

How to get into ngircd on router to set config?