-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
issues with resolv.conf file #11
Comments
: not found2: |
sounds like you copied from a windows host into a vm. use nano to copy it, or if you can use vim. |
My ParrotOS computer won't go inline at all sue to this issue and I don't know how to transfer it except a usb drive. I have Kali on WSL in Widows and the GUI/Kex version but with no internet on ParrotOS computer. I had this issue a couple years ago on Kali and it ultimately kept me from Linux but I love it so I gave it another try. I'm surprised the same issue is still there and even more surprised that a lot more people aren't pushing this issue in droves. I'm staying in for the long haul. Thank you for your help! I guess I could ssh in but due to this issue I'm down to using ParrotOS live. |
bash is very space complainy. so put the script into vs code, because it sounds like the spacing and tabbing is messed up between how you copied it, and how it looks when you open it on the parrot system. |
I noticed a few issues with the resolv file not being created/updated after any vpn connections. This causes a massive issue for updating/doing anything as most operations require internet connections to exist. I have created this script to assist with this issue, not sure if this is a bug in how the resolv system implementation through systemd is handled by parrotOS or not, but this appears to fix most issues:
This script will need to be run as the root user in order to correct the issue presented by the broken link from
/etc/resolv.conf -> ../run/systemd/resolv/stub-resolv.conf
The text was updated successfully, but these errors were encountered: