Talk:EM Mode - Revision history

Eep1mp at 12:35, 19 February 2008

Eep1mp — Tue, 19 Feb 2008 12:35:40 GMT

← Older revision		Revision as of 12:35, 19 February 2008
Line 8:		Line 8:
	Nmap finished: 1 IP address (1 host up) scanned in 1.078 seconds		Nmap finished: 1 IP address (1 host up) scanned in 1.078 seconds
	Port must be specified, otherwise nmap will scan only 1487 "well known" ports. I wanted to do a scan of all 65535 ports, but scanning UDP ports takes for ages, compared to scanning TCP ports. --Hanfbauer 20:17, 31 July 2006 (EDT)		Port must be specified, otherwise nmap will scan only 1487 "well known" ports. I wanted to do a scan of all 65535 ports, but scanning UDP ports takes for ages, compared to scanning TCP ports. --Hanfbauer 20:17, 31 July 2006 (EDT)
-
-	~~== LED ERROR CODES ==~~
-
-	~~The Buffalo website suggest an alternate reading of the error codes.~~
-
-	~~http://www.buffalotech.com/knowledgebase/users/kb.php?id=10011&category_id=0&sid2=~~
-
-	~~LED Flash Code Explanation and solutions:~~
-
-	The Info or Error light will flash a sequence of long flashes then a sequence of short flashes. The long flashes indicate the first number and the short flashes indicate the second number. For example: on the RED ERROR light, one long flash and five short flashes would be a disk error. On the ORANGE INFO light, two long flashes and seven short flashes indicate USB disk check.
-
-	~~Info (orange) light:~~
-
-	~~I10 - PCB overheat~~
-	~~I20 - internal HDD formatting~~
-	~~I21 - internal HDD checking~~
-	~~I22 - internal HDD recovering~~
-	~~I23 - System initialising~~
-	~~I25 - firmware updating~~
-	~~I26 - initialising web setting~~
-	~~I27 - USB disk checking~~
-	~~I28 - USB disk formatting~~
-	~~Error (red) light:~~
-
-	~~E00 (no light, beep only) - MPU error~~
-	~~E01 - DRAM data line error~~
-	~~E02 - DRAM address line error~~
-	~~E03 - RTC chip error~~
-	~~E04 - flash error~~
-	~~E10 - UPS power loss~~
-	~~E11 - fan error (RPM too low or stopped altogether)~~
-	~~E12 - cooling error (unable to remove heat by the fan)~~
-	~~E15 - disk error~~
-	~~E16 - unable to locate internal HDD~~
-	~~E17 - unable to communicate with the RTC chip~~
-	~~E21 - unable to communicate with the Phy chip~~
-	~~E22 - mount error~~

Eep1mp: LED ERROR CODES

Eep1mp — Tue, 19 Feb 2008 12:22:07 GMT

LED ERROR CODES

← Older revision		Revision as of 12:22, 19 February 2008
Line 8:		Line 8:
	Nmap finished: 1 IP address (1 host up) scanned in 1.078 seconds		Nmap finished: 1 IP address (1 host up) scanned in 1.078 seconds
	Port must be specified, otherwise nmap will scan only 1487 "well known" ports. I wanted to do a scan of all 65535 ports, but scanning UDP ports takes for ages, compared to scanning TCP ports. --Hanfbauer 20:17, 31 July 2006 (EDT)		Port must be specified, otherwise nmap will scan only 1487 "well known" ports. I wanted to do a scan of all 65535 ports, but scanning UDP ports takes for ages, compared to scanning TCP ports. --Hanfbauer 20:17, 31 July 2006 (EDT)
		+
		+	== LED ERROR CODES ==
		+
		+	The Buffalo website suggest an alternate reading of the error codes.
		+
		+	http://www.buffalotech.com/knowledgebase/users/kb.php?id=10011&category_id=0&sid2=
		+
		+	LED Flash Code Explanation and solutions:
		+
		+	The Info or Error light will flash a sequence of long flashes then a sequence of short flashes. The long flashes indicate the first number and the short flashes indicate the second number. For example: on the RED ERROR light, one long flash and five short flashes would be a disk error. On the ORANGE INFO light, two long flashes and seven short flashes indicate USB disk check.
		+
		+	Info (orange) light:
		+
		+	I10 - PCB overheat
		+	I20 - internal HDD formatting
		+	I21 - internal HDD checking
		+	I22 - internal HDD recovering
		+	I23 - System initialising
		+	I25 - firmware updating
		+	I26 - initialising web setting
		+	I27 - USB disk checking
		+	I28 - USB disk formatting
		+	Error (red) light:
		+
		+	E00 (no light, beep only) - MPU error
		+	E01 - DRAM data line error
		+	E02 - DRAM address line error
		+	E03 - RTC chip error
		+	E04 - flash error
		+	E10 - UPS power loss
		+	E11 - fan error (RPM too low or stopped altogether)
		+	E12 - cooling error (unable to remove heat by the fan)
		+	E15 - disk error
		+	E16 - unable to locate internal HDD
		+	E17 - unable to communicate with the RTC chip
		+	E21 - unable to communicate with the Phy chip
		+	E22 - mount error

Hanfbauer at 00:23, 1 August 2006

Hanfbauer — Tue, 01 Aug 2006 00:23:02 GMT

← Older revision		Revision as of 00:23, 1 August 2006
Line 7:		Line 7:
	MAC Address: 00:0D:0B:74:00:34 (Buffalo)		MAC Address: 00:0D:0B:74:00:34 (Buffalo)
	Nmap finished: 1 IP address (1 host up) scanned in 1.078 seconds		Nmap finished: 1 IP address (1 host up) scanned in 1.078 seconds
-	Port must be specified, otherwise nmap will scan only 1487 "well known" ports. I wanted to do a scan of all 65535 ports, but scanning UDP ports takes for ages compared to scanning TCP ports. --Hanfbauer 20:17, 31 July 2006 (EDT)	+	Port must be specified, otherwise nmap will scan only 1487 "well known" ports. I wanted to do a scan of all 65535 ports, but scanning UDP ports takes for ages, compared to scanning TCP ports. --Hanfbauer 20:17, 31 July 2006 (EDT)

Hanfbauer at 00:21, 1 August 2006

Hanfbauer — Tue, 01 Aug 2006 00:21:41 GMT

← Older revision		Revision as of 00:21, 1 August 2006
Line 1:		Line 1:
-	~~finding~~ the open UDP port with nmap while box is in EM mode:	+	Finding the open UDP port with nmap while box is in EM mode:
-		+	c:\Programme\Nmap>nmap -sU -p22936 192.168.1.4
-	c:\Programme\Nmap>nmap -sU -p22936 192.168.1.4	+	Starting Nmap 4.11 ( http://www.insecure.org/nmap )
-	Starting Nmap 4.11 ( http://www.insecure.org/nmap )	+	Interesting ports on 192.168.1.4:
-	Interesting ports on 192.168.1.4:	+	PORT STATE SERVICE
-	PORT STATE SERVICE	+	22936/udp open\|filtered unknown
-	22936/udp open\|filtered unknown	+	MAC Address: 00:0D:0B:74:00:34 (Buffalo)
-	MAC Address: 00:0D:0B:74:00:34 (Buffalo)	+	Nmap finished: 1 IP address (1 host up) scanned in 1.078 seconds
-	Nmap finished: 1 IP address (1 host up) scanned in 1.078 seconds	+
-		+
	Port must be specified, otherwise nmap will scan only 1487 "well known" ports. I wanted to do a scan of all 65535 ports, but scanning UDP ports takes for ages compared to scanning TCP ports. --Hanfbauer 20:17, 31 July 2006 (EDT)		Port must be specified, otherwise nmap will scan only 1487 "well known" ports. I wanted to do a scan of all 65535 ports, but scanning UDP ports takes for ages compared to scanning TCP ports. --Hanfbauer 20:17, 31 July 2006 (EDT)

Hanfbauer at 00:20, 1 August 2006

Hanfbauer — Tue, 01 Aug 2006 00:20:34 GMT

New page

finding the open UDP port with nmap while box is in EM mode:

c:\Programme\Nmap>nmap -sU -p22936 192.168.1.4
Starting Nmap 4.11 ( http://www.insecure.org/nmap )
Interesting ports on 192.168.1.4:
PORT STATE SERVICE
22936/udp open|filtered unknown
MAC Address: 00:0D:0B:74:00:34 (Buffalo)
Nmap finished: 1 IP address (1 host up) scanned in 1.078 seconds

Port must be specified, otherwise nmap will scan only 1487 "well known" ports. I wanted to do a scan of all 65535 ports, but scanning UDP ports takes for ages compared to scanning TCP ports. --Hanfbauer 20:17, 31 July 2006 (EDT)