HamWAN Getting Started: Difference between revisions

From OCARC
Jump to navigation Jump to search
(Created page with "This is a work in progress == Key Points == * HamWAN Generally requires a direct line-of-site to a sector site in order to function correctly. Unlike more traditional radio c...")
 
Line 11: Line 11:
== What Can Go Wrong? ==
== What Can Go Wrong? ==
* In most cases no permanent damage can be done to the radio, with some exceptions:
* In most cases no permanent damage can be done to the radio, with some exceptions:
** As with most devices there is always a chance that upgrading the firmware could fail, resulting in a radio that will no longer startup. Thankfully Mikrotik offers a recovery mode that can usually fix this called [[https://wiki.mikrotik.com/wiki/Manual:Netinstall Netinstall]]
** As with most devices there is always a chance that upgrading the firmware could fail, resulting in a radio that will no longer startup. Thankfully Mikrotik offers a recovery mode that can usually fix this called [https://wiki.mikrotik.com/wiki/Manual:Netinstall Netinstall]


== Security Considerations==
== Security Considerations==
* HamWAN provides an almost entirely unfiltered connection to the internet. This means it is VERY important to ensure that all equipment connected to the network is up to date including the radio firmware.
* HamWAN provides an almost entirely unfiltered connection to the internet. This means it is VERY important to ensure that all equipment connected to the network is up to date including the radio firmware.
* Our suggested configuration for client radios results in the Radio receiving a public-facing (44.x.x.x) IP Address on the wireless side, this address is fully accessible from the internet. Devices connected to the radio via ethernet will receive private addresses (192.1.88.x) and cannot be directly accessed from the internet. This process is called NAT or Network Address Translation and works for 95% of use cases. If you intend to host services such as an IRLP node where connections from the Internet are required your will need to configure Port Forwarding on the radio.
* Our suggested configuration for client radios results in the Radio receiving a public-facing (44.x.x.x) IP Address on the wireless side, this address is fully accessible from the internet. Devices connected to the radio via ethernet will receive private addresses (192.1.88.x) and cannot be directly accessed from the internet. This process is called NAT or Network Address Translation and works for 95% of use cases. If you intend to host services such as an IRLP node where connections from the Internet are required your will need to configure Port Forwarding on the radio.

Revision as of 04:10, 3 November 2021

This is a work in progress

Key Points

  • HamWAN Generally requires a direct line-of-site to a sector site in order to function correctly. Unlike more traditional radio communications things like trees or buildings will cause significant interference.
  • Not all Mikrotik Radios can be used on the HamWAN Network. Radios must support 5/10mHz channels AND the must also be the INTL (International) version as the US versions CANNOT operate outside of the commercial band.

Quick Intro to WinBox and how to use it to configure a radio

Winbox is a Mikrotik Provided application for managing the radios. (Web Browser and SSH are also options) The main benefit to using this tool is that it can usually access any radio directly connected to the computer even if the configuration is completely incorrect.

What Can Go Wrong?

  • In most cases no permanent damage can be done to the radio, with some exceptions:
    • As with most devices there is always a chance that upgrading the firmware could fail, resulting in a radio that will no longer startup. Thankfully Mikrotik offers a recovery mode that can usually fix this called Netinstall

Security Considerations

  • HamWAN provides an almost entirely unfiltered connection to the internet. This means it is VERY important to ensure that all equipment connected to the network is up to date including the radio firmware.
  • Our suggested configuration for client radios results in the Radio receiving a public-facing (44.x.x.x) IP Address on the wireless side, this address is fully accessible from the internet. Devices connected to the radio via ethernet will receive private addresses (192.1.88.x) and cannot be directly accessed from the internet. This process is called NAT or Network Address Translation and works for 95% of use cases. If you intend to host services such as an IRLP node where connections from the Internet are required your will need to configure Port Forwarding on the radio.