You are here

Giving a connected service a name?

8 posts / 0 new
Last post
N3WTT
Giving a connected service a name?

Sorry is this has been addressed before, doing a search of the forum I seen similar topics but nothing quite black and white or if it was explained I did not understand. That said I apologize if it has been asked.

I have a series of nodes set up for testing indoors and currently learning how to use the Areden system. Of my 3 local nodes one has a raspberry pi running a standard web server. Everything works great! all nodes see one another I can connect to any node from another node, as well as connect and interact with my server/service from any node. 

My question is this: Is there a way to assign a name to my service so a user can just type it into the browser url field to connect rather than having to know the ip address  and typing 10.xxx.xxx.xxx/site or clicking on the link from the Aredn interface? It would be so much easier if I told someone (callsign example:) "open your browser and go to http://N3WTT" or "enter N3WTT in your browser or something similar to find my connected service. So does Aredn have a DNS or something similar for resolving redirects maybe?

Thanks in advance!

K5DLQ
K5DLQ's picture
Hi and welcome to AREDN!

Hi and welcome to AREDN!

Check out the documentation on this topic...
https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/advanced_...

in short, add a DHCP reservation for the device, then, create a Service advertisement.
 

N3WTT
Good read! I skimmed though

Good read! I skimmed though the documentation early on but never sunk in. The hostname of the device is what reserves the DHCP? For example my webserver is running on a raspberry pi default name for it is "raspberrypi" (all one word.) Any of the 3 nodes (all connected to one another) I connect to I can access the service by entering "http://raspberrypi.local.mesh/" in my browser.

So I should be able to rename the pie to "N3WTT" and DHCP reserve the name/service and access it at "http://N3WTT.local.mesh" granted the name is unique. While not as standard as www.sitename.com it's miles better than remembering an IP address.

k1ky
k1ky's picture
Be sure to make it a unique name

In addition - you will want to give your devices unique names in order to avoid the possibilty of "duplications" across the entire system as these names can be used systemwide on your MESH network.  If you are part of a larger system, this becomes even more important.  Usually Callsign-devicename or something like that.

N3WTT
Totally makes sense. This was

Totally makes sense. This was something I was intending to test on my little house setup but maybe you have experience already and can save me a step or two? What would happen (hypothetically of course) if two devices/services use the same name? I am sure it would have some sort of negative impact we want to avoid but to what extent?

k1ky
k1ky's picture
Duplicate names

Duplicate service names can yield some very erratic behavior in the listings - avoid this practice for sanity sake! 

N3WTT
https://youtu.be/jyaLZHiJJnE
AK4FA
Rename Host

https://geek-university.com/raspberry-pi/change-raspberry-pis-hostname/
you can change the name on the pi itself and it should register correctly when you follow the above instructions for setting the reservation

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer