dark_pyrro

There are limits for new users due to the fact that there has been "abuse" over time. Not sure what the limits are, but I think it has been 5 messages before. I.e. that you have to post 5 messages and after that, it will be possible to post with less restrictions. That is only happening when you try to load the web UI, right? What happens if you try to ssh into the Pineapple? Try the diagnostics as well, if possible to reach http://172.16.42.1:1471/api/basic-diagnostics.html

How is the Bunny going to get access to the payloads?

Yes, either ssh or use the built-in terminal in the web UI https://docs.hak5.org/wifi-pineapple/ui-overview/introduction#web-terminal

What's the output of lsusb?

I'd bet my money on the fact that you won't find a bulletproof solution. It also depends on the one that finds it (or the one that gets it in the end). If it's a non tech person, it wouldn't understand what it is anyway. If it's a tech person (that's really interested in diving deeper into what it is), then it will be more difficult to hide things. But it all depends on if someone have the time to do the digging even if you're skilled enough to do it. I would probably do some changes under the hood of the Bunny to make it a bit more stealth, but that would limit the flexibility of the Bunny and also jeopardize the possibility to get further help or support. Or, use the USB Rubber Ducky (that has the HIDE_PAYLOAD command and is generally more "stealth" than the Bunny), but it all depends on what attack features that are needed.

Still not sure in what way the symlink fits into the scenario. It will most likely not help since it still can't find the relevant things needed to run Python3 (since paths are missing).

Since the topic of the thread was about the battery based Shark, connecting using serial won't be applicable. For the SJC, yes, For the battery based Shark, no.

phy2 should be radio2 which in turn is wlan2 that should be used to connect the Pineapple as a client to an existing wireless network (for internet access, etc.), so if that is failing then the other features should work (such as the management interface, the open AP). One thing that you could try that has worked for some users stuck in the config/setup loop is to connect using serial and check if you can see the following file in the file system: /etc/pineapple/setup_required If so, delete it and reboot. It's an "old trick" that was valid on earlier fw versions of the Mark VII, so not sure it applies in this specific case. Could be worth trying. Remember though that opening the Pineapple (to get access to the serial header) will void warranty, but I guess the warranty is gone with the wind anyway when it comes to this specific device.

I guess you got some help on Discord. If both 7601 radios where gone, I'd say it would be the USB hub on the Pineapple that was toast. But when just one of them is gone, I'd guess it's that specific radio. Difficult to say why, maybe the previous owner fried it running it without antenna for some reason. The only power related thing to try is to make sure you use a power source that provides at least 2A (it should run on less than that, but just to follow what the docs say).

So, this is a Tetra issue then, should have been posted in that section of the forums really, but, anyway... define "huge", how big are the icons and where in the UI? Screenshot?

Submit a support ticket. There was another Mk2 user that had similar issues on Discord recently and it was advised by Hak5 officials to contact official support about the matter. https://hak5.customerdesk.io/

100 Mbps

That's most likely because of the fact that OpenWrt can't bring the interface up. My bet is that there is some issue with the kmod/driver for that specific OpenWrt version for that specific chipset. It should generally work since it's fully functional on other kinds of Linux based distros, and of course on the Pineapple Mk7 where it's supported out of the box. It's identified/enumerated as something else instead of "link/ether" and doesn't seem to be able to handle the MAC address properly (it's set to 00:00:00:00:00:00 and if trying to set the MAC address of the interface and bring it up manually, it just throws and error back at you and that goes for both the RTL8152 and 8153 on the Nano). My advise is to use something that is known to work, and from my own experience, that is the previously mentioned ASIX chipset.

OK, knowing that you are running it inside a VM is something that would be good to know right from the start. You probably need to pass it from the host/hypervisor to the VM in the correct way. I'm not a VMware user since I use VirtualBox most of the time, but how to do that is most likely not a difficult thing to obtain via a Google search. This is most likely not an adapter issue, but instead something related to properly passing the adapter to the VM the way it's supposed to be done. (No pictures posted btw)

This should have been solved by parallel Discord discussions on the same subject

I can't remember that I've been needing to install anything specific to get MT7612 based adapters to work in Kali Linux. What's the output of lsusb before and after the adapter has been inserted?

That might be very true, I haven't tried it. It as just an assumption that it would lead to issues. Installing that package shouldn't be a problem on the Nano though. Did you run 'opkg update' before trying to install it?

That link is for the Mark VII, not the Nano. You will most likely not succeed getting an RTL8153 based device working with the RTL8152 kmod. One chipset that I know works along with the Nano is the ASIX AX88772B.

In what way did you verify that the chipset is supported/"in the image"?

(and... wrong section of the forums, the Nano has a specific section)

What chipset does the USB Ethernet adapter use?

From format? To format?

If you did a symbolic link, what did you link to if the library is missing?

You need to add things to the relevant paths to make Python know where things are since you have installed it to an alternative location.

Local server where? On the machine that the Bunny is connected to?