KB3TAC:

I am very interested in running a chat server. Can't find a way to pm you for assistance. Pm me please n1ahh at ARRL.net Thanks Ron, N1AHH

The article describing the install process for the IRC on the Linksys router says the software can be found in the repository. Where is a this exactly (URL?). 

Thanks, Ron, N1AHH

Simple answer:

Ignore the mesh, it's not relevant to what your planning at first.

Treat this exactly the same way you would for a aprs node that was at someone's house.  Get all that sorted first.

After that than you can look at how to combine the data from each node (the problem here is can you trust all nodes will always have contact. This will be pretty unlikely. You would more likely need a query method from a central node that crawls out and asks the other nodes (or receives pushes and checks for the node not being reachable)

The simple method is configure all field nodes to stream updates to a single central node.  But again that assumes the nodes can reach that node at all times (this is how aprs gateways work currently when they go over the internet) or that they store history for forwarding when they can connect to the central node.

the non central method of this is just to display the aprs position data on each node and that you go to each node and ask it "hey who's here". Some APRS servers may be able to do this already.

Here is my vision.  Don't know if it has been thought of or tried but anyway...

I would like to have the Pi node with the TNC, which I have working, act as an APRS server of sorts.  Then when the mesh is deployed at say a fire the firefighters could be carrying APRS equipped handhelds or mobiles.  A service available on the mesh would allow those in control to see where personnel are located.

Lots of things to do to make it happen and some I don't know how to do. :-)  The idea is to try and  prevent the disaster that happened last year with 16 dead.  I theory it sounds good but implementation is lacking for me.

Anyway, back to dreaming.

Kirk - N6SXR

NanoBridge M5 info:

XM.v5.5.6# cat /etc/board.info
board.sysid=0xe2b5
board.cpurevision=0x00000101
board.name=NanoBridge M5
board.shortname=NB5
board.subtype=
board.netmodes=7
board.hwaddr=002722741B52
board.reboot=30
board.upgrade=150
board.phycount=1
board.phy.1.maxmtu=2024
board.phy.2.maxmtu=2024
radio.1.name=
radio.1.shortname=
radio.1.bus=pci
radio.1.subsystemid=0xe2b5
radio.1.subvendorid=0x0777
radio.1.txpower.max=23
radio.1.txpower.offset=1
radio.1.antennas=4
radio.1.def_antenna=4
radio.1.antenna.1.id=4
radio.1.antenna.1.name=Not specified
radio.1.antenna.1.gain=0
radio.1.antenna.2.id=3
radio.1.antenna.2.name=Feed only
radio.1.antenna.2.gain=3
radio.1.antenna.3.id=1
radio.1.antenna.3.name=300
radio.1.antenna.3.gain=22
radio.1.antenna.4.id=2
radio.1.antenna.4.name=400
radio.1.antenna.4.gain=25
XM.v5.5.6#

Bullet M2 Titanium

board.sysid=0xe2d2
board.cpurevision=0x00000101
board.name=Bullet M2 Titanium
board.shortname=B2T
board.subtype=
board.netmodes=7
board.hwaddr=DC9FDB049109
board.reboot=30
board.upgrade=150
board.phycount=1
board.phy.1.maxmtu=9192
board.phy.2.maxmtu=2024
radio.1.name=
radio.1.shortname=
radio.1.bus=pci
radio.1.subsystemid=0xe2d2
radio.1.subvendorid=0x0777
radio.1.txpower.max=28
radio.1.txpower.offset=12
radio.1.antennas=1
radio.1.def_antenna=4
radio.1.antenna.1.id=4
radio.1.antenna.1.name=Main
radio.1.antenna.1.gain=0
XM.v5.5.2#

Hey there KJ6ETL! KK6INS here.

Just got my node on the air in Fremont and posted to the map! My friend KH2SR also just got a node online in Saratoga and another one recently showed up in Sunnyvale.

Is your node still online? If not fire that puppy back up. I didn't see your node on the map. Could you please post it to the map so other hams know where to aim their antennas?

Use this link to post your nodes location to the map: http://www.broadband-hamnet.org/addmap1.cfm

Don't forget to convince your ham friends and local ham clubs to build nodes and join in on all the fun building the SF bay area BBHN/HSMM-MESH network!

KK6INS here.

I've done my part, my node in on the air and has been posted to the map in Fremont, CA!

Now we just need more hams to get on board with this fun and cool project!

Hi, KJ6ZGJ.

My name is Aaron KK6INS. KH2SR and I have been working on putting up a node in Fremont and Saratoga. The one in Saratoga has one 16db gain directional antenna, one 8.5 db gain omni and eventually a second 15db gain directional antenna. for now my node in Fremont will only have omni directional antennas. However I plan on eventually adding two directional ones as well.

As you can see on the map, we now have our nodes on the air in Fremont and Saratoga. KH2SR has also convinced VE4AAI/W6 to setup a node in Cupertino. We have just started promoting BBHN/HSMM-MESH to some ham radio clubs around the greater SF Bay Area. We have already had a very positive response from several groups and individuals showing interest in setting up nodes to help build a BBHN/HSMM-MESH Bay Area Network.

If you are still willing to put a few nodes on the air in San Jose that would be awesome!

If you also happen to know some other hams or clubs in the bay area that would be interested in participating, please direct them to this website so they can create accounts, join the conversation, and with any luck, set up nodes of their own.

Feel free to follow/join the conversation on this forum thread as well: http://www.broadband-hamnet.org/hsmm-mesh-forums/view-postlist/forum-11-sfbay-area/topic-787-saratoga-fremont-san-jose-mesh-network-plans.html

One thing I like about networks stack.

It's the same with every operating system and device. The only difference is how you input the changes  to do what of want.

Using two DHCP nic will never work by default without more work.

What is most likely happening is you "LAN" nick of your PC is being chosen for getting  to 0.0.0.0(any unknown network) from your local network.

Add a route 10.0.0.0/8 on the allstar PC to go out via the mesh connected port.

The reason it works when your other PC is on the LAN port is because the Allstate PC knows that computers on the same DHCP subnet  can be accessed via the same port rather than going out via the default gateway.

Also see http://www.broadband-hamnet.org/hsmm-mesh-forums/view-postlist/forum-1-general/topic-796-dual-network-cards-in-pc.html

If your going to run dual ports on a single computer you need I consider running fully manual networking as your close to a server environment than a desktop environment at that point and while dhcp makes setup easy it's not intended to solve the problems of multiple ports.

I have a couple of WRT54G nodes that I am getting setup.  One will be the main ‘on air” mesh node.  The other is for me to use for testing, demos, etc…

I currently have a XIPAR Allstar Desktop PC system running Centos and that is one of the things that I would like to access / provide IAX access across the Mesh.  I have a second NIC in the Allstar PC and that NIC is connected to one of the main Mesh node LAN ports.  Let’s call that node “Node 2”.  I have the LAN setting on Node 2 set to Direct.  I have IAX client support setup on the Allstar PC and it normally works fine with the iaxRpt client on other PCs, both internally on the home network and across the Internet.

I have a DHCP reservation for the Allstar PC second NIC on Node 2.  I currently have the firewall off on the Allstar PC for testing purposes.  It is already isolated from the Internet by a router firewall on that side of the other NIC on the home network.

With a Laptop connected to the LAN on my other mesh node, let’s call that one Node 5, I can see Node2 in the mesh status screen on Node 5, and I can see name of the Allstar PC from the DHCP reservation on Node 2.  I can access the web interface of Node 2 just fine across the mesh.  I also have DNS resolution at the Laptop of the Allstar PC across the mesh.  So far so good.

The problem is that I cannot access anything on the Allstar PC across the mesh.  I can plug the Laptop into a LAN port on the Node 2 router, and both IAX and SSH are working fine when connecting to the Allstar PC, so the interface in the PC is working fine and those services are functioning across that interface.  Even though the Help indicates the port forwards are not used in Direct mode, I tried that anyway with forwards configured at the Node 2 router, but still no joy.  I have tried specifying the Allstar PC IP address instead of the DNS name, while attempting connections across the mesh, but still no joy.
I have tried disabling the WAN interface on Node 2, thinking that maybe the router was getting confused, but that did not help.  There is currently nothing plugged into the WAN interface.

What am I missing?

Thanks

Dean  KD4TWJ

"Mode 1 WILL WORK(and it is NOT suppose to allow internet access from wifi UNLESS you check MESHGW checkbox.)) It will let you connect to the local network and internet (assuming your local net is not in the 10.x range).  As this is suppose to allow wired LAN to WAN and WIFI TO LAN but not WIFI TO WAN."

Method 1 wasn't working for me yesterday, not sure why, but pings to the remote node by name were failing. Pings by IP Address were working. Clearly a DNS issue. One thing I didn't try before throwing in the towel on method 1 was to flush the DNS. That's why I tried the configuration with using two wired NICs which didn't work correctly as explained in the first post.

This morning I went back to the method 1 configuration, turned on the PC and now it is working correctly as it should. What I probably should have done was flush the DNS on the PC or at the worst case rebooted. In any case, its working as it should.

Now on to testing connectivity to a neighbor ham who is .8 miles from me. We've ordered high gain directional antennae for the testing. I've had great success with long distance WiFi connectivity using a parabolic antenna. I'm having a great time with this and hope to spur on more interest with the local EmComm group.

Thanks to all who commented on this thread. It is greatly appreciated.

--
Bob
bob@k8nrt.net

A fully DHCP setup will never work with multiple NICS.

The preference will be to use the wired port where possible. DNS priority is indeterminate in this state as wired is considered less cost than wireless.

Mode 1 WILL WORK (and it is NOT suppose to allow internet access from wifi UNLESS you check MESHGW checkbox.)) It will let you connect to the local network and internet (assuming your local net is not in the 10.x range).  As this is suppose to allow wired LAN to WAN and WIFI TO LAN but not WIFI TO WAN. 

Disable your WIFI while plugged in via the wired port in mode 1

Mode 2 is just complicating it

Mode 3 is actually exposing the internet to the mesh