Broadband-Hamnet™ Forum :: Hardware
Welcome Guest   [Register]  [Login]
Joined: 2015-11-29- 18:45:40
Posts: 0

We started with 2 new Linksys WRT54GL routers and loaded the HSMM-MESH 3.2 software per
their instructions on each.
We attached 1 Laptop computer running Windows XP Home and 1 Running Windows XP Media
Center software to one router only. We obtained several IP addresses and wrote them down.
First the IP address of the MESH routers in the format, and these came from the
routers using a browser and the address which brought up the routers set-up page.
We easily found the routers new IP address from those set-up pages, Secondly the address of
each of the attached laptop machines issued by the routers LAN DHCP in the format was found by going into the DOS prompt and running IPCONFIG on each. You
can also find this by looking at the network connections page on each machine. We recorded
the names of the two computers from the Control Panel >System>Computer Name screen on

Here are the applications we plan to run on our server
FTP Server
HTTP/web Server
E-Mail Server
3CX PBX Server

Here are the major applications running on our client machines
FTP client
Internet Explorer
Outlook Express
3CX Phone

We turned off all firewalls on all the computers to simplify our tasks as has been recommended by others.

We decided to start our testing with the simplest piece of software we could find, and we
guessed that a simple FTP server would be the simplest.
We obtained an open software free copy of 3com’s, FTP software and set up an FTP
Damon/Server on one of the machines. We also set up FTP clients on the other machine. Now
recognize that these machines are on the same LAN and have different LAN addresses. Lets call
them and is the machine that we loaded the
Damon/server software. We configured the machine to use and connect to and since they use port 20 AND 21 to send and receive messages, and since we
were outside the firewall on the router, we did not have to port forward anything to anywhere.
We told to connect to As soon as we told it to connect, it did and
we had an FTP link from to and could move files and folders in either
direction. We also moved some files into a shared folder on our Damon/server so that any
machine on the network could come and download it. Why we did this will become evident in
a minute when we go from one computer to a router, then to another router trying to get to
another machine that has what we want.
Now we took a third machine and attached it to the second router. We obtained the applicable and address as before for this router and client machine. We
installed our FTP Client software on this machine. We then went to our first router
( and Port forwarded port 20 and 21 (FTP uses these ports) to (this is
the machine that was running our FTP Damon/server) . Now we told our client machine
attached to the second router to connect to and off it went and connected to our machine (remember we port forwarded ports 20 and 21 to this machine).
Effectively, our third machine got onto the MESH and told everyone that it wanted to send a
message to and use ports 20 and 21 to send the message through. When the
message was delivered to it sent it out on port 21 to over ports 20
and 21 and was listening on port 20 or 21 and received the message. Now is known as the NCC-KC0TGY machine and is known as SPARE-1-
KC0TGY. ( It absolutely makes no difference which comes first the name of the router or the
Ham call sign and I prefer this arrangement.) These names can be substituted for the IP
Addresses whenever you figure you know that it really is working and the DNS facility of the
routers translates the names to ip addresses and gets the messages to the appropriate places
just as fast and accurately. Now everyone knows, (originally I didn’t but it is true), you cannot
send a message to a machine that has not asked for something to be sent to it that is behind a
firewall. This is what firewalls do. They stop unsolicatated messages from coming into your
computer unless you asked someone to send you that information. Going out is OK….. So what
does this really mean? Remember I said we put a shared folder on the machine that has our
FTP Damon/server running on it? That was so one machine can place (upload) a file or folder
onto the FTP server machine, and another machine, far across the mesh can come along and
download it for its use. In fact, a lot of machines can come along and download that file. This is
the way we intend to keep our e-mail and telephone number listings up to date. We will put
the updated files and folders on the FTP machine in a shared folder and everyone will come
along and download it to their desktops, replacing whatever was there and thereby updating
their e-mail and telephone number files.

The process of loading up the HTTP/WEB Server was done the same way. We installed IIS (a
Windows service available on Windows XP Media Center and Windows XP Professional) on our
Windows XP Media Center Machine, and configured it. This was on the server
machine which was on the NCC-KC0TGY node. Everything was easy from here. Our browsers
on our client machines were configured to use for the machine on
the same LAN as the server and (on the client
machine on the LAN on the node) (port 90 was used because the HSMM-MESH™
nodes use port 80 for their HTTP Set-up web pages) as the home pages of the browsers and off
we went with web pages appearing from or

We used the Mailenable free e-mail software and loaded the e-mail server on our server
machine i.e. on the node. For the client machine on this LAN we set
the e-mail address to access the machine as the server. We port forwarded port
25 to the server machine. On the client machine we set the address to the node and it sent the message out thru port 25 to our server,

We used the 3CX free VoIP software from 3CX and loaded the server on our server on the node. Now we know that this free software will only allow
four concurrent telephone calls and is only for demonstration purposes, but this is enough for
our demo project. For the client machine on this LAN we set the telephone number to access
the as the server. We port forwarded port 5060 and 5090 to the
client machine on our node, so that the client machine on node can find its way to the appropriate server. We aimed these none local routers to, and everything worked well.

IP Logged
Page # 

Powered by ccBoard