Mesh/OpenWRT - Revision history

Maxb: /* OpenWRT on a VM */

2013-08-15T19:54:35Z

OpenWRT on a VM

← Older revision		Revision as of 12:54, 15 August 2013
Line 499:		Line 499:

	[http://ediy.com.my/index.php/blog/item/31-openwrt-in-virtualbox OpenWRT in VirtualBox]		[http://ediy.com.my/index.php/blog/item/31-openwrt-in-virtualbox OpenWRT in VirtualBox]


			I've uploaded an already setup VM with a basic dev environment here:

			[https://github.com/max-b/sudomesh-dev-vm Pre-configured VM]

			The readme page should have some details on how to set it up and work around some issues.

2013-08-15T19:40:46Z

OpenWRT on a VM

← Older revision		Revision as of 12:40, 15 August 2013
Line 495:		Line 495:

	[http://wiki.openwrt.org/doc/howto/virtualbox OpenWRT Virtualbox HowTo]		[http://wiki.openwrt.org/doc/howto/virtualbox OpenWRT Virtualbox HowTo]

			This page has some helpful hints, especially on setting up network configurations:

			[http://ediy.com.my/index.php/blog/item/31-openwrt-in-virtualbox OpenWRT in VirtualBox]

2013-08-09T04:50:26Z

← Older revision		Revision as of 21:50, 8 August 2013
Line 486:		Line 486:

	sudo /etc/init.d/network-manager start		sudo /etc/init.d/network-manager start


			= OpenWRT on a VM =

			For some development, it might be easier to run OpenWRT on a virtual machine. This keeps you from having to worry about a bunch of wires and carrying around a router everywhere and mostly keeps you from having to deal with flashing and some other more unpleasant stuffs.

			OpenWRT has a page on how to setup a VM on virtualbox:

			[http://wiki.openwrt.org/doc/howto/virtualbox OpenWRT Virtualbox HowTo]

2013-08-01T18:52:26Z

Logging in and setting root password

← Older revision		Revision as of 11:52, 1 August 2013
Line 43:		Line 43:

	telnet 192.168.1.1		telnet 192.168.1.1

			(I've found that if you get an error here--like no path to host or connection refused--immediately after flashing, unplugging the router and plugging it back in is useful)

	If it asks for a password use 'passwd' (without the quotes).		If it asks for a password use 'passwd' (without the quotes).

2013-07-19T05:43:08Z

Connecting to wifi

← Older revision		Revision as of 22:43, 18 July 2013
Line 170:		Line 170:

	If you restart networking on the device after changing your lan ip address, you will be disconnected from your terminal session. Log back in using the new ip address. (You may have to manually update your ip address on your computer).		If you restart networking on the device after changing your lan ip address, you will be disconnected from your terminal session. Log back in using the new ip address. (You may have to manually update your ip address on your computer).

			You may need to assign yourself a new manual IP
			<pre>
			sudo ifconfig eth0 192.168.2.2 netmask 255.255.255.0 up
			</pre>

	There may also be a need to update your nameserver.		There may also be a need to update your nameserver.

2013-07-19T04:14:51Z

Ubiquiti

← Older revision		Revision as of 21:14, 18 July 2013
Line 294:		Line 294:
	sudo /etc/init.d/network-manager stop		sudo /etc/init.d/network-manager stop

	On most linux machines (assuming your ethernet interface is eth0) setting your ip address ~~on your~~		On most linux machines (assuming your ethernet interface is eth0) setting your ip address looks like this:

	sudo ifconfig eth0 192.168.1.12 netmask 255.255.255.0 up		sudo ifconfig eth0 192.168.1.12 netmask 255.255.255.0 up


	Afterwards do the following:		Afterwards do the following:

2013-07-19T04:14:17Z

Ubiquiti

← Older revision		Revision as of 21:14, 18 July 2013
Line 288:		Line 288:
	The Bullet will now be running a TFTP server 192.168.1.20		The Bullet will now be running a TFTP server 192.168.1.20

	Ensure that you have an IP address different from 192.168.1.20 and in the 192.168.1.x range. On most linux machines (assuming your ethernet interface is eth0) ~~that would be~~		Ensure that you have an IP address different from 192.168.1.20 and in the 192.168.1.x range.

			You may want to stop network-manager (I believe Ubuntu mostly)

			sudo /etc/init.d/network-manager stop

			On most linux machines (assuming your ethernet interface is eth0) setting your ip address on your

	sudo ifconfig eth0 192.168.1.12 netmask 255.255.255.0 up		sudo ifconfig eth0 192.168.1.12 netmask 255.255.255.0 up

	~~You may also want to stop network-manager (I believe Ubuntu mostly)~~

	~~sudo /etc/init.d/network-manager stop~~

	Afterwards do the following:		Afterwards do the following:

2013-07-19T04:08:48Z

Ubiquiti

← Older revision		Revision as of 21:08, 18 July 2013
Line 288:		Line 288:
	The Bullet will now be running a TFTP server 192.168.1.20		The Bullet will now be running a TFTP server 192.168.1.20

	Ensure that you have an IP address different from 192.168.1.20 and in the 192.168.1.x range ~~and~~ do the following:		Ensure that you have an IP address different from 192.168.1.20 and in the 192.168.1.x range. On most linux machines (assuming your ethernet interface is eth0) that would be

			sudo ifconfig eth0 192.168.1.12 netmask 255.255.255.0 up

			You may also want to stop network-manager (I believe Ubuntu mostly)

			sudo /etc/init.d/network-manager stop

			Afterwards do the following:

	tftp 192.168.1.20		tftp 192.168.1.20

2013-07-02T19:28:43Z

← Older revision		Revision as of 12:28, 2 July 2013
Line 152:		Line 152:

	Restart networking and you should be set.		Restart networking and you should be set.
			/etc/init.d/network restart

			There are a few other issues that might come up if you're trying to connect to the internet through the device. One is that 192.168.1.1 is a common ip (subnet?) for home routers. If you're connecting from your computer to your open-wrt router over 192.168.1.1 and the wifi router you're attempting to connect to is also on 192.168.1.1, there will be a (routing?) problem connecting to the internet.

			One easy fix is to edit your networking config file so that the open-wrt router is on a different subnet.

			vi /etc/config/network

			<pre>
			config interface lan
			option ifname eth0
			option type bridge
			option proto static
			option ipaddr 192.168.2.1
			option netmask 255.255.255.0
			</pre>

			If you restart networking on the device after changing your lan ip address, you will be disconnected from your terminal session. Log back in using the new ip address. (You may have to manually update your ip address on your computer).

			There may also be a need to update your nameserver.

			vi /etc/resolv.conf

			<pre>

			search lan
			nameserver 192.168.1.1

			</pre>
			Where 192.168.1.1 is the ip address of the wireless router you are attempting to connect to the internet over.

			After making the changes, restart networking.

	/etc/init.d/network restart		/etc/init.d/network restart

2013-06-26T08:29:31Z

Ubiquiti in Windows

← Older revision		Revision as of 01:29, 26 June 2013
Line 285:		Line 285:
	=== Ubiquiti in Windows ===		=== Ubiquiti in Windows ===
	from the directory where you stored the .bin file:		from the directory where you stored the .bin file:

	>tftp -i 192.168.1.20 PUT openwrt-atheros-ubnt2-squashfs.bin		>tftp -i 192.168.1.20 PUT openwrt-atheros-ubnt2-squashfs.bin