January 16, 2018 at 3:30 am #12519
Testing the Pi-Tail build for a couple of days now. Everything is just working magically, apart from the issue with the external usb wifi dongles. This totally ruins the whole joy of Pi-Tail.
Is there a slightest possibility, both can coexist?
My dongle is 722n v1.
January 16, 2018 at 8:07 am #12521
It does work. Is your USB port in mass storage or ethernet or standard OTG mode?
Edit: Just saw the “ethernet.gadget” in the title. I think I got it to work before but let me look into it tonight.
It definitely works with OTG and I think with ethernet too but I haven’t got a dongle on me to test. Just switch around and see if that makes a difference.
Hope that helps,
January 16, 2018 at 5:40 pm #12524
Seems to work for me Today, not sure, what I was doing wrong before.
Seems to be power sensitive, but finally works.
Another thing, many pentensting tools are relying on network-manager to work properly and trying to set up interfaces, using it. Which, obviously, doesn’t work with Pi-Tail, out of the box.
So, is it doable, to modify Pi-Tail, to be network-manager based, keeping all the current features active?
January 17, 2018 at 8:51 am #12529
network-manager should work without any problems.
The reason for me disabling it, is to avoid it conflicting with your main management channel until that is fully set up.
Once you’ve configured your main connection you can just re-enable it.
I’m surprised that there are tools requiring it though, generally it’s the other way around. Have you got an example? I’d like to dig into it.
January 16, 2018 at 9:34 pm #12525
Another thing, I want to try to implement, is to connect Pi Zero W to my android phone, via the ftdi device, for the console access, to spare the only usb port.
January 17, 2018 at 1:35 am #12526
Tried using the serial, have to enable_uart=1 in config.txt, to activate it, otherwise nothing happens.
Sadly, it crashes on start up, with kernel panic error.
Any possible solution?
January 17, 2018 at 8:25 am #12527
Are you trying to connect via the GPIO pins?
I’m not sure if anyone has ever get it to work properly. Using Bluetooth, running the Pi at full clock speed, and using UART serial has never worked reliably as far as I know.
Do you have any information to the contrary? I wouldn’t mind giving it another try.
January 17, 2018 at 8:33 am #12528
Actually, after running the sd card with fsck, fixed the kernel panic issue.
I’ve been testing the terminal connection via GPIO pins, for a few hours now.
Mostly, it’s working just fine.
The only issue, I encountered so far, one of the scripts is shooting out “curses.error: curs_set() returned ERR” error, which seems to be connected with the terminal type.
January 17, 2018 at 9:00 am #12530
Isn’t that awfully slow?
You must be logged in to reply to this topic.