Ervin T. ervteng

## 3drsolohotspot.txt
In this guide, we will be turning the 3DR solo into a router. The controller-Solo link will be the WAN, and clients will connect to the
3DR solo as an AP.

NOTE: For each *.conf file, we have to modify the md5 hash as well. Otherwise, when the Solo boots, it will reset the files back to the factory default.
- Run "md5sum <full-path-to-file.conf> > <full-path-to-file.conf.md5>" after editing the file.

1. Change /etc/sololink.conf. Find the parameter called "APEnable" and set it to True.
2. Change hostapd.conf. Set the desired SSID (probably needs to be something other than the Controller's SSID)
3. Change dnsmasq.conf so that the Drone's DHCP server hands out IPs in the right range. Note that <3DR_Solo_address> should NOT be in the 10.1.1.X range.
  - dhcp-option=3,<3DR_Solo_address>
	In this guide, we will be turning the 3DR solo into a router. The controller-Solo link will be the WAN, and clients will connect to the
	3DR solo as an AP.

	NOTE: For each *.conf file, we have to modify the md5 hash as well. Otherwise, when the Solo boots, it will reset the files back to the factory default.
	- Run "md5sum <full-path-to-file.conf> > <full-path-to-file.conf.md5>" after editing the file.

	1. Change /etc/sololink.conf. Find the parameter called "APEnable" and set it to True.
	2. Change hostapd.conf. Set the desired SSID (probably needs to be something other than the Controller's SSID)
	3. Change dnsmasq.conf so that the Drone's DHCP server hands out IPs in the right range. Note that <3DR_Solo_address> should NOT be in the 10.1.1.X range.
	- dhcp-option=3,<3DR_Solo_address>