I tried olsr.restart again and it seemed to work for my node.
Yes, the olsr.restart only affects the node that appears on its neighbors as IP address only.
This function does not affect your neighbors that appear as IP address only on your node.
Now my node host name shows up on my tunnel client's node but his still shows as ip address only. Done multiple rlsr.restart's with no change. Anyone else ever had this problem? Thanks
My Mikrotik hAP all but refuses to broacast its name.
I can spend hours doing 'olsrd.restart's and never get it to display correctly on its neighbors.
:-(
It's the node that appears as IP address only - not your node - that needs to do the OLSR restart. I have a couple of mine that ALWAYS come up as IP only after a node firmware update. Have to restart OLSR on those nodes every time.
Thanks for the info. I have restarted it on both my node and my tunnel node multiple times. Still showing his node as IP only. Not sure what else to try. Not critical I guess but kinda annoying.
You cannot fix their node by restarting your node.
It is the node that is displaying with IP address on its neighbors that must be 'aredn.olsr.restart'ed.
I hope this helps,
Chuck
I don't know if it's relevant, but in my field tests I have noticed that when my node first connects with another, and when the link is weak (too slow or not aligned wel) it will show the IP instead of the host name. As the link quality increases, the host names of neighbors show up. And eventually the whole list of other nodes populates. So, could it be a weak link?
This function does not affect your neighbors that appear as IP address only on your node.
I can spend hours doing 'olsrd.restart's and never get it to display correctly on its neighbors.
:-(
You cannot fix their node by restarting your node.
It is the node that is displaying with IP address on its neighbors that must be 'aredn.olsr.restart'ed.
I hope this helps,
Chuck
Guys, can anyone help me with a Tunnel so I can test my settings?
Thanks
A