PPPwn
PPPwn copied to clipboard
README.md updated dependency instructions
When running sudo pip install -r requirements.txt normally, I get the error externally-managed-environment. pip recommends using pacman. Adding --break-system-packages works too but mixing pacman and pip packages is risky.
you need to use sudo pacman -S scapy that s it
You can alternatively install the python dependencies in a venv
as such:
$ python3 -m venv .venv
$ source ./.venv/bin/activate
$ pip install -r requirements.txt
Which, may be a preferable solution, since it'll work on any system, not just Arch. It's usually not a good idea to install python dependencies globally either-way, if you can avoid it.
True, I know venv also works. Maybe I should add all of this info, as an optional expandable section.
I think it could be argued setting up PPPwn through a venv
should be part of the default setup process for PPPwn, since that might help address similar issues to this on other systems as well with an externally managed Python environment.
On Mac pip does work, you use pip3
You can alternatively install the python dependencies in a
venv
as such:$ python3 -m venv .venv $ source ./.venv/bin/activate $ pip install -r requirements.txt
Which, may be a preferable solution, since it'll work on any system, not just Arch. It's usually not a good idea to install python dependencies globally either-way, if you can avoid it.
I agree with this. As often I'm concerned about conflicts with packages between Linux and Python, as seen in my PR.
This type of installation could be added as an second option or an alternative for Linux users.
same on ubuntu alternative way is to install using this command, since requirements.txt include scapy only
$ apt install python3-scapy
$ apt install python3-scapy
This is already in the PR. Also apt requires root permisions to install
$ sudo apt install
or
$ su
# apt install
```shell $ apt install python3-scapy
This is already in the PR. Also apt requires root permisions to install
$ sudo apt install
or
$ su # apt install
I don't recommend running this in root or su! This is a bad practice in security unless you really need it
It's better to make the commands using apt, assuming that they need to install it. Besides, probably the general population will use Debian-based distributions either way.
can you add to requirments in readme that the USB adapter of ethernet needs to be 3.0 otherwise if it's 2.0 you'll get stuck in "waiting for PADR"
can you add to requirments in readme that the USB adapter of ethernet need to be 3.0 otherwise if it's 2.0 you'll get stuck in "waiting for PADR"
Did it hang for an hour when using a USB 2.0?
can you add to requirments in readme that the USB adapter of ethernet need to be 3.0 otherwise if it's 2.0 you'll get stuck in "waiting for PADR"
Did it hang for an hour when using a USB 2.0?
It shows ip failure everytime in stage 0