baaronz Posted January 30, 2011 Share Posted January 30, 2011 Hi I've searched everywhere, but no luck. I want root access into the pineapple. It seems to connect, but It says "connection timeout" everytime I try to ssh/scp the thing. Help? Quote Link to comment Share on other sites More sharing options...
Netshroud Posted January 30, 2011 Share Posted January 30, 2011 Did you telnet in and run passwd? Quote Link to comment Share on other sites More sharing options...
Mr-Protocol Posted January 31, 2011 Share Posted January 31, 2011 I sense user error. Check IP addresses, as Psychosis said you have to connect via telnet and run passwd. Can you access the jasager interface or webif (if you installed webif)? Quote Link to comment Share on other sites More sharing options...
baaronz Posted January 31, 2011 Author Share Posted January 31, 2011 Already tried telnet, when I try to connect it says: Error connecting to 192.168.1.1 on port 23. Quote Link to comment Share on other sites More sharing options...
digininja Posted February 2, 2011 Share Posted February 2, 2011 nmap the IP you think the Fon is on and send us the results. Quote Link to comment Share on other sites More sharing options...
baaronz Posted February 2, 2011 Author Share Posted February 2, 2011 I ran a port scan on the pineapple, port 53 is open. Here are the results: Starting Nmap 5.50 ( http://nmap.org ) at 2011-02-02 11:39 Eastern Standard Time NSE: Loaded 57 scripts for scanning. NSE: Script Pre-scanning. NSE: Starting runlevel 1 (of 2) scan. Initiating NSE at 11:39 Completed NSE at 11:39, 0.00s elapsed NSE: Starting runlevel 2 (of 2) scan. Initiating ARP Ping Scan at 11:39 Scanning 192.168.1.1 [1 port] Completed ARP Ping Scan at 11:39, 0.67s elapsed (1 total hosts) Initiating Parallel DNS resolution of 1 host. at 11:39 Completed Parallel DNS resolution of 1 host. at 11:39, 0.00s elapsed Initiating UDP Scan at 11:39 Scanning 192.168.1.1 [1000 ports] Increasing send delay for 192.168.1.1 from 0 to 50 due to 11 out of 11 dropped probes since last increase. Increasing send delay for 192.168.1.1 from 50 to 100 due to max_successful_tryno increase to 4 Increasing send delay for 192.168.1.1 from 100 to 200 due to max_successful_tryno increase to 5 UDP Scan Timing: About 5.96% done; ETC: 11:47 (0:08:09 remaining) Increasing send delay for 192.168.1.1 from 200 to 400 due to 11 out of 21 dropped probes since last increase. Increasing send delay for 192.168.1.1 from 400 to 800 due to 11 out of 11 dropped probes since last increase. UDP Scan Timing: About 9.27% done; ETC: 11:50 (0:09:57 remaining) Increasing send delay for 192.168.1.1 from 800 to 1000 due to 11 out of 28 dropped probes since last increase. UDP Scan Timing: About 11.40% done; ETC: 11:52 (0:11:47 remaining) UDP Scan Timing: About 27.30% done; ETC: 11:54 (0:11:06 remaining) UDP Scan Timing: About 33.80% done; ETC: 11:54 (0:10:19 remaining) UDP Scan Timing: About 39.50% done; ETC: 11:55 (0:09:31 remaining) UDP Scan Timing: About 45.20% done; ETC: 11:55 (0:08:41 remaining) UDP Scan Timing: About 50.60% done; ETC: 11:55 (0:07:53 remaining) UDP Scan Timing: About 56.00% done; ETC: 11:55 (0:07:03 remaining) Discovered open port 53/udp on 192.168.1.1 UDP Scan Timing: About 61.60% done; ETC: 11:55 (0:06:15 remaining) UDP Scan Timing: About 66.70% done; ETC: 11:55 (0:05:26 remaining) UDP Scan Timing: About 73.97% done; ETC: 11:56 (0:04:36 remaining) UDP Scan Timing: About 79.07% done; ETC: 11:56 (0:03:41 remaining) UDP Scan Timing: About 84.17% done; ETC: 11:56 (0:02:47 remaining) UDP Scan Timing: About 89.27% done; ETC: 11:56 (0:01:53 remaining) UDP Scan Timing: About 94.37% done; ETC: 11:56 (0:00:59 remaining) Completed UDP Scan at 11:57, 1065.80s elapsed (1000 total ports) Initiating Service scan at 11:57 Scanning 32 services on 192.168.1.1 Service scan Timing: About 6.25% done; ETC: 12:17 (0:19:30 remaining) Service scan Timing: About 68.75% done; ETC: 12:00 (0:01:10 remaining) Completed Service scan at 11:59, 155.01s elapsed (32 services on 1 host) TRACEROUTE HOP RTT ADDRESS 1 1.77 ms 192.168.1.1 NSE: Script Post-scanning. NSE: Starting runlevel 1 (of 2) scan. NSE: Starting runlevel 2 (of 2) scan. Read data files from: C:\Program Files (x86)\Nmap OS and Service detection performed. Please report any incorrect results at http://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 1230.73 seconds Raw packets sent: 1372 (40.829KB) | Rcvd: 2181 (134.858KB) Quote Link to comment Share on other sites More sharing options...
digininja Posted February 2, 2011 Share Posted February 2, 2011 Should have been more explicit, can you do a default TCP scan, no parameters, just nmap and the IP address. Quote Link to comment Share on other sites More sharing options...
baaronz Posted February 3, 2011 Author Share Posted February 3, 2011 Done!; Regular scan: Starting Nmap 5.50 ( http://nmap.org ) at 2011-02-03 15:29 Eastern Standard Time Nmap scan report for 192.168.1.1 Host is up (0.00s latency). Not shown: 997 closed ports PORT STATE SERVICE 22/tcp open ssh 53/tcp open domain 80/tcp open http MAC Address: 00:12:CF:A4:A4:20 (Accton Technology) Nmap done: 1 IP address (1 host up) scanned in 44.78 seconds Quote Link to comment Share on other sites More sharing options...
digininja Posted February 3, 2011 Share Posted February 3, 2011 So telnet is closed and both ssh and http are open so you should be able to both ssh to it and browse to the web interface. The only reason I can see either failing is some odd firewall that is allowing you to see the port but not allowing connections but generally if they are there and open as far as nmap is concerned then they should both work. Quote Link to comment Share on other sites More sharing options...
baaronz Posted February 4, 2011 Author Share Posted February 4, 2011 I can access web file access, I can't ssh. I've tried filezilla/putty/telnet on port 22. I'm connecting to it but not getting a response... Maybe this new info would help? Quote Link to comment Share on other sites More sharing options...
digininja Posted February 6, 2011 Share Posted February 6, 2011 nmap says port 22 is open so there is no reason why you shouldn't be able to connect to it. What if you try to browse to it. Seems to me like the Fon is running fine but there might be a network issue, maybe multiple devices on the same IP? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.