Jump to content

Pineapple Mark VII connection issues


bakedmuffinman

Recommended Posts

Posted

is anyone else having connection issues when trying to setup an internet connection ?

Please keep in mind I have been using Pineapples since markiv.

first I tried wireless client mode (which has no other option then to use wlan2 ? is it meant to be this way? if so why is there a select interface drop down?).  scanned for SSIDs. selected my SSID. put in password (if I put in the wrong password the connect bar has a circling animation that just appears to circle forever. and I can no longer scan for SSIDs until I reboot.). then it looks as if it connects (green checkmark). I click save config. switch to another page. and switch back and it is no longer connected. and I would be lucky if it decides that it can scan again or not. 

 

Trying ICS through windows. which is normaly my preferred way with the other Pineapples. I go through the usual steps. (which normally would include at the end changing my internal LAN IP to 172.16.42.42.) before testing the network. and I still cannot get out. I check the routing table. and it has changed to 192.168.137.1 which is the IP address windows would like to use for my internal adapter when I first initialize ICS. I do not see a GUI option to change my routes ? this was removed ?

Posted

So I can connect to a wifi network but and load the news... but when I add modules and go to install dependencies it keeps erroring saying there is no network connection

Posted
1 hour ago, Br@d said:

So I can connect to a wifi network but and load the news... but when I add modules and go to install dependencies it keeps erroring saying there is no network connection

If you ssh into the pineapple can you ping 8.8.8.8 for example? or run 'opkg update' successfully? if so then the pineapple is online and working and the module has an issue. You should be able to browse to the modules directory and find the dependency script, run it manually and see if you get the actual error output. that might give a clue as to what the root problem is.

Posted
1 hour ago, Br@d said:

yup that's the weird thing, can ping and tested opkg without issue.

Should just be the modules dependency script then, see if you can find it on the pineapple and when you run it manually it might give more clues. either way its not the pineapple but more the module, maybe its looking for an old source or has a small typo etc. go looking, see what you find and report back!

Posted

found the issue in another thread.... for some reason the pineapple will not resolve "example.com" which it uses to check connectivity prior to installing.  ***note it resolves everything else*** 

 

 

  • 1 month later...
Posted

Unfortunately, that isn't enough information to diagnose the issue.

What firmware version are you on? What security does the AP you're trying to connect to have? Is there an error message?

Posted

Just received the Mk-VII and same issue - not able to connect device to WiFi network via web UI .

 

  1. Test machine:
    • macOS 10.14.6 Mojave
  2. Test machine connected to:
    • Pineapple Management Access Point
  3. Attempting to connect Pineapple to:
    • Google Nest WiFi mesh network with 1 router + 1 node
  4. On click "Connect":
    • POST
      http://172.16.42.1:1471/api/settings/networking/clientmode/connect
    • payload:
      {
        "ssid":"NETWORK_NAME_REDACTED",
        "bssid":"F0:72:EA:31:97:XX",
        "password":"NETWORK_PASS_REDACTED",
        "encryption":"mixed WPA2/WPA3 PSK/SAE (CCMP)",
        "hidden":false,
        "interface":"wlan2"
      }

       

  5. Error message in browser console: 500 Internal server error
  6. Note: in the POST request I can see the correct ssid and pwd being sent to Pineapple
  7. Response payload:
    • {"error":"connection failed"}

       

 

Posted
1 hour ago, everyday_wtf said:

Just received the Mk-VII and same issue - not able to connect device to WiFi network via web UI .

 

  1. Test machine:
    • macOS 10.14.6 Mojave
  2. Test machine connected to:
    • Pineapple Management Access Point
  3. Attempting to connect Pineapple to:
    • Google Nest WiFi mesh network with 1 router + 1 node
  4. On click "Connect":
    • POST
      
      http://172.16.42.1:1471/api/settings/networking/clientmode/connect
    • payload:
      
      {
        "ssid":"NETWORK_NAME_REDACTED",
        "bssid":"F0:72:EA:31:97:XX",
        "password":"NETWORK_PASS_REDACTED",
        "encryption":"mixed WPA2/WPA3 PSK/SAE (CCMP)",
        "hidden":false,
        "interface":"wlan2"
      }

       

  5. Error message in browser console: 500 Internal server error
  6. Note: in the POST request I can see the correct ssid and pwd being sent to Pineapple
  7. Response payload:
    • 
      {"error":"connection failed"}

       

 

SAME exact issue I'm having, and still no response to a unit exchange request!

Posted
18 hours ago, everyday_wtf said:

Just received the Mk-VII and same issue - not able to connect device to WiFi network via web UI .

 

  1. Test machine:
    • macOS 10.14.6 Mojave
  2. Test machine connected to:
    • Pineapple Management Access Point
  3. Attempting to connect Pineapple to:
    • Google Nest WiFi mesh network with 1 router + 1 node
  4. On click "Connect":
    • POST
      
      http://172.16.42.1:1471/api/settings/networking/clientmode/connect
    • payload:
      
      {
        "ssid":"NETWORK_NAME_REDACTED",
        "bssid":"F0:72:EA:31:97:XX",
        "password":"NETWORK_PASS_REDACTED",
        "encryption":"mixed WPA2/WPA3 PSK/SAE (CCMP)",
        "hidden":false,
        "interface":"wlan2"
      }

       

  5. Error message in browser console: 500 Internal server error
  6. Note: in the POST request I can see the correct ssid and pwd being sent to Pineapple
  7. Response payload:
    • 
      {"error":"connection failed"}

       

 

Thank you for the detailed report! It really does make a difference.

I'm not able to check right now, but perhaps there is an issue with connecting to WPA2/3 Mixed APs. I'll update this thread when the week starts and I've had time to investigate.

16 hours ago, Chiba said:

SAME exact issue I'm having, and still no response to a unit exchange request!

Unit replacements are for hardware faults, which this is extremely unlikely to be. Can you confirm if the AP you're trying to connect to is WPA2/3 Mixed also?

Thanks

Posted
10 hours ago, Foxtrot said:

Thank you for the detailed report! It really does make a difference.

I'm not able to check right now, but perhaps there is an issue with connecting to WPA2/3 Mixed APs. I'll update this thread when the week starts and I've had time to investigate.

Unit replacements are for hardware faults, which this is extremely unlikely to be. Can you confirm if the AP you're trying to connect to is WPA2/3 Mixed also?

Thanks

Foxtrot:

WPA2 PSK

 

Thank you Foxtrot

  • 3 weeks later...
Posted

Same problem here, but I even tried it on an open network. I'm using firmware 1.0.0. Scanning in the Wireless Client Mode takes a split second to populate with a number of networks, but attempting to connect to one of them results in an "exit status 1" error, and the spinning circle of death.

Posted
3 hours ago, DrChaos said:

I'm using firmware 1.0.0.

Please upgrade to 1.0.1.

Posted

Pff... for Windows ICS, it is a missing/incorrect route.

For a (very) quick and dirty fix, you can open a terminal and add:

route add default gw 172.16.42.42 br-lan

Is it just me, or Hak5 gear and sw quality is getting worse by every year?

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...