<discussion>
Same logic.
All service names (host names) should/must be unique.
Beginning a service name with your callsign is a good and safe practice.
</discussion>
;-)
Would you like to see some examples?
I only noticed last night when I installed both the iperfspeed and MeshChat ipk.
iperfspeed is easy enough to change but the meshchat uses the service name as the zone so there are multiple on our mesh with that zone name.
Node name, Host name, Service name are 3 separate lists.
The Node name and the Host name must be unique.
The 'Advertised services' name can be common, but if it is a link
it can only 'point to' a DHCP Address Reservation on the (LAN) Host name
on the same device.
Notice that every MeshChat 'Service Name' link 'points to' a different MeshChat server.
I hope this helps, Chuck
Same logic.
All service names (host names) should/must be unique.
Beginning a service name with your callsign is a good and safe practice.
</discussion>
;-)
Would you like to see some examples?
73, Chuck
I only noticed last night when I installed both the iperfspeed and MeshChat ipk.
iperfspeed is easy enough to change but the meshchat uses the service name as the zone so there are multiple on our mesh with that zone name.
73
Jesse
The Node name and the Host name must be unique.
The 'Advertised services' name can be common, but if it is a link
it can only 'point to' a DHCP Address Reservation on the (LAN) Host name
on the same device.
Notice that every MeshChat 'Service Name' link 'points to' a different MeshChat server.
I hope this helps, Chuck
Jesse