Widy/Configuration - Revision history

Admin: /* Opkg Package Manager Configuration */

2018-01-30T02:21:38Z

Opkg Package Manager Configuration

← Older revision		Revision as of 02:21, 30 January 2018
Line 101:		Line 101:

	<pre>		<pre>
	root@~~dropbear~~:~# cat /etc/opkg.conf		root@widy:~# cat /etc/opkg.conf

	dest root /		dest root /

Admin: /* System Configuration */

2018-01-30T02:21:23Z

System Configuration

← Older revision		Revision as of 02:21, 30 January 2018
Line 87:		Line 87:

	A: You can use a shell script to check on the state of the slider button.		A: You can use a shell script to check on the state of the slider button.

			=Opkg Package Manager Configuration=

			the opkg setup on openwrt underwent some changes a few years back, so there is now a split into "packages" and "old packages".

			Up to date packages (these have maintainers and no security issues): https://archive.openwrt.org/barrier_breaker/14.07/ar71xx/generic/packages/packages/

			Old packages (these have no maintainers and potentially have issues): https://archive.openwrt.org/barrier_breaker/14.07/ar71xx/generic/packages/oldpackages/

			Best approach is probably to only add in the old packages when you specifically need them.

			To modify the list of packages, edit <code>/etc/opkg.cfg</code>:

			<pre>
			root@dropbear:~# cat /etc/opkg.conf

			dest root /
			dest ram /tmp
			lists_dir ext /var/opkg-lists
			option overlay_root /overlay
			src/gz barrier_breaker_packages http://downloads.openwrt.org/barrier_breaker/14.07/ar71xx/generic/packages/packages
			src/gz old_barrier_breaker_packages http://downloads.openwrt.org/barrier_breaker/14.07/ar71xx/generic/packages/oldpackages
			src/gz barrier_breaker_base http://downloads.openwrt.org/barrier_breaker/14.07/ar71xx/generic/packages/base
			src/gz barrier_breaker_luci http://downloads.openwrt.org/barrier_breaker/14.07/ar71xx/generic/packages/luci
			src/gz barrier_breaker_management http://downloads.openwrt.org/barrier_breaker/14.07/ar71xx/generic/packages/management
			src/gz barrier_breaker_routing http://downloads.openwrt.org/barrier_breaker/14.07/ar71xx/generic/packages/routing
			src/gz barrier_breaker_telephony http://downloads.openwrt.org/barrier_breaker/14.07/ar71xx/generic/packages/telephony
			option check_signature 1

			</pre>

	=Slider Button Configuration=		=Slider Button Configuration=

Admin: /* Checking Output from Switch Script */

2017-03-13T22:22:51Z

Checking Output from Switch Script

← Older revision		Revision as of 22:22, 13 March 2017
Line 211:		Line 211:
	Fri Mar 3 20:50:45 2017 user.notice root: [hotplug] Slider AP		Fri Mar 3 20:50:45 2017 user.notice root: [hotplug] Slider AP
	Fri Mar 3 20:50:45 2017 user.notice root: [hotplug] Killed python and airodump		Fri Mar 3 20:50:45 2017 user.notice root: [hotplug] Killed python and airodump
	~~root@OpenWrt:~#~~
			$
	</pre>		</pre>

Admin: /* How The Switch Works */

2017-03-13T22:22:30Z

How The Switch Works

← Older revision		Revision as of 22:22, 13 March 2017
Line 195:		Line 195:

	Bada-bing!		Bada-bing!

			==Checking Output from Switch Script==

			<pre>
			$ # okay, go ahead and flick the button

			$ logread
			Fri Mar 3 20:48:46 2017 authpriv.notice dropbear[1247]: Password auth succeeded for 'root' from 192.168.1.189:52934
			Fri Mar 3 20:50:43 2017 user.notice root: [hotplug] loging button BTN_0 -- action pressed
			Fri Mar 3 20:50:43 2017 user.notice root: [hotplug] Slider AP
			Fri Mar 3 20:50:43 2017 user.notice root: [hotplug] Killed python and airodump
			Fri Mar 3 20:50:44 2017 user.notice root: [hotplug] loging button BTN_1 -- action released
			Fri Mar 3 20:50:44 2017 user.notice root: [hotplug] Slider WISP
			Fri Mar 3 20:50:45 2017 user.notice root: [hotplug] loging button BTN_1 -- action pressed
			Fri Mar 3 20:50:45 2017 user.notice root: [hotplug] Slider AP
			Fri Mar 3 20:50:45 2017 user.notice root: [hotplug] Killed python and airodump
			root@OpenWrt:~#
			</pre>

	==Connecting Configurations with Switch==		==Connecting Configurations with Switch==

Admin: /* Slider Button Configuration */

2017-03-03T01:53:18Z

Slider Button Configuration

← Older revision		Revision as of 01:53, 3 March 2017
Line 106:		Line 106:

	You can create a new file <code>/etc/hotplug.d/button/buttons</code>, to run when the slider button is changed, and make a script that will record the names of each of the buttons to the system log:		You can create a new file <code>/etc/hotplug.d/button/buttons</code>, to run when the slider button is changed, and make a script that will record the names of each of the buttons to the system log:

	~~<pre>~~

	<pre>		<pre>

Admin: /* Network Configuration */

2017-03-03T01:52:05Z

Network Configuration

← Older revision		Revision as of 01:52, 3 March 2017
Line 71:		Line 71:

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

	~~Note that, once you change this~~

	==System Configuration==		==System Configuration==

Admin: /* Network Configuration */

2017-03-03T01:51:17Z

Network Configuration

← Older revision		Revision as of 01:51, 3 March 2017
Line 54:		Line 54:
	To check whether this is an issue, go to <code>192.168.1.1</code> in your browser. If you see the LUCI web interface, it's no biggie. If you see some other configuration page for a different wireless router, then you have an IP address conflict.		To check whether this is an issue, go to <code>192.168.1.1</code> in your browser. If you see the LUCI web interface, it's no biggie. If you see some other configuration page for a different wireless router, then you have an IP address conflict.

	To fix this, use the LUCI interface to change the IP address range that the Widy uses to assign new IP addresses. ~~I changed~~ it to <code>192.168.0.X</code> ~~to keep it simple.~~		To fix this, disconnect from any networks you are connected to, then connect to the Widy using an ethernet cable. You can use the LUCI interface to change the IP address range that the Widy uses to assign new IP addresses. This example will change it to <code>192.168.0.X</code>

	Start by logging in to the LUCI interface:		Start by logging in to the LUCI interface:

Admin: /* Slider Button Configuration */

2016-06-21T18:17:36Z

Slider Button Configuration

← Older revision		Revision as of 18:17, 21 June 2016
Line 97:		Line 97:
	* AP		* AP

	[[Image:WidySwitch.jpg\|~~350px~~]]		[[Image:WidySwitch.jpg\|200px]]

	~~Before we~~ can ~~control these buttons, we need to know their names.~~		To link the slider button with scripts, you can create a script that will run whenever the buttons are activated. Start by creating the following directory:

	~~Start by making~~ a script that will run whenever the buttons are activated:

	<pre>		<pre>
Line 107:		Line 105:
	</pre>		</pre>

	Now create ~~the~~ file <code>/etc/hotplug.d/button/buttons</code> and ~~add~~ a ~~command~~ to ~~log some information about the button in~~ the system log:		Now, anytime you change the state of the slider button, the Widy will run any and all scripts contained in this folder.

			You can create a new file <code>/etc/hotplug.d/button/buttons</code>, to run when the slider button is changed, and make a script that will record the names of each of the buttons to the system log:

			<pre>

	<pre>		<pre>
	#!/bin/sh		#!/bin/sh
	logger the button was $BUTTON and the action was $ACTION		logger "the button was $BUTTON and the action was $ACTION"
	</pre>		</pre>

Line 175:		Line 177:
	<pre>		<pre>
	#!/bin/sh		#!/bin/sh
	sleep 1		sleep 1 # give it a second, in case the user has butterfingers
	logger "log: $BUTTON -- $ACTION"		logger "log: $BUTTON -- $ACTION"

Line 196:		Line 198:
	</pre>		</pre>

	~~Badda~~-bing		Bada-bing!


	==Connecting Configurations with Switch==		==Connecting Configurations with Switch==

	Different switch states can be set with this init script.		Different switch states can be set with this init script. By adding actions in the above script, where it says "some action here," you can make the Widy do things when you change the slider switch.

	we can add actions where those "some action here" comments are, specifically by using the <code>uci</code> command: https://wiki.openwrt.org/doc/uci#command_line_utility		We can add actions where those "some action here" comments are, specifically by using the <code>uci</code> command: https://wiki.openwrt.org/doc/uci#command_line_utility

	Let's illustrate with an example:		Let's illustrate with an example:

Admin: /* System Configuration */

2016-06-21T18:05:21Z

System Configuration

← Older revision		Revision as of 18:05, 21 June 2016
Line 79:		Line 79:

	Q: What happens when you change <code>/etc/config/file</code>? Does it stay persistent?		Q: What happens when you change <code>/etc/config/file</code>? Does it stay persistent?

			A: Yes, when you edit <code>/etc/config/file</code> it will be a permanent change. If you reboot the router the configuration will remain the same. If you open the LUCI web interface, it will load all of the configuration details from the files in <code>/etc/config/</code>. Everything will be reflected correctly, as it should.

	Q: When and how does UCI override changes with defaults?		Q: When and how does UCI override changes with defaults?

	Q: How can I link UCI with the 3 slider ~~buttons~~?		A: If you don't set options in the files in <code>/etc/config/</code>, then default options will be used. If you set it in a config file, the option you set will be used. If you remove the setting from the config file, the default value will be used again.

			Q: How can I link UCI with the 3-setting slider button on the side of the Widy?

			A: You can use a shell script to check on the state of the slider button.

	=Slider Button Configuration=		=Slider Button Configuration=

Admin: /* Network Configuration */

2016-06-21T17:59:47Z

Network Configuration

← Older revision		Revision as of 17:59, 21 June 2016
Line 51:		Line 51:

	After installing OpenWRT, the Widy will, by default, assign IP addresses in the range <code>192.168.1.X</code>. However, this will cause problems if you want to connect to the Widy and simultaneously connect to a wireless network that also assigns IP addresses in the range <code>192.168.1.X</code>.		After installing OpenWRT, the Widy will, by default, assign IP addresses in the range <code>192.168.1.X</code>. However, this will cause problems if you want to connect to the Widy and simultaneously connect to a wireless network that also assigns IP addresses in the range <code>192.168.1.X</code>.

			To check whether this is an issue, go to <code>192.168.1.1</code> in your browser. If you see the LUCI web interface, it's no biggie. If you see some other configuration page for a different wireless router, then you have an IP address conflict.

	To fix this, use the LUCI interface to change the IP address range that the Widy uses to assign new IP addresses. I changed it to <code>192.168.0.X</code> to keep it simple.		To fix this, use the LUCI interface to change the IP address range that the Widy uses to assign new IP addresses. I changed it to <code>192.168.0.X</code> to keep it simple.
Line 69:		Line 71:

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

			Note that, once you change this

	==System Configuration==		==System Configuration==