Client Node Configuration - Revision history

Va7stv at 00:19, 9 September 2020

2020-09-09T00:19:23Z

New page

{{Template:Alert | type = danger | message = 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!!! }}
{{Template:Alert | type = warning| message = 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.

== Understanding What HamWAN Is and Isn't ==
* Who can use it?
** Anyone with a valid Amateur Radio license can use our network

* What can it be used for?
** Primarily the network is intended to serve as an emergency communications system
** Encrypted Traffic is not allowed
** Commercial traffic is prohibited

== 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 ==

{{Template:Alert | type = info| message = When programming this radio for the first time it is generally easier to use the Mac Address of the device to connect to it from winbox, This will ensure that if you remove the current IP address you remain connected to the radio. You can do this by either typing the mac address into the address field or selecting a detected radio by clicking on the mac address column. }}

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)

<ol>
<li>
Upgrade your modem to the latest version of RouterOS
<ul>
<li>
If you have connected the modem to your LAN in a way that provides Internet access, the following two command can be used:
<pre>/system package update install</pre>
once the system is don upgrading and rebooting run
<pre>/system routerboard upgrade</pre>
</li>
<li>
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)
</li>
</ul>
</li>

<li>
Reset the router to a blank configuration.
<pre>/system reset-configuration no-defaults=yes</pre>
</li>

<li>
Give your modem a name, use your callsign so that we can easily identify the owner of this radio
<pre>/system identity set name=MYCALL</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>
Set a password for the admin user
<pre>/user set admin password=
/console clear-history</pre>
This is an example password generated in your browser. You may choose any password you like.
</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>
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.
</li>

<li>
In the PDSR instructions you would install the Shared Administrator SSH Certificates here. This is much easier once you are connected to the network so we do this at the end.
</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
<pre>
/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
</pre>
</li>
<li>
Configure Central Authentication
<pre>
/radius add address=44.135.217.99 secret=AmprNET service=login
/user aaa set use-radius=yes
</pre>
</li>
<li>
SNMP Monitoring
<pre>
/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 trap-version=2</pre>
</li>

<li>
Setup NTP Skip this step for now we do not yet have a network time server
<pre>
/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
</pre>
</li>

<li>
Clear the firewall rules
<pre>
/ip firewall filter remove [find dynamic=no]
</pre>
</li>

<li>
Set the HamWAN Maximum Transmission Unit (MTU) policy
TODO: We need to make sure this is correct for our network
<pre>
/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
</pre>
</li>

<li>
Remove local DHCP server
<pre>
/ip dhcp-server remove [find]
/ip dhcp-server network remove [find]
</pre>
</li>

<li>
Remove local IP address
<pre>/ip address remove [find interface~"^wlan1"]</pre>
</li>

<li>
Disable DNS Service Important!!!
<pre>/ip dns set allow-remote-requests=no</pre>
</li>

<li>
Add HamWAN sector channels. HamWAN uses custom channels outside the normal frequency range for 5ghz WiFi, you need to add these channels to the radio. Currently all of our sector sites use 10mhz channels but you should add both 5 and 10 variants to be safe.
<pre>
/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
</pre>
</li>

<li>
Configure the modem to announce your callsign
<pre>/interface wireless set 0 radio-name="MYCALL"</pre>
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.
</li>

<li>
Set your location, so that your station shows up on the HamWAN map. Supply your latitude and longitude in decimal degrees separated by a comma, like <code>location=47.1234,-121.1234</code>.
<pre>/snmp set location=LAT,LON</pre>
</li>

<li>
Configure the wireless card to connect to HamWAN
<pre>/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</pre>
</li>

<li>
Configure your modem to request a DHCP address from the HamWAN network.
<pre>/ip dhcp-client add add-default-route=yes dhcp-options=hostname,clientid disabled=no interface=wlan1
</pre>
</li>
</ol>

<ol>
<li>Now that you have an internet connection install the keys that support shared administration. Note username are case sensitive. 
Download:
<pre>
/tool fetch url="http://portal.hamwan.ca/users/keys/sshkey-manage.pub" dst-path=sshkey-manage.pub;
</pre>
Install:
<pre>
/user ssh-keys import public-key-file=sshkey-manage.pub user=manage
</pre>
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.

<li>

</ol>

== Next Steps ==
===Integrating HamWAN into your LAN===
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 [http://hamwan.org/Standards/Network%20Engineering/LAN%20Integration.html here].

====Create an isolated LAN for use with HamWAN====
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.

<ol>
<li>
Assign an IP address to your modem's LAN port
<pre>
/ip address add address=192.168.88.1/24 interface=ether1
</pre>
</li>
<li>
Configure DHCP server
<pre>
/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
</pre>
</li>
<li>
Configure NAT (Network Address Translation)
<pre>
/ip firewall nat add chain=srcnat action=masquerade out-interface=wlan1
</pre>
</li>
<li>
Connect one end of an Ethernet cable to your modem and the other to the PoE injector (the injector included with the Metal feeds power to the socket side of the adapter). Plug the injector directly into your PC, or into a switch for use with multiple PCs. The modem will assign IP addresses to connected PCs and route their packets to HamWAN.
</li>
</ol>

Example of [[VA7DBD.client]] VA7DBD's Client Radio Config

Va7stv at 15:52, 2 October 2019

2019-10-02T15:52:50Z

New page

{{Template:Alert | type = danger | message = 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!!! }}
{{Template:Alert | type = warning| message = 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.

== Understanding What HamWAN Is and Isn't ==
* Who can use it?
** Anyone with a valid Amateur Radio license can use our network

* What can it be used for?
** Primarily the network is intended to serve as an emergency communications system
** Encrypted Traffic is not allowed
** Commercial traffic is prohibited

== 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 ==

{{Template:Alert | type = info| message = When programming this radio for the first time it is generally easier to use the Mac Address of the device to connect to it from winbox, This will ensure that if you remove the current IP address you remain connected to the radio. You can do this by either typing the mac address into the address field or selecting a detected radio by clicking on the mac address column. }}

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)

<ol>
<li>
Upgrade your modem to the latest version of RouterOS
<ul>
<li>
If you have connected the modem to your LAN in a way that provides Internet access, the following two command can be used:
<pre>/system package update install</pre>
once the system is don upgrading and rebooting run
<pre>/system routerboard upgrade</pre>
</li>
<li>
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)
</li>
</ul>
</li>

<li>
Reset the router to a blank configuration.
<pre>/system reset-configuration no-defaults=yes</pre>
</li>

<li>
Give your modem a name, use your callsign so that we can easily identify the owner of this radio
<pre>/system identity set name=MYCALL</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>
Set a password for the admin user
<pre>/user set admin password=
/console clear-history</pre>
This is an example password generated in your browser. You may choose any password you like.
</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>
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.
</li>

<li>
In the PDSR instructions you would install the Shared Administrator SSH Certificates here. This is much easier once you are connected to the network so we do this at the end.
</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
<pre>
/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
</pre>
</li>
<li>
Configure Central Authentication
<pre>
/radius add address=44.135.217.99 secret=AmprNET service=login
/user aaa set use-radius=yes
</pre>
</li>
<li>
SNMP Monitoring
<pre>
/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 trap-version=2</pre>
</li>

<li>
Setup NTP Skip this step for now we do not yet have a network time server
<pre>
/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
</pre>
</li>

<li>
Clear the firewall rules
<pre>
/ip firewall filter remove [find dynamic=no]
</pre>
</li>

<li>
Set the HamWAN Maximum Transmission Unit (MTU) policy
TODO: We need to make sure this is correct for our network
<pre>
/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
</pre>
</li>

<li>
Remove local DHCP server
<pre>
/ip dhcp-server remove [find]
/ip dhcp-server network remove [find]
</pre>
</li>

<li>
Remove local IP address
<pre>/ip address remove [find interface~"^wlan1"]</pre>
</li>

<li>
Disable DNS Service Important!!!
<pre>/ip dns set allow-remote-requests=no</pre>
</li>

<li>
Add HamWAN sector channels. HamWAN uses custom channels outside the normal frequency range for 5ghz WiFi, you need to add these channels to the radio. Currently all of our sector sites use 10mhz channels but you should add both 5 and 10 variants to be safe.
<pre>
/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
</pre>
</li>

<li>
Configure the modem to announce your callsign
<pre>/interface wireless set 0 radio-name="MYCALL"</pre>
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.
</li>

<li>
Set your location, so that your station shows up on the HamWAN map. Supply your latitude and longitude in decimal degrees separated by a comma, like <code>location=47.1234,-121.1234</code>.
<pre>/snmp set location=LAT,LON</pre>
</li>

<li>
Configure the wireless card to connect to HamWAN
<pre>/interface wireless set 0 disabled=no frequency-mode=superchannel band=5ghz-onlyn mode=station scan-list="HamWAN" ssid=HamWAN wireless-protocol=nv2</pre>
</li>

<li>
Configure your modem to request a DHCP address from the HamWAN network.
<pre>/ip dhcp-client add add-default-route=yes dhcp-options=hostname,clientid disabled=no interface=wlan1
</pre>
</li>
</ol>

<ol>
<li>Now that you have an internet connection install the keys that support shared administration. Note username are case sensitive. 
Download:
<pre>
/tool fetch url="http://portal.hamwan.ca/users/keys/sshkey-manage.pub" dst-path=sshkey-manage.pub;
</pre>
Install:
<pre>
/user ssh-keys import public-key-file=sshkey-manage.pub user=manage
</pre>
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.

<li>

</ol>

== Next Steps ==
===Integrating HamWAN into your LAN===
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 [http://hamwan.org/Standards/Network%20Engineering/LAN%20Integration.html here].

====Create an isolated LAN for use with HamWAN====
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.

<ol>
<li>
Assign an IP address to your modem's LAN port
<pre>
/ip address add address=192.168.88.1/24 interface=ether1
</pre>
</li>
<li>
Configure DHCP server
<pre>
/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
</pre>
</li>
<li>
Configure NAT (Network Address Translation)
<pre>
/ip firewall nat add chain=srcnat action=masquerade out-interface=wlan1
</pre>
</li>
<li>
Connect one end of an Ethernet cable to your modem and the other to the PoE injector (the injector included with the Metal feeds power to the socket side of the adapter). Plug the injector directly into your PC, or into a switch for use with multiple PCs. The modem will assign IP addresses to connected PCs and route their packets to HamWAN.
</li>
</ol>

Example of [[VA7DBD.client]] VA7DBD's Client Radio Config

Va7stv at 06:14, 18 November 2017

2017-11-18T06:14:43Z

← Older revision		Revision as of 06:14, 18 November 2017
Line 82:		Line 82:
	<pre>		<pre>
	/snmp set enabled=yes contact="#HamWAN on irc.freenode.org"		/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</pre>		/snmp community set name=hamwan addresses=44.135.216.0/23 read-access=yes write-access=no numbers=0 trap-version=2</pre>
	</li>		</li>

Va7stv: /* Next Steps */

2017-11-14T21:35:39Z

Next Steps

← Older revision		Revision as of 21:35, 14 November 2017
Line 182:		Line 182:
	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 [http://hamwan.org/Standards/Network%20Engineering/LAN%20Integration.html here].		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 [http://hamwan.org/Standards/Network%20Engineering/LAN%20Integration.html here].


			====Create an isolated LAN for use with HamWAN====
	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.		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.

	~~====Create an isolated LAN for use with HamWAN====~~
	<ol>		<ol>
	<li>		<li>

Va7stv at 21:35, 14 November 2017

2017-11-14T21:35:17Z

@@ Line 177: / Line 177: @@
 <li>
 </ol>
 Example of  [[VA7DBD.client]] VA7DBD's Client Radio Config

Va7stv at 23:21, 1 November 2017

2017-11-01T23:21:37Z

← Older revision		Revision as of 23:21, 1 November 2017
Line 152:		Line 152:
	<li>		<li>
	Configure the wireless card to connect to HamWAN		Configure the wireless card to connect to HamWAN
	<pre>/interface wireless set 0 disabled=no frequency-mode=superchannel band=5ghz-onlyn mode=station scan-list=HamWAN ssid=HamWAN wireless-protocol=nv2</pre>		<pre>/interface wireless set 0 disabled=no frequency-mode=superchannel band=5ghz-onlyn mode=station scan-list="HamWAN" ssid=HamWAN wireless-protocol=nv2</pre>
	</li>		</li>

Va7stv at 20:46, 22 October 2017

2017-10-22T20:46:16Z

← Older revision		Revision as of 20:46, 22 October 2017
Line 164:		Line 164:

	<ol>		<ol>
	<li>Now that you have an internet connection install the keys that support shared administration. Note username are case sensitive.		<li>Now that you have an internet connection install the keys that support shared administration. Note username are case sensitive.<br>
			Download:
	<pre>		<pre>
	/tool fetch url="http://portal.hamwan.ca/users/keys/sshkey-manage.pub" dst-path=sshkey-manage.pub;		/tool fetch url="http://portal.hamwan.ca/users/keys/sshkey-manage.pub" dst-path=sshkey-manage.pub;
			</pre>
			Install:
			<pre>
	/user ssh-keys import public-key-file=sshkey-manage.pub user=manage		/user ssh-keys import public-key-file=sshkey-manage.pub user=manage
	</pre>		</pre>

Va7stv at 19:41, 22 October 2017

2017-10-22T19:41:06Z

← Older revision		Revision as of 19:41, 22 October 2017
Line 166:		Line 166:
	<li>Now that you have an internet connection install the keys that support shared administration. Note username are case sensitive.		<li>Now that you have an internet connection install the keys that support shared administration. Note username are case sensitive.
	<pre>		<pre>
	/tool fetch url="~~https~~://portal.hamwan.ca/users/keys/sshkey-manage.pub" dst-path=sshkey-manage.pub;		/tool fetch url="http://portal.hamwan.ca/users/keys/sshkey-manage.pub" dst-path=sshkey-manage.pub;
	/user ssh-keys import public-key-file=sshkey-manage.pub user=manage		/user ssh-keys import public-key-file=sshkey-manage.pub user=manage
	</pre>		</pre>

Va7stv at 19:40, 22 October 2017

2017-10-22T19:40:22Z

← Older revision		Revision as of 19:40, 22 October 2017
Line 60:		Line 60:

	<li>		<li>
	~~TODO: Install hamwan~~ SSH ~~Keys,~~ This is ~~not required~~ to ~~achieve a connection~~		In the PDSR instructions you would install the Shared Administrator SSH Certificates here. This is much easier once you are connected to the network so we do this at the end.
	</li>		</li>

Line 163:		Line 163:


			<ol>
			<li>Now that you have an internet connection install the keys that support shared administration. Note username are case sensitive.
			<pre>
			/tool fetch url="https://portal.hamwan.ca/users/keys/sshkey-manage.pub" dst-path=sshkey-manage.pub;
			/user ssh-keys import public-key-file=sshkey-manage.pub user=manage
			</pre>
			<span style='margin-top: -15px; display: block;color:red; font-size: 0.8em'>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.</span>

			<li>

			</ol>

	Example of [[VA7DBD.client]] VA7DBD's Client Radio Config		Example of [[VA7DBD.client]] VA7DBD's Client Radio Config

Va7stv at 03:00, 22 October 2017

2017-10-22T03:00:16Z

← Older revision		Revision as of 03:00, 22 October 2017
Line 70:		Line 70:
	<li>		<li>
	Configure Remote Central Logging		Configure Remote Central Logging
	~~<span style="color: red;">Skip this step for now we do not yet have a central logging server</span>~~
	<pre>		<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 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=info
	/system logging add action=remote disabled=no prefix="" topics=warning		/system logging add action=remote disabled=no prefix="" topics=warning