Hello,
I am going to extend my network adding two new nodes operating at different frequencies and connected in DtD with a 802.1Q GS108E switch.
I can't see in the mesh one of the two new nodes.
I attach some screenshots with some notes.
Thanks for any help and advice.
I3RKE / AC2OG
File Attachment:
https://www.arednmesh.org/content/network-switch-configuration-files
Out-of-the-box the NetGear GS-108Ev2 is a VLAN capable switch.
Out-of-the-box no VLANs are programmed.
It must be programmed to act as a VLAN switch.
How is your GS-108E programmed and are the DtD'ed node's plugged into VLAN ports or LAN ports?
I hope this helps, Chuck
My question is: why can I see the complete mesh with all the nodes connected only if I enter (from remotely) into the node IQ3VV-3 ?
Please observe the attached screenshots.
Major:
First let us fix the 'only as I.P. address' issue.
A Node appearing to its RF and DtD neighbors with only an IP address will not be propagated throughout the network.
This issue is so common that there is a fix in the web interface in recent releases; 3.20.3.x.
Because I see '.local.mesh' in your images, I assume that you are running 3.19.x.x or earlier.
So, the 'web interface' fix may not be available to you, yet.
To fix the 'IP address only' issue, the OLSR process should be restarted.
'ssh -p2222 root@[the IP address of the affected node name]' then enter
'/etc/init.d/olsrd restart'
After the node begins appearing with a node-name, begin testing.
I hope this helps, Chuck
first of all, thanks a lot for your support. My node I3RKE-1 is running the night build version "aredn-1601-d06bbaa-ath79-ubnt-bullet-m-sysupgrade.bin" all the other nodes the version "aredn-3.20.3.0".
I changed the firmware of my node I3RKE-1 under suggestion of Darryl - K5DLQ in order to access the AREDN Global Tunnel Server.
Shall I turn back to aredn-3.20.3.0 version to solve my problem ? I haven't enabled the ssh keys pair so far.
Moreover why the problem is only with the node IQ3VV-3 ? This node is a Rocket M5 2X2 MIMO running 3.20.3.0 and will be used for a link to another mesh 40 Km away.
It worked fine! Thanks for the instructions. Thanks also to Chuck for the support and suggestions.
How to do for closing the deal?
73 de Leo I3RKE / AC2OG
Minor: Not related to your issue
Reference: DHCP Address Reservations/Hostname :: Advertised Services/Name
Although, at present, 'raspberrypi' may be unique in your small network, this standard is not scaleable.
If your network expands and another operator wishes to add a Raspberry Pi service...shall they also call their service 'raspberrypi' ? !!!
I highly recommend pre-pending [callsign-] to every service name.
i.e. 'raspberrypi' becomes 'i3rke-raspberrypi' or 'i3rke-rpi'.
'Sharkrf' becomes 'i3rke-Sharkrf'.
'RASPI-PBX' becomes 'IR3UFR-RASPI-PBX'.
I hope this helps.
Chuck