04-06-2016, 11:24 AM
It seems Step 6 is really unnecessary. Once put into developer mode and the unit is cycled, you should be able to connect to it over wifi. You just need to know the IP. This can be obtained from your router easily and it saves having to assign static IPs or bridging the ethernet port (not really sure why you had to do this anyway.)
At any rate, after setting dev mode, rebooting, and grabbing IP....voila:
$ nmap -Pn -n 192.168.2.32
Starting Nmap 6.47 ( http://nmap.org ) at 2016-04-06 14:16 EDT
Stats: 0:00:01 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 26.15% done; ETC: 14:16 (0:00:03 remaining)
Nmap scan report for 192.168.2.32
Host is up (0.0092s latency).
Not shown: 998 closed ports
PORT STATE SERVICE
21/tcp open ftp
23/tcp open telnet
Nmap done: 1 IP address (1 host up) scanned in 1.56 seconds
At any rate, after setting dev mode, rebooting, and grabbing IP....voila:
$ nmap -Pn -n 192.168.2.32
Starting Nmap 6.47 ( http://nmap.org ) at 2016-04-06 14:16 EDT
Stats: 0:00:01 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 26.15% done; ETC: 14:16 (0:00:03 remaining)
Nmap scan report for 192.168.2.32
Host is up (0.0092s latency).
Not shown: 998 closed ports
PORT STATE SERVICE
21/tcp open ftp
23/tcp open telnet
Nmap done: 1 IP address (1 host up) scanned in 1.56 seconds