darn it anyway.........double post

LARRY

Just received a phone call from a friend about my ADA phone adapter

he said V.3 will only allow one thing to be plugged into a Linksys router.

it can be a computer, camera or phone adapter.

he told me "they" determined hooking two or more devices can cause some kind of trouble.

I have two routers so I'll try this out sometime this week

if I feel up to doing anything after I get out of the hospital.

LARRY

On the port forwarding DHCP and services page, add a link for the PI server.

ON the right side of the row, Name Link URL are required.

Make sure the "link" box is checked if you want it to be clickable.

see 2 screen shots in attachments.

73

JIM AG6IF

Attachments
 mesh1.png [34 KB] ::
 mesh2.png [93 KB] ::

Joe the adapter has been "hacked" and worked with V.2

I hate to say I'm not to smart with using any mesh stuff yet

I'm learning but it is hard to teach an old dog new tricks

I'll need the phone adapter and phone and I am also going to be adding a camera

let me do some more testing thanks for the help I'll be back (after my stay in the hospital)

to see if I can get it working.

Larry

Well if you want to give the following a shot:

use vi on the node to edit /etc/config.mesh/dhcp   (vi /etc/config.mesh/dhcp)

scroll down a few lines and make the file look as follows (use the i key to get into insert mode to type text) (your basically adding the two list dhcp_option lines)

config dhcp
option interface        lan
option start            <dhcp_start>
option limit            <dhcp_limit>
option leasetime        1h
option ignore           <lan_dhcp>
list dhcp_option        '121,10.0.0.0/8,<lan_ip>,172.33.0.0/16,<lan_ip>'
list dhcp_option        '249,10.0.0.0/8,<lan_ip>,172.33.0.0/16,<lan_ip>'

config dhcp
option interface        wan
option ignore           1

config dhcp
option interface        wifi
option ignore           1

use escape key then type  wq and hit enter.

After that go to the web interface, setup, save changes, reboot node.

While that is happening go to your control panel, network connections

For the wired and the wireless card go to properties> Internet Protocol TCP/IP (IPV4)  > Properties > Advanced > Uncheck Automatic Metric

Set the Wireless card to say 20, and the wired card metric to say 40.

Save the changes, and reboot the computer

Hint: you just told the computer that you prefer to use wireless whenever possible so now the wireless will be preferred over the wired port. However the change we made on the node for the DHCP file tells your computer "Hey I'm the best way to get to the mesh" 

If you mess up the router you can just press and hold the reset button (assuming it is version 3.0.0 or newer) for 15 seconds and the node will reset and reboot to just flashed status.

Nope,  that would be the comob I run, a Ubiquiti for the device/modem part of it and let it be just a node and add a Pi or similar to be the actual brute force worker for the phone system.

I'm a big fan of run as little on the nodes, let them be nodes and do what nodes do, and let everything else run on some other device.

I have an idea and would like to get a sense as to whether there is interest is pursuing it.  Thus I would appreciate feedback.

The current broadband mesh development effort is based on the use of Ubiquity routers.  While this has served well we are still limited by some of the decisions made by he manufacturer.  For example this limits the ability to access certain ham bands and it limits the available power levels.  In this context would there be an interest in a router hardware platform that would allow Hams to modify the lower level firmware, and to add transceivers for different Amateur bands.  Other capabilities are open for discussion.

I know an experienced hardware engineer who might be interested in leading the effort.  We would need somebody with the skills and interest to write firmware to support the BBHN software.  This could be somebody in your group or somebody else willing to work closely with your group.

Initially the router would be released in a kit form.  Later versions would be fully assembled and have FCC certification.  While the mature versions of the platform would be a commercial product the idea is that there would be documented interfaces to allow for extensive customization.  It could come with the HSMM-Mesh software preinstalled.  The idea is that a Ham could buy one of these units and use it in a plug and play mode or he/she could modify it if she/he has the need and the desire.

The idea is in the formative stages and your input would be appreciated.  What do you see as the demand for such a router.

KD6MZC

I have read what I could find on VOIP, but need some additional advice and counsel.

I have:

Ubiquiti NSM2

Netgear GS108E-NAS

Two Linksys SPA941NA phones

What next?  Can you point me to articles that would get me started?

Vance, KC8RGO 

I deleted all IE files and then deleted them again. Exit and restart IE, It will not connect to localnode:8080.

The AP is using airmax set to AP/BRIDGE, Maybe there is a setting buried in the list blocking the connection?

Next thought.... I started IE and use http://localnode:8080 instead of just typing localnode:8080 as the URL... it worked. So without the http:// IE was kicking of the search setup.

mike

Try clearing your browser cache (or at least closing your browser)  might clear up.

As Andre just pointed out in another post (and reminded me of how often the basics need to be done) you can be surprised what browser can do to muck things up, especially when you been flashing/reflashing/reflashing software.

If I understand your configuration correctly it looks like this:

Home router <-cable-> MESH-node-A <-RF-> MESH-node-B <-cables-> Repeater-site-devices

Comments:

1) MESH-node-A needs to check the box in setup to advertise the internet gateway.

2) The Dstar gateway (configured appropriately and plugged into MESH-node-B) will be able to initiate outgoing internet connections, e.g. aprs reporting.

3) Special port forward settings will need to be made on the MESH-node-A (by hand in firewall settings) to enable incoming connections to the Dstar gateway and other repeater site devices, e.g. echolink, Dstar to Dstar linking, etc. You will need to know how to do this or enlist this expertise.

Joe AE6XE

On a hunch, I tried the CHROME browser and it actually works. I have full access to the MESH nodes and services. Windows and internet  explorer has some setting screwed up.

regards