OpenWRT: Installation - Revision history

Jostrowski: typo

2020-01-30T10:09:15Z

typo

← Older revision		Revision as of 10:09, 30 January 2020
Line 1:		Line 1:
	== Summary ==		== Summary ==

	This is a tutorial how to install OpenWRT.		This is a tutorial on how to install OpenWRT.
	For this example the Router [[Zyxel Armor Z2 AC 2600 MU-MIMO dualband wireless router]] is used.		For this example the Router [[Zyxel Armor Z2 AC 2600 MU-MIMO dualband wireless router]] is used.

Line 93:		Line 93:

	As soon as Wireshark starts "listening" on the pipe, SSH will prompt for the password and allow you to continue. Wireshark can also be switched out for tshark and tcpdump can be used in place of dumpcap with slight variations on the above commands.		As soon as Wireshark starts "listening" on the pipe, SSH will prompt for the password and allow you to continue. Wireshark can also be switched out for tshark and tcpdump can be used in place of dumpcap with slight variations on the above commands.



	== Used Hardware ==		== Used Hardware ==

Jostrowski: formatting

2019-10-30T12:49:57Z

formatting

← Older revision		Revision as of 12:49, 30 October 2019
Line 29:		Line 29:
	; OEM easy installation		; OEM easy installation
	: Telnet (or ssh, if you allowed ssh on the router webpage) to the router		: Telnet (or ssh, if you allowed ssh on the router webpage) to the router
	:: login:root		:: <code>login:root</code>
	:: password:1234(or the set password)		:: <code>password:1234</code>(or the set password)
	:: [[File:Zyxel sshLogin.png]]		:: [[File:Zyxel sshLogin.png]]
	:: Interestingly OpenWRT is already is already installed by default, but limited and modified by Zyxel		:: Interestingly OpenWRT is already is already installed by default, but limited and modified by Zyxel
	: copy the kernel.bin and rootfs.bin to the /tmp/ folder		: copy the kernel.bin and rootfs.bin to the /tmp/ folder
	:: scp j@192.168.1.67:/home/j/Desktop/openwrt-18.06.4-ipq806x-zyxel_nbg6817-squashfs-mmcblk0p4-kernel.bin /tmp/		:: <code>scp j@192.168.1.67:/home/j/Desktop/openwrt-18.06.4-ipq806x-zyxel_nbg6817-squashfs-mmcblk0p4-kernel.bin /tmp/</code>
	:: scp j@192.168.1.67:/home/j/Desktop/openwrt-18.06.4-ipq806x-zyxel_nbg6817-squashfs-mmcblk0p5-rootfs.bin /tmp/		:: <code>scp j@192.168.1.67:/home/j/Desktop/openwrt-18.06.4-ipq806x-zyxel_nbg6817-squashfs-mmcblk0p5-rootfs.bin /tmp/</code>
	: copy to local folders:		: copy to local folders:
	:: printf "\xff" >/dev/mtdblock6		:: <code>printf "\xff" >/dev/mtdblock6</code>
	:: cat /tmp/openwrt-ipq806x-NBG6817-squashfs-mmcblk0p4-kernel.bin >/dev/mmcblk0p4		:: <code>cat /tmp/openwrt-ipq806x-NBG6817-squashfs-mmcblk0p4-kernel.bin >/dev/mmcblk0p4</code>
	:: cat /tmp/openwrt-ipq806x-NBG6817-squashfs-mmcblk0p5-rootfs.bin >/dev/mmcblk0p5		:: <code>cat /tmp/openwrt-ipq806x-NBG6817-squashfs-mmcblk0p5-rootfs.bin >/dev/mmcblk0p5</code>
	:: sync		:: <code>sync</code>
	:: reboot -f		:: <code>reboot -f</code>
	; Update openWRT		; Update openWRT
	: Browse to http://192.168.1.1/cgi-bin/luci/mini/system/upgrade/ LuCI Upgrade URL		: Browse to http://192.168.1.1/cgi-bin/luci/mini/system/upgrade/ LuCI Upgrade URL
Line 62:		Line 62:
	#: Go to "System" -> "Administration" and allow SSH		#: Go to "System" -> "Administration" and allow SSH
	# Connect to SSH via terminal		# Connect to SSH via terminal
	#: ssh root@192.168.1.1		#: <code>ssh root@192.168.1.1</code>
	# Update system		# Update system
	#: opkg update		#: <code>opkg update</code>
	# Install tcpdump		# Install tcpdump
	#: opkg install tcpdump		#: <code>opkg install tcpdump</code>

	'''Pipe tcpdump to remote Wireshark session [https://wiki.wireshark.org/CaptureSetup/Pipes Wireshark Wiki]:'''		'''Pipe tcpdump to remote Wireshark session [https://wiki.wireshark.org/CaptureSetup/Pipes Wireshark Wiki]:'''
Line 74:		Line 74:
	In bash syntax, remote capture is possible with the following command:		In bash syntax, remote capture is possible with the following command:

	wireshark -k -i <(ssh -l root remote-host "dumpcap -P -w - -f 'not tcp port 22'")		:<code>wireshark -k -i <(ssh -l root remote-host "dumpcap -P -w - -f 'not tcp port 22'")</code>

	The main problem is that you have to exclude the traffic generated by the ssh session from capturing. Several patches are available to do this, but excluding port 22 is probably the easiest solution for now.		The main problem is that you have to exclude the traffic generated by the ssh session from capturing. Several patches are available to do this, but excluding port 22 is probably the easiest solution for now.
Line 82:		Line 82:
	This can be worked around by combining SSH with a FIFO.		This can be worked around by combining SSH with a FIFO.

	mkfifo /tmp/sharkfin		:<code>mkfifo /tmp/sharkfin</code>
	wireshark -k -i /tmp/sharkfin		:<code>wireshark -k -i /tmp/sharkfin</code>
	ssh user@remote-host "dumpcap -P -w - -f 'not tcp port 22'" > /tmp/sharkfin		:<code>ssh user@remote-host "dumpcap -P -w - -f 'not tcp port 22'" > /tmp/sharkfin</code>

	'''for openWRT this would look like:'''		'''for openWRT this would look like:'''

	mkfifo /tmp/sharkfin		:<code>mkfifo /tmp/sharkfin</code>
	wireshark -k -i /tmp/sharkfin		:<code>wireshark -k -i /tmp/sharkfin</code>
	ssh root@192.168.1.1 "tcpdump -i any -w - -f 'not tcp port 22'" > /tmp/sharkfin		:<code>ssh root@192.168.1.1 "tcpdump -i any -w - -f 'not tcp port 22'" > /tmp/sharkfin</code>

	As soon as Wireshark starts "listening" on the pipe, SSH will prompt for the password and allow you to continue. Wireshark can also be switched out for tshark and tcpdump can be used in place of dumpcap with slight variations on the above commands.		As soon as Wireshark starts "listening" on the pipe, SSH will prompt for the password and allow you to continue. Wireshark can also be switched out for tshark and tcpdump can be used in place of dumpcap with slight variations on the above commands.

Jostrowski at 10:20, 3 October 2019

2019-10-03T10:20:41Z

← Older revision		Revision as of 10:20, 3 October 2019
Line 90:		Line 90:
	mkfifo /tmp/sharkfin		mkfifo /tmp/sharkfin
	wireshark -k -i /tmp/sharkfin		wireshark -k -i /tmp/sharkfin
	ssh root@192.168.1.1 "tcpdump -w - -f 'not tcp port 22'" > /tmp/sharkfin		ssh root@192.168.1.1 "tcpdump -i any -w - -f 'not tcp port 22'" > /tmp/sharkfin

	As soon as Wireshark starts "listening" on the pipe, SSH will prompt for the password and allow you to continue. Wireshark can also be switched out for tshark and tcpdump can be used in place of dumpcap with slight variations on the above commands.		As soon as Wireshark starts "listening" on the pipe, SSH will prompt for the password and allow you to continue. Wireshark can also be switched out for tshark and tcpdump can be used in place of dumpcap with slight variations on the above commands.

Jostrowski at 10:17, 3 October 2019

2019-10-03T10:17:57Z

← Older revision		Revision as of 10:17, 3 October 2019
Line 90:		Line 90:
	mkfifo /tmp/sharkfin		mkfifo /tmp/sharkfin
	wireshark -k -i /tmp/sharkfin		wireshark -k -i /tmp/sharkfin
	ssh root@192.168.1.1 "tcpdump -w - -f 'not tcp port 22'" > /tmp/~~wireshark~~		ssh root@192.168.1.1 "tcpdump -w - -f 'not tcp port 22'" > /tmp/sharkfin

	As soon as Wireshark starts "listening" on the pipe, SSH will prompt for the password and allow you to continue. Wireshark can also be switched out for tshark and tcpdump can be used in place of dumpcap with slight variations on the above commands.		As soon as Wireshark starts "listening" on the pipe, SSH will prompt for the password and allow you to continue. Wireshark can also be switched out for tshark and tcpdump can be used in place of dumpcap with slight variations on the above commands.

Jostrowski at 08:24, 3 October 2019

2019-10-03T08:24:55Z

← Older revision		Revision as of 08:24, 3 October 2019
Line 83:		Line 83:

	mkfifo /tmp/sharkfin		mkfifo /tmp/sharkfin
	wireshark -k -i /tmp/sharkfin &		wireshark -k -i /tmp/sharkfin
	ssh user@remote-host "dumpcap -P -w - -f 'not tcp port 22'" > /tmp/sharkfin		ssh user@remote-host "dumpcap -P -w - -f 'not tcp port 22'" > /tmp/sharkfin

Line 89:		Line 89:

	mkfifo /tmp/sharkfin		mkfifo /tmp/sharkfin
	wireshark -k -i /tmp/sharkfin &		wireshark -k -i /tmp/sharkfin
	ssh root@192.168.1.1 "tcpdump -w - -f 'not tcp port 22'" > /tmp/wireshark		ssh root@192.168.1.1 "tcpdump -w - -f 'not tcp port 22'" > /tmp/wireshark

Jostrowski: Add remote capture

2019-10-03T08:01:18Z

Add remote capture

← Older revision		Revision as of 08:01, 3 October 2019
Line 56:		Line 56:
	----		----

	=== ~~Sniff traffic~~ with tcpdump ===		=== Remote capture with tcpdump and Wireshark ===

	;Installing tcpdump		;Installing tcpdump on the OpenWRT system
	# Allow SSH		# Allow SSH
	#: Go to "System" -> "Administration" and allow SSH		#: Go to "System" -> "Administration" and allow SSH
Line 67:		Line 67:
	# Install tcpdump		# Install tcpdump
	#: opkg install tcpdump		#: opkg install tcpdump
	~~; Use tcpdump~~

			'''Pipe tcpdump to remote Wireshark session [https://wiki.wireshark.org/CaptureSetup/Pipes Wireshark Wiki]:'''

			Remote Capture

			In bash syntax, remote capture is possible with the following command:

			wireshark -k -i <(ssh -l root remote-host "dumpcap -P -w - -f 'not tcp port 22'")

			The main problem is that you have to exclude the traffic generated by the ssh session from capturing. Several patches are available to do this, but excluding port 22 is probably the easiest solution for now.

			The second problem is that ssh cannot ask for a password on stdin. You should either set up ssh-agent, so that you don't need a password, or you should configure x-askpass to open a window for the password.

			This can be worked around by combining SSH with a FIFO.

			mkfifo /tmp/sharkfin
			wireshark -k -i /tmp/sharkfin &
			ssh user@remote-host "dumpcap -P -w - -f 'not tcp port 22'" > /tmp/sharkfin

			'''for openWRT this would look like:'''

			mkfifo /tmp/sharkfin
			wireshark -k -i /tmp/sharkfin &
			ssh root@192.168.1.1 "tcpdump -w - -f 'not tcp port 22'" > /tmp/wireshark

			As soon as Wireshark starts "listening" on the pipe, SSH will prompt for the password and allow you to continue. Wireshark can also be switched out for tshark and tcpdump can be used in place of dumpcap with slight variations on the above commands.


Line 82:		Line 104:
	* https://openwrt.org/		* https://openwrt.org/
	* https://openwrt.org/toh/zyxel/nbg6817		* https://openwrt.org/toh/zyxel/nbg6817
			* https://wiki.wireshark.org/CaptureSetup/Pipes

	[[Category:Documentation]]		[[Category:Documentation]]

Jostrowski: Add tcpdump

2019-09-26T10:47:31Z

Add tcpdump

← Older revision		Revision as of 10:47, 26 September 2019
Line 50:		Line 50:

	[[File:OpenWRT StatusScreen.png\|border\|800px]]		[[File:OpenWRT StatusScreen.png\|border\|800px]]




			----

			=== Sniff traffic with tcpdump ===

			;Installing tcpdump
			# Allow SSH
			#: Go to "System" -> "Administration" and allow SSH
			# Connect to SSH via terminal
			#: ssh root@192.168.1.1
			# Update system
			#: opkg update
			# Install tcpdump
			#: opkg install tcpdump
			; Use tcpdump






	== Used Hardware ==		== Used Hardware ==

Jostrowski: Created page with "== Summary == This is a tutorial how to install OpenWRT. For this example the Router Zyxel Armor Z2 AC 2600 MU-MIMO dualband wireless router is used. This tutorial is b..."

2019-09-26T10:02:12Z

Created page with "== Summary == This is a tutorial how to install OpenWRT. For this example the Router Zyxel Armor Z2 AC 2600 MU-MIMO dualband wireless router is used. This tutorial is b..."

New page

== Summary ==

This is a tutorial how to install OpenWRT.
For this example the Router [[Zyxel Armor Z2 AC 2600 MU-MIMO dualband wireless router]] is used.

This tutorial is based on [https://openwrt.org/docs/guide-quick-start/factory_installation First-time install from OpenWRT]

== Requirements ==

* Router supporting OpenWRT (visit [https://openwrt.org/toh/start OpenWRT])

== Installation ==

=== Find the openWRT installation image ===

# Filter for your router on the [https://openwrt.org/toh/start official openWRT page]
# Go to "Device Page" or "Device Techdata"
# Check "Firmware OpenWrt Install URL"
#: If you can not find '''“factory.bin”''' firmware file (true for 70% of all supported devices), a device-specific custom installation procedure is required (Assuming your device does not already have an older LEDE or OpenWrt version installed). You can find custom installation instructions at the following locations
# In the case of the Zyxel Router we only have '''"kernel.bin"''' and '''"rootfs.bin"''' file.
#: '''So we have to proceed with a custom installation'''

If you have a factory.bin please follow these instructions: [https://openwrt.org/docs/guide-quick-start/factory_installation OpenWRT factory install]

=== Custom installation for the Zyxel Router ===

Following the custom installation steps: [https://openwrt.org/toh/zyxel/nbg6817]

; OEM easy installation
: Telnet (or ssh, if you allowed ssh on the router webpage) to the router
:: login:root
:: password:1234(or the set password)
:: [[File:Zyxel sshLogin.png]]
:: Interestingly OpenWRT is already is already installed by default, but limited and modified by Zyxel
: copy the kernel.bin and rootfs.bin to the /tmp/ folder
:: scp j@192.168.1.67:/home/j/Desktop/openwrt-18.06.4-ipq806x-zyxel_nbg6817-squashfs-mmcblk0p4-kernel.bin /tmp/
:: scp j@192.168.1.67:/home/j/Desktop/openwrt-18.06.4-ipq806x-zyxel_nbg6817-squashfs-mmcblk0p5-rootfs.bin /tmp/
: copy to local folders:
:: printf "\xff" >/dev/mtdblock6
:: cat /tmp/openwrt-ipq806x-NBG6817-squashfs-mmcblk0p4-kernel.bin >/dev/mmcblk0p4
:: cat /tmp/openwrt-ipq806x-NBG6817-squashfs-mmcblk0p5-rootfs.bin >/dev/mmcblk0p5
:: sync
:: reboot -f
; Update openWRT
: Browse to http://192.168.1.1/cgi-bin/luci/mini/system/upgrade/ LuCI Upgrade URL
: Upload image file for sysupgrade to LuCI
: Wait for reboot

=== Enjoy ===

[[File:OpenWRT StatusScreen.png|border|800px]]

== Used Hardware ==

[[Zyxel Armor Z2 AC 2600 MU-MIMO dualband wireless router]]

== References ==

* https://openwrt.org/
* https://openwrt.org/toh/zyxel/nbg6817

[[Category:Documentation]]