Client Node Configuration: Difference between revisions

From OCARC
Jump to navigation Jump to search
No edit summary
Line 39: Line 39:
/console clear-history</pre>
/console clear-history</pre>
   Note: PDSR does this differently and wants you to suffix your callsign with the name of the site you are connecting too. Its unclear why they do this as it just makes roaming more complicated.
   Note: PDSR does this differently and wants you to suffix your callsign with the name of the site you are connecting too. Its unclear why they do this as it just makes roaming more complicated.
  </li>
  <li>
  To support shared administration, add the following HamWAN Network Administration accounts into the "full" group. Usernames are case sensitive.
  <pre>/user add group=full name=manage password=
/console clear-history</pre>
  Note: PDSR does this differently and wants you to suffix your callsign with the name of the site you are connecting too. Its unclear why they do this as it just makes roaming more complicated.
  </li>
  <li>
  TODO: Install hamwan SSH Keys, This is not required to achieve a connection
  </li>
  <li>
  Enable Ethernet boot in case you ever need to reinstall the router with NetInstall (this could save you a trip up to your roof, its a good idea)
  <pre>/system routerboard settings set boot-device=try-ethernet-once-then-nand</pre>
  </li>
  <li>
  Configure Remote Central Logging
  <span style="color: red;">Skip this step for now we do not yet have a central logging server</span>
<pre>
/system logging action set 3 bsd-syslog=no name=remote remote=X.X.X.X remote-port=514 src-address=0.0.0.0 syslog-facility=daemon syslog-severity=auto target=remote
/system logging add action=remote disabled=no prefix="" topics=info
/system logging add action=remote disabled=no prefix="" topics=warning
/system logging add action=remote disabled=no prefix="" topics=error
</pre>
   </li>
   </li>
</ol>
</ol>
<code style="display:block; margin-left: 20px">
<code style="display:block; margin-left: 20px">
1. Upgrade your modem to the latest version of RouterOS
1. Upgrade your modem to the latest version of RouterOS

Revision as of 02:46, 18 October 2017

An antenna MUST be connected to the radio at all times when it is powered on, Not having an antenna connected will result in damage to the radio!!!
These instructions are a work in progress and are unlikely to result in a working connection

Preface

This describes one simple method of configuring your radio modem to connect to HamWAN. It will configure your radio to be used connected directly to a computer(s) without another internet connection. It will provide a provide DHCP address to computers connected over ethernet and will have a public 44.x.x.x address on the wireless side.

Integration With An Existing Network

Integrating HamWAN with an existing network is not a simple task an involves complex networking concepts and may be beyond the capabilities of your home networking equipment.

Configuration Steps

  1. Upgrade your modem to the latest version of RouterOS
    • If you have connected the modem to your LAN in a way that provides Internet access, the following command can be used:
      /system package update upgrade
    • Otherwise, use the standalone upgrade method: http://wiki.mikrotik.com/wiki/Manual:Upgrading_RouterOS (also works on older ROS 5.xx that does not support the upgrade command)
  2. Reset the router to a blank configuration.
    /system reset-configuration no-defaults=yes
  3. Give your modem a name, use your callsign so that we can easily identify the owner of this radio
    /system identity set name=MYCALL
     Note: PDSR does this differently and wants you to suffix your callsign with the name of the site you are connecting too. Its unclear why they do this as it just makes roaming more complicated.
    
  4. Set a password for the admin user
    /user set admin password=
    /console clear-history
     Note: PDSR does this differently and wants you to suffix your callsign with the name of the site you are connecting too. Its unclear why they do this as it just makes roaming more complicated.
    
  5. To support shared administration, add the following HamWAN Network Administration accounts into the "full" group. Usernames are case sensitive.
    /user add group=full name=manage password=
    /console clear-history
     Note: PDSR does this differently and wants you to suffix your callsign with the name of the site you are connecting too. Its unclear why they do this as it just makes roaming more complicated.
    
  6. TODO: Install hamwan SSH Keys, This is not required to achieve a connection
  7. Enable Ethernet boot in case you ever need to reinstall the router with NetInstall (this could save you a trip up to your roof, its a good idea)
    /system routerboard settings set boot-device=try-ethernet-once-then-nand
  8. Configure Remote Central Logging Skip this step for now we do not yet have a central logging server
    /system logging action set 3 bsd-syslog=no name=remote remote=X.X.X.X remote-port=514 src-address=0.0.0.0 syslog-facility=daemon syslog-severity=auto target=remote
    /system logging add action=remote disabled=no prefix="" topics=info
    /system logging add action=remote disabled=no prefix="" topics=warning
    /system logging add action=remote disabled=no prefix="" topics=error
    


1. Upgrade your modem to the latest version of RouterOS

  1. Upgrade your modem to the latest version of RouterOS
    • If you have connected the modem to your LAN in a way that provides Internet access, the following command can be used:
      /system package update upgrade
    • Otherwise, use the standalone upgrade method: http://wiki.mikrotik.com/wiki/Manual:Upgrading_RouterOS (also works on older ROS 5.xx that does not support the upgrade command)
  1. Reset the modem configuration
/system reset-configuration no-defaults=yes

3. Assign a name to your modem so that if can be identified on the network

/system identity set name=VE7OGO

4. Secure your modem by assigning a password to the admin user account

/user set admin password=<password> /console clear-history

5. Add additional user accounts to support monitoring and remote configuration /user add group=full name=va7dig password=<password> add group=read name=monitoring password=<password> /console clear-history

6. Install Keys for Remote Access TODO: Instructions 7. Enabled Recovery Mode (NetInstall)

/system routerboard settings set boot-device=try-ethernet-once-then-nand

8. Remote Logging We do not currently have remote logging

9. SNMP Monitoring

/snmp set enabled=yes contact="#HamWAN on irc.freenode.org" /snmp community set name=hamwan addresses=44.135.216.0/23 read-access=yes write-access=no numbers=0


15. Disable Internal DNS Server

/ip dns set allow-remote-requests=no


16. Configure the modem to use HamWAN Sector Channels

/interface wireless channels add band=5ghz-onlyn comment="Cell sites radiate this at 0 degrees (north)" frequency=5920 list=HamWAN name=Sector1-5 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 120 degrees (south-east)" frequency=5900 list=HamWAN name=Sector2-5 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 240 degrees (south-west)" frequency=5880 list=HamWAN name=Sector3-5 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 0 degrees (north)" frequency=5920 list=HamWAN name=Sector1-10 width=10 add band=5ghz-onlyn comment="Cell sites radiate this at 120 degrees (south-east)" frequency=5900 list=HamWAN name=Sector2-10 width=10 add band=5ghz-onlyn comment="Cell sites radiate this at 240 degrees (south-west)" frequency=5880 list=HamWAN name=Sector3-10 width=10

17. Configure the modem to identify using your callsign

/interface wireless set 0 radio-name="<CALLSIGN>" # For example, set 0 radio-name="AE7SJ/Monroe-Paine"

18. Configure your modems location. This allows it to show on our map /snmp set location=LAT,LON Replace LAT and LON with your coordinates in decimal

Example of VA7DBD.client VA7DBD's Client Radio Config