Search the Community
Showing results for tags 'console'.
Found 3 results
Woke up this mornin', ... 3 little birds beside my doorstep... NOT! Hi all, Actually woke up this mornin' to a rotten Pineapple. So, I was hoping someone could help me. It worked fine last night, but this morning it kept connecting and disconnecting from the ethernet ports. (Wireless password didn't work) I've tried the following firmware: 2.5.4, 2.5.2, 2.4.2. I didn't really want to try any more because it's just plain not working. Reloading 2.5.4 and 2.5.2 get the same result as my original problem where it keeps connecting then disconnecting. 2.4.2 is the one that just gets the APIPA and doesn't get a DHCP address. Even setting it to 192.168.1.2 and trying to contact 192.168.1.1 doesn't work. How do you get to the UBoot? Can I connect to this thing with a console over the USB? I've done this with other SBCs (i.e. Raspberry Pi). HELP! Thank you, John Byrne
Hello: I have a BashBunny plugged into a Windows laptop and I want to connect to it via the serial port. Before posting this question I searched the forums on serial port and didn't get any related results back. In Device Manger, it shows up as COM3. This is my PuTTY config: Serial -- COM3 115200, 8, N, 1 When I launch the console, it just hangs there. When I bang on the Enter key, it just hangs there. Nothing happens... I never get a prompt. Any thoughts? Thanks!
I've been in the process of setting up and playing with my first wifi pineapple nano. It works like a charm. However, I'm bothered by something going on with the Management console (accessible at 172.16.42.1:1471). I have the nano setup to expose a "Management AP" as well as a "Open AP". It was my understanding that the Management AP is for managing the nano. For example, from my analysis laptop I can connect to the nano's "Management AP" and then I can direct my browser to 172.16.42.1:1471 to setup and monitor the nano. However, if I connect to the "Open AP" I am also still able to access the management console at 172.16.42.1:1471. I guess that I had figured the management console should only be accessible via the "Management AP" because otherwise any old sucker connected to the open AP can try to go to 172.16.42.1:1471 and then is able to see that they are actually connecting to a wifipineapple. Can someone explain why this would be the case? Is this just due to certain default settings that open AP clients can access the management console? Or is this "supposed" to happen?