I want to install netcat on my genymotion to use wireshark. I tried alot and copied alot of netcat files in to genymotion but what ever i do the nc command will return nc not found.
It's been said than it can be downloaded from the belw link but i dont know what i should do:
https://android.googlesource.com/platform/external/netcat/+/master
Thanks
What you see in https://android.googlesource.com/platform/external/netcat/+/master is nc source code, not a ready-to-use binary.
To use it, you need to:
Compile the source using the NDK to produce a binary;
Send the binary to the device, for example using adb push path/to/your/nc /system/bin;
When this is done you should be able to open a shell inside your device with adb shell and use nc.
Related
So I am trying to get started developing on Fuchsia and I wanted to get the hello world component to run. However, following these steps doesn't work for me. I'm using core.qemu-x64 running on an Ubuntu 20.04 VM with Virtual Box. I have gotten the emulator to run with fx qemu -N but fx vdl start -N hasn't worked for me.
I run fx serve-updates but it just outputs "Discovery..." and never changes. Then I try to run fx shell run fuchsia-pkg://fuchsia.com/hello-world-cpp#meta/hello-world-cpp.cmx but it says "No devices found." It seem like this shouldn't be an issue because with Linux the device finder should automatically pick it up. Regardless I tried following the MAC instructions and setting the device with fx set-device 127.0.0.1:22. That just makes the run command say "ssh: connect to host 127.0.0.1 port 22: Connection refused". I also tried to set it to the device to the nodename outputted by the fx qemu -N command which is "fuchsia-####-####-####" but that just makes the run command say no devices are found again.
I have verified that I actually have the hello-world packages with the fx list-packages hello-world which outputs all the hello-world packages as expected.
Is there any way I can get the device to be discoverable by the shell command? Alternatively, can I run components like the hello-world component from the qemu emulator directly?
Please let me know if I can provide any additional information.
I guess I just wasn't patient enough. I assumed the emulator was done getting setup because it stopped giving console output and it allowed me to input commands but it seems I just had to wait longer. After 50 minutes of the fx qemu -N command running, the terminal that had fx serve-updates going finally picked up the device. Then I was able to execute the hello world component. It would be nice if the documentation at least gave an idea of how long the different commands would take before they'd be usable.
Hello there guys i have been trying to use hcitool on mac os terminal but whenever i type hcitool scan the following error is appeared -bash: hcitool: command not found i have tried pip install hci and pip install hcitool but the following error is shown
ERROR: Could not find a version that satisfies the requirement gatttool (from versions: none)
ERROR: No matching distribution found for gatttool
please help me with this
Commands such as hcitool, gatttool, hciconfig, etc. are part of the BlueZ package which works on Linux only. MacOS on the other hand is UNIX-core and therefore the commands will not run on a MacOS operating system. There have been hacks before to get some sort of functionality on MacOS OSs but the solution is always incomplete.
Your next best bet will be to use a Virtual Machine running a Linux guest (e.g. Ubuntu) and then use the BlueZ commands from within that VM OS.
I hope this helps.
Get yourself a Docker container up and running. You can write scripts that you keep in a shared volume between the host and the container (meaning you don't have to log into the container). You can then execute those scripts from your OSX terminal, to run in the container.
HTH
Hello I am using the following command on Ubuntu:
dig google.com #localhost -p 4000
I need a corresponding command on Windows.
You can install the digtool comes along with bind for windows. Use the below url to download bind - https://www.isc.org/downloads/
Once installed, dig will work on windows.
You can follow the instructions from this blog - http://nil.uniza.sk/linux-howto/how-install-dig-dns-tool-windows-10
I've recently bought a NodeMCU board and flashed Micropython in it.
I've read about the boot.py and main.py scripts, but I can't understand how to access them. I have succesfully connected to the Python REPL with the screen command and everything works fine.
Is there a way to mount it as an external drive on Mac OS X? Because I haven't found a way till now.
Thanks in advance!
you can enable the webrepl and upload via that
I've found this one package very helpful to upload vi the serial.
pip install mpfshell
python -m mp.mpfshell
> open COM3
> put main.py
micropython is cool...
Due to some questions I had about the NodeMcu and running Python on it, I just set up a pretty end-to-end documentation python2nodemcu on GitHub.
Viewing, downloading, uploading or listing files of the MicroPython filesystem has its own section there.
It utilizes Ampy, a Python library to connect to the MicroPython-based board via its serial connection. For listing all files for example, simply run python3 ampy/cli.py --port /dev/tty.{device-file} --baud 115200 ls.
The mpy-utils software package contains a tool called mpy-fuse that allows you to mount a MicroPython device from Linux or MacOS using FUSE. I found this tool through this video that describes how to set it up and shows how it looks like in action.
I have a fresh install of cygwin and xemacs on my home laptop. I'm trying to get to the packages list in xemacs, but not having much luck.
First of all I was getting an error message telling me "ftp.XXX.com seems not a pty". Following the instructions here I was able to tell efs to use lftp, and got past that error.
Now I get told:
Process not open for writing: #<process "*ftp yyy#ftp.xxx.org*" pid 9999 state:exit>
Any idea what's going on there?
The problem has to do with which ftp you are using. From the message, I believe you are trying to use the ftp that comes with Windows. It won't work as the native Windows ftp does not act like a pty.
The best solution I can suggest is to install the Cygwin port of ftp.