The feature for this is currently in beta.

Keep an eye out for "dtdlink" or "device-to-device linking" 

in the current released version: a node close enough should be able to pickup on the back scatter (same as Linksys) to get the connection via near field energy.

Due to topology we have a couple of clusters of nodes that are isolated from each other. The hardware is Ubiquiti so there is one antenna per node. We can get a signal between the clusters using ptp technology. So how do we integrate a ptp link into another node?

Thanks,

Bernie

Due to topology we have a couple of clusters of nodes that are isolated from each other. The hardware is Ubiquiti so there is one antenna per node. We can get a signal between the clusters using ptp technology. So how do we integrate a ptp link into another node?

Thanks,

Bernie

Hi Jim,

Thank you for your prompt reply.

If I understand you correctly, all I should need to do to connect to the web server on any adjacent node is click the active link for it in the MESH Status view.  So if I am connected locally to KO2F-501 and KO2F-503 is shown as a link in the mesh status page I should be able to click the link and then be connected to the KO2F-501 status page.

I seem to have a problem if this is the case.  Let me investigate a bit and decide whether to continue this thread or open another focused on the problem that I find.

Bob, KO2F

The article "Starting to use Broadband-Hamnet" on this site includes the following statement:

You don't need to physically attach to a given mesh node to make changes to it. You may "remote in" to configure it from anywhere on the mesh network

I have searched the forum, but haven't found anything that indicates how this is done.

Can anyone offer any guidance on this topic?

If it has been addressed in another topic, I would be grateful for a link or pointer.

Bob, KO2F

Scratch that previous version.

I can't say that I've run into that before.  When you get a connection refused, have you gone back to the node that's running the IRC server and verified that 'ngircd' is still running?   I can't vouch for that 15.2 version working correctly. even on the Rocket, as I have ZERO experience with it.

The firewall on the PC shouldn't be of any concern unless it is blocking outgoing traffic to port 6667 on the remote host.

Thank you Conrad,

I checked the network settings, issued the firstboot command and rebooted the Bullet.  It came back up and I was able to connect and rerun the setup sequence with no problems at all.

I will add this to my recovery bag for the future.

Bob, KO2F

After mount_root. You can look at /etc/config/network to see what the settings will be on reboot.

just run "firstboot" and restart the node to restore the node to "just flashed" default ( removes any new programs and config changes )

I successfully loaded one of my Ubiquiti Bullets and managed to subsequently save a bad NAT configuration with DHCP turned off.  I can still see the node from the RF interface, but I apparently fat fingered the static IP LAN address.  The combination of not knowing what LAN address was actually saved and  DHCP being turned off is effectively preventing me from accessing the web page interface.

Not my best move, but this where I'm at for the moment...

I read everything that I can find searching the forum and I have managed to boot my bullet into recovery mode.  I can mount_root and then issue a ls command to see the file structure.

Is it possible to issue some sequence of commands at this point to reset the bullet configuration back to a point where I can connect to the web interface?  Or, perhaps determine what the current LAN address and  net mask settings are?

Bob

KO2F

I have a small problem. I was given two Cisco IP phones (7961 & 7962) for Raspbx attempt.

I followed the Cisco instructions to reset the phones. Hold down #, plug in phone, hold the # till the line indicator light start to flash, enter 123456789*0#, it displayed "upgrading" so I left the phone to do there thing.

When I came back later last evening (9PM) the phones now appear to be DEAD! Nothing on the display, when you apply power the Headset, Mute, and Speaker lights flash. Then everything goes dead.

Any suggestions?

I am trying to remove the HSMM-MESH firmware from one of my WRT54GS version 4 routers to reuse it with DD-WRT.

I have followed the steps referenced in another post in this area.

Go to SETUP>ADMINISTRATION>CHOOSE FILE>UPLOAD but when the upload finishes, it responds with "Firmware CANNOT be updated, the uploaded file is not recognized>

File I am trying to install is dd-wrt.v23_wrt54gs.bin

Any ideas?

On one end we have a TP-Link dish with a Ubiquiti M2HP bullet
(Schunnemunk:  41.378944 -74.136688). On the other end we have a 15dBi Outdoor
Omni-directional Antenna with another Ubiquiti M2HP bullet.
It gets 100% signal strength.

steve