Feature Ideas

I've been trying to figure out why wlan0mon wasn't hopping channels for months now even though _pineap INTERFACE LIST says its set to fast hop. Spent hours upon hours digging through like every config file, changing uci configs, trying to initialize the pineapd service with different arguments with no luck; no matter what it would only sniff channel 1. Well looking at the iw dev output, I noticed there was two phy0 interfaces, wlan0 and wlan0mon. Thinking about it, I was wondering if the wlan0 interface was locking it to that specific channel, then I stumbled across this block in /etc/config/wireless config wifi-iface 'dummy_radio0' option device 'radio0' option mode 'sta' option ifname 'wlan0' option disabled '0' option encryption 'wpa3' Well setting the 'option disabled' line to 1 got rid of that wlan0 interface, and now wlan0mon hops! My only question is, what is this dummy_radio0's purpose? It doesn't seem like it does anything at the moment, so there shouldn't be an issue disabling it I'd imagine. But I'm wondering if y'all are planning something with it in the future. I wanted to bring this up anyway as in the discord Drag0rn said wlan0mon should hop automatically given there are no AP's/Client mode enabled. But even with everything disabled it wouldn't hop until I made this change. Just so you guys are aware in the event this wasn't intentional

Hopefully it will make it easier to develop payloads for the pager. It would help everyone who wants to develop payloads because from my experience with Payload Studio it’s a grade environment to develop Payloads. Maybe add a new selection to the other presets.

Having a information selection on payloads where developers can add short descriptions so from the device prior to deploying a payload the information could be read to make sure its the correct payload.

I'd like a channel analyzer added to Recon, with the ability to switch between 2.4/5/6 GHz, and view the number of APs and/or Clients on each channel. It would be a bar graph with channels across the X access and devices on the Y axis. The wifi_guppy payload has similiar functionality but lacks pretty visualization.

there should be a simple way to use custom fonts. example: assets/font/{font_name}/ttfs with font family ttf variants in this folder. you can assign the font as global in the themes.json file or as a locally assigned submenu. then any text would appear as that font by default. you can also execute this font per line with some value key pair like "text_family": "{font_name}" plus other attributes like bold or italics. this allows for more that one font to be used by addressing them as instances. maybe even as class ids so you can have scalable options on when to use what fontbis available. currently using pngs to replicate the same effect is like hardcoding a non-scalable workaround. it takes more work and if ever anything changes it would likely break the theme.

I’d like to be able to sort this list by signal strength (I think this is what it does now?), packet count, connected clients, etc.

Some payloads include a readme.md. It would be nice to be able to view that from the pineapple ui

This could be used for sharing LSP for pager payload development. Or for tools to aid in the development of themes, for example: Locally test out Themes with the advantage of quicker reloading.Checks for the correctness of the json files or the size of the background images My first idea was for you guys to provide the tools but then I remembered that you have a lot to do so I think this would be the best solution.

As it is now, if client mode is enabled but not connected, the management AP will not broadcast. I will have to disable client mode, then disable and reenable management AP to get it to broadcast. This is kinda annoying as there's many times i'm using the pager in an area where i don't have the ability to connect client mode, and doing all the enabling/disabling takes a good bit of time. Great work guys, love yall

Tagged this as a bug report, but not really sure it's a bug. Anyway, it's the category that seems to fit the best. I'm not describing it all here since it's possible to read about it on the forums. Link to the thread on the forums below. The initial topic was about something else, but the _pineap "issue" was brought up in this post (and continued from that point in the thread) https://forums.hak5.org/topic/63351-pager-general-external-usb-wifi-dongle-support/#findComment-373395

I have noticed an increasing number of payloads from myself and others which are needing better graphics capability and resorting to shutting off the pager service to gain access to the framebuffer pineapplepager stop This works great but has side effects like killing the API etc. and of course you must wait for the pager service to come back up "system initializing" when the payload is complete. (Doom, Pong, Snake, Hakanoid etc) For this I have a recommendation for a firmware enhancement that could solve this issue. Feature Request for Hak5 Wifi Pineapple Pager A DISPLAY_YIELD / DISPLAY_RESUME command pair would solve this elegantly: Proposed DuckyScript commands DISPLAY_YIELD Pager service pauses rendering but keeps API alive payload draws directly to /dev/fb0 for full graphics DISPLAY_RESUME Return control to pager UI This yield/acquire pattern is standard for shared hardware resources in embedded systems. Why This Would Work: Minimal firmware change - The pineapple service already manages the framebuffer; it just needs to pause its render loop on commandAPI stays live - Web UI, remote access, PineAP, and all background services continue runningClean handoff - No race conditions from stop/start cyclingBackwards compatible - Existing payloads continue to work unchangedEnables rich payloads - Games, custom UIs, data visualizations become possible without sacrificing connectivity This is the smallest change that would enable full graphics capabilities while keeping all services running.

I absolutely love this device and on its initial firmware it was jaw dropping. Since updating to the latest firmware, I am finding that the device freezes a lot and swiftly after 1-3 minutes of use become unusable. Most recently I have updated my payloads using the payload which pulls and updates from the GitHub, however when attempting to do this for themes it completely crashed. Have there been reported bugs since this update to the firmware other than this? Do we know if this will get patched or do I need to perform a full factory reset?

Please can you add to the double tap menu a "Kill Payload" so that I don't have to hard reset stop it.

Bluetooth icon to access some setting like a ON/OFF for power, scanner for nearby, live scan or graphics I think the power option would benefits everybody, live scan or graphics I think would start more payloads around bluetooth. THANK TO ALL