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.
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.
These steps should get you on the air but do not include any local networking (radio will have HamWAN access but your computer will not)
/system package update install
once the system is don upgrading and rebooting run
/system routerboard upgrade
/system reset-configuration no-defaults=yes
/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.
/user set admin password= /console clear-history
This is an example password generated in your browser. You may choose any password you like.
/user add group=full name=manage password= /console clear-history
The passwords above are randomly generated in your browser, not stored anywhere, and will never be used. Any HamWAN access to your modem will be done with certificates.
/system routerboard settings set boot-device=try-ethernet-once-then-nand
/system logging action set 3 bsd-syslog=no name=remote remote=44.135.216.4 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
/radius add address=44.135.217.99 secret=AmprNET service=login /user aaa set use-radius=yes
/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 /snmp set trap-version=2
/system clock set time-zone-name=America/Vancouver /ip cloud set update-time=no /system ntp client set enabled=yes primary-ntp=208.73.56.29 secondary-ntp=45.76.244.193
/ip firewall filter remove [find dynamic=no]
/ip firewall mangle add action=change-mss chain=output new-mss=1378 protocol=tcp tcp-flags=syn tcp-mss=!0-1378 add action=change-mss chain=forward new-mss=1378 protocol=tcp tcp-flags=syn tcp-mss=!0-1378
/ip dhcp-server remove [find] /ip dhcp-server network remove [find]
/ip address remove [find interface~"^wlan1"]
/ip dns set allow-remote-requests=no
/interface wireless country=no_country_set /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 /interface wireless channels add band=5ghz-onlyn comment="Cell sites radiate this at 120 degrees (south-east)" frequency=5900 list=HamWAN name=Sector2-5 width=5 /interface wireless channels add band=5ghz-onlyn comment="Cell sites radiate this at 240 degrees (south-west)" frequency=5880 list=HamWAN name=Sector3-5 width=5 /interface wireless channels add band=5ghz-onlyn comment="Cell sites radiate this at 0 degrees (north)" frequency=5920 list=HamWAN name=Sector1-10 width=10 /interface wireless channels add band=5ghz-onlyn comment="Cell sites radiate this at 120 degrees (south-east)" frequency=5900 list=HamWAN name=Sector2-10 width=10 /interface wireless channels add band=5ghz-onlyn comment="Cell sites radiate this at 240 degrees (south-west)" frequency=5880 list=HamWAN name=Sector3-10 width=10
/interface wireless set 0 radio-name="MYCALL"
Note: PDSR does this differently and wants you to suffix your callsign with your location and the site your connecting to. Its unclear why they do this as it just makes roaming more complicated.
location=47.1234,-121.1234
.
/snmp set location=LAT,LON
/interface wireless set 0 disabled=no frequency-mode=superchannel band=5ghz-onlyn mode=station scan-list="HamWAN" ssid=HamWAN wireless-protocol=nv2 country=no_country_set
/ip dhcp-client add add-default-route=yes dhcp-options=hostname,clientid disabled=no interface=wlan1
/tool fetch url="http://portal.hamwan.ca/users/keys/sshkey-manage.pub" dst-path=sshkey-manage.pub;
Install:
/user ssh-keys import public-key-file=sshkey-manage.pub user=manage
The passwords above are randomly generated in your browser, not stored anywhere, and will never be used. Any HamWAN access to your modem will be done with certificates.
There are a number of ways to integrate HamWAN into your local network - dedicated local network for HamWAN use. We will discuss only the simplest here for now. PDSR has an in depth article describing other methods here.
Remember to ensure you are within the restrictions of your license it is important to fully understand your network implementation and how traffic will move through it. In this simple configuration all WAN bound traffic will be transmitted/received over your HamWAN radio.
/ip address add address=192.168.88.1/24 interface=ether1
/ip pool add name=dhcp-pool ranges=192.168.88.100-192.168.88.199 /ip dhcp-server network add address=192.168.88.0/24 dns-server=44.135.216.2,44.135.216.3 gateway=192.168.88.1 /ip dhcp-server add address-pool=dhcp-pool interface=ether1 name=dhcp disabled=no
/ip firewall nat add chain=srcnat action=masquerade out-interface=wlan1
Example of VA7DBD.client VA7DBD's Client Radio Config
The contents of this page have been republished from the OCARC wiki - http://wiki.ocarc.ca/index.php?title=Client_Node_Configuration