Widy/Access Point - Revision history

Admin: /* Test Connection to Access Point */

2016-06-18T17:06:06Z

Test Connection to Access Point

← Older revision		Revision as of 17:06, 18 June 2016
Line 106:		Line 106:
	09:10:47.061073 IP morpheus.lan.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 PTR _udisks-ssh._tcp.local., PTR morpheus [AA:21:ZZ:XX:YY:XX]._workstation._tcp.local., PTR _workstation._tcp.local., PTR morpheus._udisks-ssh._tcp.local. (164)		09:10:47.061073 IP morpheus.lan.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 PTR _udisks-ssh._tcp.local., PTR morpheus [AA:21:ZZ:XX:YY:XX]._workstation._tcp.local., PTR _workstation._tcp.local., PTR morpheus._udisks-ssh._tcp.local. (164)
	</pre>		</pre>

			This shows a machine called "morpheus" connecting to the Widy and being assigned an IP address.

	Check that you have gotten an IP address by running <code>ifconfig</code> from the connecting client.		Check that you have gotten an IP address by running <code>ifconfig</code> from the connecting client.

Admin: /* Test Connection to Access Point */

2016-06-18T17:05:17Z

Test Connection to Access Point

Admin: /* Widy as an Access Point */

2016-03-16T04:36:37Z

Widy as an Access Point

← Older revision		Revision as of 04:36, 16 March 2016
Line 1:		Line 1:
	=Widy as an Access Point=		=Widy as an Access Point=

	~~Step~~ by step:		This page guides you through setting up the Widy to act as an Access Point and create a wireless network that will allow multiple devices to talk to each other.

			The step by step of the setup process:

	1. Get access point on and broadcasting		1. Get access point on and broadcasting
Line 13:		Line 15:
	5. Reproduce from scratch. Luci interface, clear out, start from square one, have DHCP config file in a repo somewhere, widy repo, multi clients communicate via network		5. Reproduce from scratch. Luci interface, clear out, start from square one, have DHCP config file in a repo somewhere, widy repo, multi clients communicate via network

	Luci interface~~, clear out,~~ start ~~from square one, have DHCP config file in~~ a ~~repo somewhere (widy repo)~~, ~~multiple clients communicating via~~ the ~~network~~.		Start with the Luci interface. We'll start with a clean slate, and set up the access point and the DHCP service so that our Widy access point will hand out IP addresses properly.

	==Basic Setup==		==Basic Setup==
Line 60:		Line 62:

	[[Image:Luci9.png\|500px]]		[[Image:Luci9.png\|500px]]


	=Problems (Solved)=		=Problems (Solved)=

Admin: /* Problems */

2016-03-16T04:35:02Z

Problems

← Older revision		Revision as of 04:35, 16 March 2016
Line 62:		Line 62:


	=Problems=		=Problems (Solved)=

	I can successfully ping machine B from machine A, when the two machines are connected to the Widy wireless network.		I can successfully ping machine B from machine A, when the two machines are connected to the Widy wireless network.

Admin: /* Problems */

2016-03-16T04:28:29Z

Problems

← Older revision		Revision as of 04:28, 16 March 2016
Line 71:		Line 71:

	Debug notes: [[Widy/Access Point/SSH]]		Debug notes: [[Widy/Access Point/SSH]]

			Finished. Debugged. <code>dpkg-reconfigure openssh-server</code> to the rescue!

	=Other Notes=		=Other Notes=

Admin: /* Problems */

2016-03-16T03:48:04Z

Problems

← Older revision		Revision as of 03:48, 16 March 2016
Line 70:		Line 70:
	However, I can SSH from machine B into the Widy, and from machine A into the Widy.		However, I can SSH from machine B into the Widy, and from machine A into the Widy.

			Debug notes: [[Widy/Access Point/SSH]]


	=Other Notes=		=Other Notes=

Admin: /* Other Notes */

2016-03-16T03:47:20Z

Other Notes

← Older revision		Revision as of 03:47, 16 March 2016
Line 60:		Line 60:

	[[Image:Luci9.png\|500px]]		[[Image:Luci9.png\|500px]]


			=Problems=

			I can successfully ping machine B from machine A, when the two machines are connected to the Widy wireless network.

			I can't SSH into machine B from machine A, or vice versa.

			However, I can SSH from machine B into the Widy, and from machine A into the Widy.




Line 89:		Line 100:

	Check that you have gotten an IP address by running <code>ifconfig</code> from the connecting client.		Check that you have gotten an IP address by running <code>ifconfig</code> from the connecting client.


	=Related=		=Related=

	{{WidyFlag}}		{{WidyFlag}}

Admin at 03:44, 16 March 2016

2016-03-16T03:44:57Z

@@ Line 12: / Line 12: @@
 . Reproduce from scratch. Luci interface, clear out, start from square one, have DHCP config file in a repo somewhere, widy repo, multi clients communicate via network
 Luci interface, clear out, start from square one, have DHCP config file in a repo somewhere (widy repo), multiple clients communicating via the network.
@@ Line 129: / Line 60: @@
 [[Image:Luci9.png|500px]]
 =Related=
 {{WidyFlag}}

Admin: /* Reproduce from Scratch */

2016-03-16T03:42:50Z

Reproduce from Scratch

← Older revision		Revision as of 03:42, 16 March 2016
Line 80:		Line 80:
	Make sure that everyone can connect to the Widy router and receive an IP address and a DHCP lease. The Widy should be successfully handing out IP addresses.		Make sure that everyone can connect to the Widy router and receive an IP address and a DHCP lease. The Widy should be successfully handing out IP addresses.

	==Reproduce from Scratch==		=Reproduce from Scratch=

	Luci interface, clear out, start from square one, have DHCP config file in a repo somewhere (widy repo), multiple clients communicating via the network.		Luci interface, clear out, start from square one, have DHCP config file in a repo somewhere (widy repo), multiple clients communicating via the network.

	===Basic Setup===		==Basic Setup==

	Start by plugging in the Widy router to the computer via the Ethernet cable. Your computer should be assigned an IP address like 192.168.1.109. Now the Widy router and its web interface (Luci) should be available by typing 192.168.1.1 into your browser.		Start by plugging in the Widy router to the computer via the Ethernet cable. Your computer should be assigned an IP address like 192.168.1.109. Now the Widy router and its web interface (Luci) should be available by typing 192.168.1.1 into your browser.
Line 90:		Line 90:
	The first page you'll see is the login page. Start by logging in with your root username and password.		The first page you'll see is the login page. Start by logging in with your root username and password.

	===Set Up the AP Interface===		==Set Up the AP Interface==

	Now click Network > Interfaces. You should see this page:		Now click Network > Interfaces. You should see this page:
Line 112:		Line 112:
	[[Image:Luci5.png\|500px]]		[[Image:Luci5.png\|500px]]

	===Double-Check Associated Clients===		==Double-Check Associated Clients==

	Now it's time to double-check that our wireless network can, in fact, receive new clients. Click Network > Wifi, then check the "Associated Stations" list - this is a list of clients connected to the wireless access point.		Now it's time to double-check that our wireless network can, in fact, receive new clients. Click Network > Wifi, then check the "Associated Stations" list - this is a list of clients connected to the wireless access point.

Admin: /* Reproduce from Scratch */

2016-03-16T03:06:20Z

Reproduce from Scratch

@@ Line 83: / Line 83: @@
 Luci interface, clear out, start from square one, have DHCP config file in a repo somewhere (widy repo), multiple clients communicating via the network.
 Start by plugging in the Widy router to the computer via the Ethernet cable. Your computer should be assigned an IP address like 192.168.1.109. Now the Widy router and its web interface (Luci) should be available by typing 192.168.1.1 into your browser.
 The first page you'll see is the login page. Start by logging in with your root username and password.
 Now click Network > Interfaces. You should see this page:
@@ Line 101: / Line 105: @@
 The next step is to set up the DHCP settings, and govern how IP addresses will be handed out. When configuring the wireless access point, you will set the IP address of the access point, as well as the subnet mask and other details. You should probably stick to 192.168.{0,1}.X and 10.{0,1}.{0,1}.X as your IP address namespaces - if your network is large enough to need subnets, it probably carries enough traffic to need a beefier router.
 =Related=
 {{WidyFlag}}

← Older revision		Revision as of 17:05, 18 June 2016
Line 79:		Line 79:
	==Test Connection to Access Point==		==Test Connection to Access Point==

	To troubleshoot the process of connecting ~~clients~~ to the ~~access point (for example, if you are connecting but not getting IP addresses)~~, or at least monitor it to make sure it goes as planned, ~~is to~~ connect to the Widy via ethernet, ~~and~~ run tcpdump to monitor the wireless network interface. ~~Then~~, connect to the ~~OpenWrt~~ wireless network ~~with~~ another computer~~, and watch~~ the packet traffic ~~that passes~~ through the wireless network interface. You should see ~~some~~ DHCP requests and BOOTP requests~~, which is~~ the new computer ~~that~~ is connecting to the wireless network getting an IP address.		You may run into an issue where you are connecting, but not being assigned an IP address.

			To troubleshoot the process of a client connecting to the AP, or at least to monitor the process to make sure it goes as planned, connect a client computer to the Widy via an ethernet cable and SSH. Once you have a shell on the Widy, run tcpdump to monitor the wireless network interface <code>wlan0</code>.

			Next, monitor the tcpdump output while you attempt to connect to the Widy's wireless network using another client computer. Watch the packet traffic passing through the Widy wireless network interface. You should see DHCP requests and BOOTP requests - these indicate that the new computer is connecting to the wireless network and getting an IP address.

			Here is some sample output:

	<pre>		<pre>
	$ tcpdump -i wlan0		$ tcpdump -i wlan0
	09:10:46.662109 00:21:6a:07:17:14 (oui Unknown) > Broadcast Null Unnumbered, xid, Flags [Response], length 6: 01 00		09:10:46.662109 AA:21:ZZ:XX:YY:XX (oui Unknown) > Broadcast Null Unnumbered, xid, Flags [Response], length 6: 01 00
	09:10:46.663583 EAPOL key (3) v2, len 95		09:10:46.663583 EAPOL key (3) v2, len 95
	09:10:46.672735 EAPOL key (3) v1, len 117		09:10:46.672735 EAPOL key (3) v1, len 117
Line 90:		Line 96:
	09:10:46.699734 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28		09:10:46.699734 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
	09:10:46.699917 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28		09:10:46.699917 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
	09:10:46.745280 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:21:6a:07:17:14 (oui Unknown), length 300		09:10:46.745280 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from AA:21:ZZ:XX:YY:XX (oui Unknown), length 300
	09:10:46.745457 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:21:6a:07:17:14 (oui Unknown), length 300		09:10:46.745457 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from AA:21:ZZ:XX:YY:XX (oui Unknown), length 300
	09:10:46.748579 IP 10.0.0.1.bootps > morpheus.lan.bootpc: BOOTP/DHCP, Reply, length 307		09:10:46.748579 IP 10.0.0.1.bootps > morpheus.lan.bootpc: BOOTP/DHCP, Reply, length 307
	09:10:46.766606 IP morpheus.lan > 224.0.0.22: igmp v3 report, 1 group record(s)		09:10:46.766606 IP morpheus.lan > 224.0.0.22: igmp v3 report, 1 group record(s)
	09:10:46.766770 IP morpheus.lan > 224.0.0.22: igmp v3 report, 1 group record(s)		09:10:46.766770 IP morpheus.lan > 224.0.0.22: igmp v3 report, 1 group record(s)
	09:10:47.019375 IP morpheus.lan.mdns > 224.0.0.251.mdns: 0 [4q] [7n] ANY (QM)? morpheus._udisks-ssh._tcp.local. ANY (QM)? morpheus.local. ANY (QM)? 228.0.0.10.in-addr.arpa. ANY (QM)? morpheus [00:21:6a:07:17:14]._workstation._tcp.local. (262)		09:10:47.019375 IP morpheus.lan.mdns > 224.0.0.251.mdns: 0 [4q] [7n] ANY (QM)? morpheus._udisks-ssh._tcp.local. ANY (QM)? morpheus.local. ANY (QM)? 228.0.0.10.in-addr.arpa. ANY (QM)? morpheus [AA:21:ZZ:XX:YY:XX]._workstation._tcp.local. (262)
	09:10:47.019499 IP morpheus.lan.mdns > 224.0.0.251.mdns: 0 [4q] [7n] ANY (QM)? morpheus._udisks-ssh._tcp.local. ANY (QM)? morpheus.local. ANY (QM)? 228.0.0.10.in-addr.arpa. ANY (QM)? morpheus [00:21:6a:07:17:14]._workstation._tcp.local. (262)		09:10:47.019499 IP morpheus.lan.mdns > 224.0.0.251.mdns: 0 [4q] [7n] ANY (QM)? morpheus._udisks-ssh._tcp.local. ANY (QM)? morpheus.local. ANY (QM)? 228.0.0.10.in-addr.arpa. ANY (QM)? morpheus [AA:21:ZZ:XX:YY:XX]._workstation._tcp.local. (262)
	09:10:47.060955 IP morpheus.lan.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 PTR _udisks-ssh._tcp.local., PTR morpheus [00:21:6a:07:17:14]._workstation._tcp.local., PTR _workstation._tcp.local., PTR morpheus._udisks-ssh._tcp.local. (164)		09:10:47.060955 IP morpheus.lan.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 PTR _udisks-ssh._tcp.local., PTR morpheus [AA:21:ZZ:XX:YY:XX]._workstation._tcp.local., PTR _workstation._tcp.local., PTR morpheus._udisks-ssh._tcp.local. (164)
	09:10:47.061073 IP morpheus.lan.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 PTR _udisks-ssh._tcp.local., PTR morpheus [00:21:6a:07:17:14]._workstation._tcp.local., PTR _workstation._tcp.local., PTR morpheus._udisks-ssh._tcp.local. (164)		09:10:47.061073 IP morpheus.lan.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 PTR _udisks-ssh._tcp.local., PTR morpheus [AA:21:ZZ:XX:YY:XX]._workstation._tcp.local., PTR _workstation._tcp.local., PTR morpheus._udisks-ssh._tcp.local. (164)
	</pre>		</pre>