Posted: Sat Apr 05, 2014 21:00 Post subject: Re: See this out
How did you do it?
Jeian wrote:
MAC Address: CC:B2:55:**:**:** (D-Link International)
Device type: WAP
Running: Linux 2.6.X
OS CPE: cpe:/o:linux:linux_kernel:2.6.23
OS details: DD-WRT (Linux 2.6.23, MIPS)
Uptime guess: 3.080 days (since Tue Feb 04 16:33:36 2014)
Network Distance: 1 hop
IP ID Sequence Generation: All zeros
PORT STATE SERVICE VERSION
53/tcp open domain
80/tcp open tcpwrapped
|_http-title: D-LINK CORPORATION, INC | WIRELESS ROUTER | HOME
111/tcp filtered rpcbind
139/tcp open tcpwrapped
443/tcp filtered https
20005/tcp open btx?
(This is the original firmware of D-Link via NMAP scan)
Posted: Thu May 29, 2014 18:42 Post subject: Re: See this out
Yeah, I'd really be interested in knowing how you did that, as just about everywhere else seems to indicate its not possible (though admittedly everywhere that says its not possible is circa 2012 and older). Please, more info!
thekingr wrote:
How did you do it?
Jeian wrote:
MAC Address: CC:B2:55:**:**:** (D-Link International)
Device type: WAP
Running: Linux 2.6.X
OS CPE: cpe:/o:linux:linux_kernel:2.6.23
OS details: DD-WRT (Linux 2.6.23, MIPS)
Uptime guess: 3.080 days (since Tue Feb 04 16:33:36 2014)
Network Distance: 1 hop
IP ID Sequence Generation: All zeros
PORT STATE SERVICE VERSION
53/tcp open domain
80/tcp open tcpwrapped
|_http-title: D-LINK CORPORATION, INC | WIRELESS ROUTER | HOME
111/tcp filtered rpcbind
139/tcp open tcpwrapped
443/tcp filtered https
20005/tcp open btx?
(This is the original firmware of D-Link via NMAP scan)
Posted: Wed Jul 30, 2014 17:58 Post subject: Re: See this out
Jeian wrote:
MAC Address: CC:B2:55:**:**:** (D-Link International)
Device type: WAP
Running: Linux 2.6.X
OS CPE: cpe:/o:linux:linux_kernel:2.6.23
OS details: DD-WRT (Linux 2.6.23, MIPS)
Uptime guess: 3.080 days (since Tue Feb 04 16:33:36 2014)
Network Distance: 1 hop
IP ID Sequence Generation: All zeros
PORT STATE SERVICE VERSION
53/tcp open domain
80/tcp open tcpwrapped
|_http-title: D-LINK CORPORATION, INC | WIRELESS ROUTER | HOME
111/tcp filtered rpcbind
139/tcp open tcpwrapped
443/tcp filtered https
20005/tcp open btx?
(This is the original firmware of D-Link via NMAP scan)
Please , provide more info about installing dd-wrt firmware on Dir-655 !
Posted: Wed Aug 13, 2014 21:18 Post subject: Re: See this out
Jeian wrote:
MAC Address: CC:B2:55:**:**:** (D-Link International)
Device type: WAP
Running: Linux 2.6.X
OS CPE: cpe:/o:linux:linux_kernel:2.6.23
OS details: DD-WRT (Linux 2.6.23, MIPS)
Uptime guess: 3.080 days (since Tue Feb 04 16:33:36 2014)
Network Distance: 1 hop
IP ID Sequence Generation: All zeros
PORT STATE SERVICE VERSION
53/tcp open domain
80/tcp open tcpwrapped
|_http-title: D-LINK CORPORATION, INC | WIRELESS ROUTER | HOME
111/tcp filtered rpcbind
139/tcp open tcpwrapped
443/tcp filtered https
20005/tcp open btx?
(This is the original firmware of D-Link via NMAP scan)
Will the truth ever be known about how this individual did this achievement?
Posted: Mon Aug 18, 2014 17:42 Post subject: Re: See this out
Jeian wrote:
MAC Address: CC:B2:55:**:**:** (D-Link International)
Device type: WAP
Running: Linux 2.6.X
OS CPE: cpe:/o:linux:linux_kernel:2.6.23
OS details: DD-WRT (Linux 2.6.23, MIPS)
Uptime guess: 3.080 days (since Tue Feb 04 16:33:36 2014)
Network Distance: 1 hop
IP ID Sequence Generation: All zeros
PORT STATE SERVICE VERSION
53/tcp open domain
80/tcp open tcpwrapped
|_http-title: D-LINK CORPORATION, INC | WIRELESS ROUTER | HOME
111/tcp filtered rpcbind
139/tcp open tcpwrapped
443/tcp filtered https
20005/tcp open btx?
(This is the original firmware of D-Link via NMAP scan)
Hate to break your hearts, but this guy is messing with y'all. Doing an NMAP scan on my DIR-655 yeilds the same result. The tool attempts to guess the operating system and firmware version of whatever "computer" it scans to help the user determine how secure they are. When you scan a 655, its best guess is the DD-WRT firmware (It's 94% sure lol). It appears that he copied the dumbed down version of his results and posted them without actually clarifying that they were not accurate. Here's my full scan results. Check out the bolded section for the proof that it's NOT actually running this firmware.
P.S. He also states on the very last line of his post that he scanned the original (stock) firmware! :)
Quote:
Starting Nmap 6.46 ( http://nmap.org ) at 2014-08-18 12:05 Central Daylight Time
NSE: Loaded 118 scripts for scanning.
NSE: Script Pre-scanning.
Initiating Ping Scan at 12:05
Scanning 192.168.0.1 [4 ports]
Completed Ping Scan at 12:05, 0.13s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 12:05
Completed Parallel DNS resolution of 1 host. at 12:05, 0.03s elapsed
Initiating SYN Stealth Scan at 12:05
Scanning 192.168.0.1 [1000 ports]
Discovered open port 139/tcp on 192.168.0.1
Discovered open port 80/tcp on 192.168.0.1
Completed SYN Stealth Scan at 12:05, 1.26s elapsed (1000 total ports)
Initiating Service scan at 12:05
Scanning 2 services on 192.168.0.1
Completed Service scan at 12:05, 3.01s elapsed (2 services on 1 host)
Initiating OS detection (try #1) against 192.168.0.1
Retrying OS detection (try #2) against 192.168.0.1
Initiating Traceroute at 12:06
Completed Traceroute at 12:06, 0.02s elapsed
Initiating Parallel DNS resolution of 2 hosts. at 12:06
Completed Parallel DNS resolution of 2 hosts. at 12:06, 0.03s elapsed
NSE: Script scanning 192.168.0.1.
Initiating NSE at 12:06
Completed NSE at 12:07, 74.60s elapsed
Nmap scan report for 192.168.0.1
Host is up (0.0018s latency).
Not shown: 995 closed ports
PORT STATE SERVICE VERSION
80/tcp open tcpwrapped
|_http-title: D-LINK CORPORATION, INC | WIRELESS ROUTER | HOME
111/tcp filtered rpcbind
139/tcp open tcpwrapped
443/tcp filtered https
1720/tcp filtered H.323/Q.931
Aggressive OS guesses: DD-WRT (Linux 2.6.23, MIPS) (94%), Linux 2.6.24 (92%), Linksys WAP54G WAP (90%), Android 1.1 (Linux 2.6.25) (90%), Linux 2.4.20 (89%), Linux 2.6.16 - 2.6.28 (89%), Logitech Alert 750i camera (Linux 2.6.18) (89%), Cisco RV042 WAP (Linux 2.6) (89%), Sony Bravia KDL-46HS720 TV (89%), Linux 2.6.26 (88%)
No exact OS matches for host (test conditions non-ideal).
Uptime guess: 1.143 days (since Sun Aug 17 08:41:53 2014)