RaspberryPi/Hotspot - Revision history

Admin: /* Link is not ready/Driver initialization failed */

2019-11-25T21:00:42Z

Link is not ready/Driver initialization failed

@@ Line 196: / Line 196: @@
 This is a problem that happens before hostapd starts. Here is the problem I encountered:
 <pre>
@@ Line 218: / Line 216: @@
 <pre>
-#!/bin/sh
+service hostapd stop
-IFACE="wlan1"
+Link: https://askubuntu.com/questions/472794/hostapd-error-nl80211-could-not-configure-driver-mode/743127#743127
 ====Cannot open PID file====

Admin: /* Hosting AP */

2019-11-25T02:08:08Z

Hosting AP

← Older revision		Revision as of 02:08, 25 November 2019
Line 111:		Line 111:
	or whatever other nameservers you want to use.		or whatever other nameservers you want to use.

	==~~Hosting~~ AP==		==Host an AP==

	We use hostapd to create the necessary infrastructure to host an access point.		We use hostapd to create the necessary infrastructure to host an access point.

Admin: /* Restart dnsmasq service */

2019-11-24T23:36:28Z

Restart dnsmasq service

@@ Line 67: / Line 67: @@
 sudo systemctl reload dnsmasq
 </pre>
 ==Hosting AP==

Admin: /* Next Steps */

2019-11-24T22:35:55Z

Next Steps

← Older revision		Revision as of 22:35, 24 November 2019
Line 239:		Line 239:

	=Next Steps=		=Next Steps=

	Our goal with turning the raspberry pi into a wifi access point was to route all of this access point traffic through a VPN connection on a second network connection that has internet. That is, one wifi antenna to serve as the access point, the second wifi antenna (or physical network port) to connect to an existing wifi network.

	* [[RaspberryPi/OpenVPN]] for setting up OpenVPN on the Raspberry Pi		* [[RaspberryPi/OpenVPN]] for setting up OpenVPN on the Raspberry Pi

Admin: /* References */

2019-11-24T22:08:19Z

References

← Older revision		Revision as of 22:08, 24 November 2019
Line 237:		Line 237:
	service dhcpcd restart		service dhcpcd restart
	</pre>		</pre>

			=Next Steps=

			Our goal with turning the raspberry pi into a wifi access point was to route all of this access point traffic through a VPN connection on a second network connection that has internet. That is, one wifi antenna to serve as the access point, the second wifi antenna (or physical network port) to connect to an existing wifi network.

			* [[RaspberryPi/OpenVPN]] for setting up OpenVPN on the Raspberry Pi

	=References=		=References=

Admin: /* Troubleshooting hostapd */

2019-11-24T21:59:08Z

Troubleshooting hostapd

← Older revision		Revision as of 21:59, 24 November 2019
Line 122:		Line 122:
	</pre>		</pre>

	==Troubleshooting hostapd==		===Troubleshooting hostapd===

	If something fails it will probably be on the start step:		If something fails it will probably be on the start step:
Line 132:		Line 132:
	</pre>		</pre>

	===Strategy for Debugging===		====Strategy for Debugging====

	For startup problems, you'll use <code>journalctl -xe</code> or your syslog to find the errors.		For startup problems, you'll use <code>journalctl -xe</code> or your syslog to find the errors.
Line 150:		Line 150:
	Now try connecting to the wifi access point that you created. This should generate some useful/interesting events in the log.		Now try connecting to the wifi access point that you created. This should generate some useful/interesting events in the log.

	===Link is not ready/Driver initialization failed===		====Link is not ready/Driver initialization failed====

	This is a problem that happens before hostapd starts. Here is the problem I encountered:		This is a problem that happens before hostapd starts. Here is the problem I encountered:
Line 197:		Line 197:
	</pre>		</pre>

	===Cannot open PID file===		====Cannot open PID file====

	Another error I encountered was hostapd not being able to open PID file:		Another error I encountered was hostapd not being able to open PID file:
Line 213:		Line 213:
	</pre>		</pre>

	===Packet received on interface that has no address===		====Packet received on interface that has no address====

	Problem with error message "DHCP packet received on wlan1 which has no address":		Problem with error message "DHCP packet received on wlan1 which has no address":

	~~<!--~~

	<pre>		<pre>
	Nov 24 10:04:33 ~~CHROMECAST~~-~~TV-2~~ hostapd: wlan1: STA d0:04:01:81:88:00 IEEE 802.11: authenticated		Nov 24 10:04:33 raspberry-pi hostapd: wlan1: STA d0:04:01:81:88:00 IEEE 802.11: authenticated
	Nov 24 10:04:33 ~~CHROMECAST~~-~~TV-2~~ hostapd: wlan1: STA d0:04:01:81:88:00 IEEE 802.11: associated (aid 1)		Nov 24 10:04:33 raspberry-pi hostapd: wlan1: STA d0:04:01:81:88:00 IEEE 802.11: associated (aid 1)
	Nov 24 10:04:33 ~~CHROMECAST~~-~~TV-2~~ hostapd: wlan1: STA d0:04:01:81:88:00 RADIUS: starting accounting session BB7B0D32203238F1		Nov 24 10:04:33 raspberry-pi hostapd: wlan1: STA d0:04:01:81:88:00 RADIUS: starting accounting session BB7B0D32203238F1
	Nov 24 10:04:33 ~~CHROMECAST~~-~~TV-2~~ hostapd: wlan1: STA d0:04:01:81:88:00 WPA: pairwise key handshake completed (RSN)		Nov 24 10:04:33 raspberry-pi hostapd: wlan1: STA d0:04:01:81:88:00 WPA: pairwise key handshake completed (RSN)
	Nov 24 10:04:33 ~~CHROMECAST-TV~~-2 dnsmasq-dhcp[1023]: DHCP packet received on wlan1 which has no address		Nov 24 10:04:33 raspberry-pi dnsmasq-dhcp[1023]: DHCP packet received on wlan1 which has no address
	Nov 24 10:04:35 ~~CHROMECAST-TV~~-2 dnsmasq-dhcp[1023]: DHCP packet received on wlan1 which has no address		Nov 24 10:04:35 raspberry-pi dnsmasq-dhcp[1023]: DHCP packet received on wlan1 which has no address
	Nov 24 10:04:39 ~~CHROMECAST~~-~~TV-2~~ dnsmasq-dhcp[1023]: DHCP packet received on wlan1 which has no address		Nov 24 10:04:39 raspberry-pi dnsmasq-dhcp[1023]: DHCP packet received on wlan1 which has no address
	Nov 24 10:04:48 ~~CHROMECAST~~-~~TV-2~~ dnsmasq-dhcp[1023]: DHCP packet received on wlan1 which has no address		Nov 24 10:04:48 raspberry-pi dnsmasq-dhcp[1023]: DHCP packet received on wlan1 which has no address
	Nov 24 10:05:02 ~~CHROMECAST~~-~~TV-2~~ CRON[1817]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)		Nov 24 10:05:02 raspberry-pi CRON[1817]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
	Nov 24 10:05:04 ~~CHROMECAST-TV~~-2 dnsmasq-dhcp[1023]: DHCP packet received on wlan1 which has no address		Nov 24 10:05:04 raspberry-pi dnsmasq-dhcp[1023]: DHCP packet received on wlan1 which has no address
	</pre>		</pre>

	~~-->~~

	Underlying issue was with DHCP not working. I was able to see the wifi AP being broadcast, and try to connect to it, but was failing to get assigned an IP address. This was an indication the problem was with the DHCP service.		Underlying issue was with DHCP not working. I was able to see the wifi AP being broadcast, and try to connect to it, but was failing to get assigned an IP address. This was an indication the problem was with the DHCP service.
Line 241:		Line 237:
	service dhcpcd restart		service dhcpcd restart
	</pre>		</pre>


	=References=		=References=

Admin at 21:58, 24 November 2019

2019-11-24T21:58:01Z

← Older revision		Revision as of 21:58, 24 November 2019
Line 1:		Line 1:
	~~Making~~ a Raspberry Pi a hotspot		This page covers the use of a Raspberry Pi to act as an AP/Wifi hotspot.

	~~==Installing Stuff==~~		The basic steps covered here are:

			* Install software for DNS, DHCP, and AP-hosting
			* Configure DHCP
			* Configure DNS

			==Install Software==

			Install DNS, DHCP, and AP-hosting software:
	<pre>		<pre>
	sudo apt install dnsmasq hostapd ~~dhcpcd5~~		sudo apt install dnsmasq dhcpcd5 hostapd
	</pre>		</pre>

	==Edit dhcpcd config file==		==Set up DHCP==

			For dhcp we'll use the dhcpcd utility.

			===Edit dhcpcd config file===

	Edit <code>/etc/dhcpcd.conf</code> and modify it to contain this:		Edit <code>/etc/dhcpcd.conf</code> and modify it to contain this:

	<pre>		<pre>
	interface ~~wlan0~~		interface wlan1
	static ip_address=192.168.4.1/24		static ip_address=192.168.4.1/24
	nohook wpa_supplicant		nohook wpa_supplicant
	</pre>		</pre>

	replace ~~wlan0~~ with whatever interface you want to use.		replace wlan1 with whatever interface you want to use.

	===Restart dhcpcd service===		===Restart dhcpcd service===
Line 25:		Line 36:
	</pre>		</pre>

	==Edit dnsmmasq config file==		==DNS==

			DNS is handled by the dnsmasq utility.

			===Edit dnsmmasq config file===

	Edit the dnsmasq config file <code>/etc/dnsmasq.conf</code>, which determines what range of ip addresses will be handed out and for how long. Modify it to contain this:		Edit the dnsmasq config file <code>/etc/dnsmasq.conf</code>, which determines what range of IP addresses will be handed out and for how long. Modify it to contain this:

	<pre>		<pre>
Line 53:		Line 68:
	</pre>		</pre>

	==Edit hostapd config file==		==Hosting AP==

			We use hostapd to create the necessary infrastructure to host an access point.

			===Edit hostapd config file===

	Now modify the file <code>/etc/hostapd/hostapd.conf</code> to configure hostapd. Modify the contents to the following:		Now modify the file <code>/etc/hostapd/hostapd.conf</code> to configure hostapd. Modify the contents to the following:

Admin at 21:53, 24 November 2019

2019-11-24T21:53:59Z

@@ Line 1: / Line 1: @@
 Making a Raspberry Pi a hotspot
 ==Installing Stuff==
@@ Line 224: / Line 222: @@
 service dhcpcd restart
 </pre>

Admin: /* Troubleshooting hostapd */

2019-11-24T21:51:55Z

Troubleshooting hostapd

@@ Line 114: / Line 114: @@
 See "systemctl status hostapd.service" and "journalctl -xe" for details.
 </pre>
 ===Link is not ready/Driver initialization failed===
-Here is the problem I encountered at first:
+This is a problem that happens before hostapd starts. Here is the problem I encountered:
 https://askubuntu.com/questions/472794/hostapd-error-nl80211-could-not-configure-driver-mode/743127#743127
@@ Line 206: / Line 224: @@
 service dhcpcd restart
 </pre>

Admin: /* Strategy for Debugging */

2019-11-24T21:50:02Z

Strategy for Debugging

← Older revision		Revision as of 21:50, 24 November 2019
Line 207:		Line 207:
	</pre>		</pre>

	==Strategy for Debugging==		===Strategy for Debugging===

	In one window, run this command to run hostapd in the foreground:		In one window, run this command to run hostapd in the foreground: