[Pineapple as router?]

I've been running my pineapple mkV as my router / wifi repeater, and it seems to be doing just fine. Stability is decent, so long as I reformat the swap and check the sd ext4 partition every once in a while.

I do, however, leave the pineapple's network configs as default, rather than having dhcp issued elsewhere or what-not.

[[Support] Connect: A client mode WiFi manager script]

The point of using a MAC address is that it never changes. ESSIDs can change whenever someone wants the network to broadcast under a different name.

Forgive me, but that was not my question. I know why, what I asked was could it be made either optional (give user the choice), or if it's capable already by manual editing of the white/blacklists.

[[Support] Connect: A client mode WiFi manager script]

Question:

Can ESSIDs be listed white/black instead of BSSIDs? I've whitelisted a few APs, and they all get listed by MAC/BSSID with no reference made to the ESSID.

I'm wondering if, in the listing process, the ESSID could at least be shown as a comment for user reference. As well, if and ESSID could be utilized in situations where a single network has multiple APs to roam between, or open hotspots at chain stores where BSSID changes but ESSID remains same...

[[Script] Client Mode WiFi Check]

I'm presently using this script with DataHead's edit added. Seems to work so far.

However, my use-case is a bit different from that for which it is designed. I live full-time in a camper, and move around quite a bit. As a result, I'm not always on the same network, and of course, the $gateway variable would likely change with it. As well, I use a USB wlan2 when signal strengths require it, and unplug for power savings when they don't, so wlan1 or wlan2 would be a variable that changes.

Here is my semi-educated idea of how it worx:

1. script pings 8.8.8.8, if good, sleeps till next run. Or,

2. pings $gateway next, if good, tells you to check house AP's WAN connection. Or,

3. checks for existence of the interface it believes it should see, and if present, reconnects. Or,

4. Reboots pineapple

And here is how I envision it improved, and maybe working with the Connect Infusion:

1. Script runs (in my case, likely at startup), somehow AUTO-determines appropriate $interface and $gateway, pings 8.8.8.8 (or any other public IP), if good, sleeps until next run. Or,

2. pings $gateway, if good, tells you to check house AP's WAN, and runs "pineapple infusion connect -W" or some other reconnection routine with some mechanism to block current AP from being connected to for this run. Or,

3. checks for existence of $interface, and if available, runs "pineapple infusion connect -W" or other reconnection routine, starts again at step 1. Or,

4. Asks if another $interface should be used, or maybe even switches on own to first (or maybe last) available, and starts over.

I've VERY seldom seen any need to reboot the pineapple for interface detection, but we might need to keep a step 5 for worst-case reboot.

I'd love to see this script work in conjunction with the Connect Infusion, since this does much of what it does not, and vice versa. I've already posted in the Connect support thread very similarly, but wanted to bring some of my non-Connect-related suggestions here as well.

Edit: Seems the Connect infusion does much more than I realized. It already takes care of gateway auto-detect and connection checking. Between the 2, I think the only thing missing is an option to prevent associating with no-Internet AP's.

[[Support] Connect: A client mode WiFi manager script]

Here's a script I found, that I thought might be somewhat easily used in conjunction with your infusion:

https://forums.hak5.org/index.php?/topic/34276-script-client-mode-wifi-check/

Here is my semi-educated idea of how it worx:

1. script pings 8.8.8.8, if good, sleeps till next run. Or,

2. pings $gateway next, if good, tells you to check house AP's WAN connection. Or,

3. checks for existence of the interface it believes it should see, and if not present, reboots pineapple.

And here is how I envision it used here:

1. Script or infusion runs, somehow AUTO-determines appropriate $interface and $gateway (seems connect already does this?), pings 8.8.8.8 (or any other public IP), if good, sleeps until next run. Or,

2. pings $gateway, if good, tells you to check house AP's WAN. Or,

3. checks for existence of the interface, and if available, runs "pineapple infusion connect -W", auto-determines $interface and $gateway. Or,

4. Asks if another $interface should be used, or maybe even switches on own to first (or maybe last) available, and starts over.

I've VERY seldom seen any need to reboot the pineapple for interface detection, but we might need to keep a step 5 for worst-case reboot.

I'm interested to know what you think of this! I'm gonna put some of these suggestions in the script's original thread as well.

edit: Realized, after reading further, that Connect already does a full and complete auto-detection and connection checking routine! This tells me that if we can daemonize, maybe just add an option to momentarily reject currently connected AP if it shows local access only? That way, it keeps associating and checking until it finds one with valid net? Not always appropriate, of course, but in my case most often so.

[[Release] 2.2.X - Codename: Disassociotops]

I've discovered that with the new 2.2.0, libgd needs to be "reinstalled" to get the Monitor infusion to work. It seems libgd and dependencies were already installed, whether by me on sd and recovered, or as part of the rom, but was failing to be recognized as usable.

This may not be new to 2.2.0, as it had not worked for a few weeks.

[[Support] Connect: A client mode WiFi manager script]

That'd be great! Kinda' like the old autoap scripts for openwrt, we'd just have to whitelist all approved AP's as we came upon them, and let 'er rip!

I live full-time in a camper, and move about quite a bit, so this would be of great benefit to me, but I'm sure that others could benefit from it as well!

[[Support] Connect: A client mode WiFi manager script]

From what little info there is about this infusion, it sounds fantastic.

I do have a question or two:

1. If this is the case, "-w Whitelists AP by SSID. Prompts for password when required", then why "-W Checks for and connects to networks specified in the whitelist. Unencrypted netowrks only"? If the AP is whitelisted with password/crypto, why can't it be used with it? Or can it?

2. Could this, by chance, be easily daemonized, to run in a loop, -s every 30 seconds (check for net), and if not connected, immediately -W, otherwise sleep 30 and -s again? Or would this need to be scripted externally?