PeasyWiFi - a reliable WiFi connection manager
PWF and DNScrypt
hello rcrsn51 are sonia, this thread was reported to me by matchpoint.
I would like to use on my xenialpup64 7.5 installed (USB stick) the PWF combined with the DNScrypt.
Everything should be connected via Ethernet.
Also I would like to use the primary and secondary DNS provided
from the Opennic Project.
In short words:
use DNScrypt with primary and secondary DNS specified by me.
Do you have any experience or suggestion of how I have to insert primary and secondary DNS?
P.S.
I read on page 15 this
" PWF uses udhcpc to acquire an IP address and DNS server from your ISP. But in rare cases, you may want to choose a different DNS server, like Google's 8.8.8.8.
1. Go to /etc and create a file named resolv.conf.head as follows:
Code:
nameserver 8.8.8.8
nameserver 8.8.4.4
2. Reboot and connect.
3. Check the file /etc/resolv.conf
4. To restore your ISP's choice of DNS server, just delete the file /etc/resolv.conf.head"
So I gather that if I want to address primary and secondary DNS taken from OpenNic I'll have to create a resolv.conf.head, right?
thanks sonia
I would like to use on my xenialpup64 7.5 installed (USB stick) the PWF combined with the DNScrypt.
Everything should be connected via Ethernet.
Also I would like to use the primary and secondary DNS provided
from the Opennic Project.
In short words:
use DNScrypt with primary and secondary DNS specified by me.
Do you have any experience or suggestion of how I have to insert primary and secondary DNS?
P.S.
I read on page 15 this
" PWF uses udhcpc to acquire an IP address and DNS server from your ISP. But in rare cases, you may want to choose a different DNS server, like Google's 8.8.8.8.
1. Go to /etc and create a file named resolv.conf.head as follows:
Code:
nameserver 8.8.8.8
nameserver 8.8.4.4
2. Reboot and connect.
3. Check the file /etc/resolv.conf
4. To restore your ISP's choice of DNS server, just delete the file /etc/resolv.conf.head"
So I gather that if I want to address primary and secondary DNS taken from OpenNic I'll have to create a resolv.conf.head, right?
thanks sonia
Last edited by soniabu on Sat 10 Feb 2018, 19:11, edited 1 time in total.
thx rcrsn51,
last question:
have you had experience with DNScrypt?
I have not trouble entering PWIFE the dnserver 127.0.0.2.
however I can not understand if this is a correct DNScrypt address in Xenialpup, because when I insert it and try to reach a website with palemoon
the browser stays in search without answering anything.
thx again
sonia
last question:
have you had experience with DNScrypt?
I have not trouble entering PWIFE the dnserver 127.0.0.2.
however I can not understand if this is a correct DNScrypt address in Xenialpup, because when I insert it and try to reach a website with palemoon
the browser stays in search without answering anything.
thx again
sonia
-
- Posts: 168
- Joined: Fri 26 Jan 2018, 20:54
Good afternoon Bill,
Nice program. Clean, straight-up interface. Works flawlessly on my Slacko 6.3.2, Tahr 6.0.5 and Xenial 7.5 saves. With Xenial I opted for the encrypted PIN. Upon completing the entry I'm unable to confirm the window with an "Enter" click. I see here, under number 9) Tips and tricks, Zigbert has code to "Press 'Enter' instead of clicking the 'Ok' button." Is this something you could easily incorporate into your peasywifi script?
Nice program. Clean, straight-up interface. Works flawlessly on my Slacko 6.3.2, Tahr 6.0.5 and Xenial 7.5 saves. With Xenial I opted for the encrypted PIN. Upon completing the entry I'm unable to confirm the window with an "Enter" click. I see here, under number 9) Tips and tricks, Zigbert has code to "Press 'Enter' instead of clicking the 'Ok' button." Is this something you could easily incorporate into your peasywifi script?
I don't understand. Are you talking about clicking the Encrypt button when you are setting up encryption?matchpoint wrote:Upon completing the entry I'm unable to confirm the window with an "Enter" click.
Or the OK button when you start a connection and enter the PIN?
Either way, they work fine for me in Xenial.
-
- Posts: 168
- Joined: Fri 26 Jan 2018, 20:54
Yes, the PIN window to connect appears at boot. I can enter my code but have to use the mouse and click to okay the window. I would prefer to type my code, hit the enter key and bypass the mouse altogether. Like in a terminal, you type your command and hit enter. I hope this clarifies the objective for you.
-
- Posts: 168
- Joined: Fri 26 Jan 2018, 20:54
rc.network in peasywifi only
Hi Bill,
I have been very impressed using peasywifi in BionicDog. Very fast connections, both on ethernet and wifi. Very easy to use.
I am so impressed that I decided to Woof up a copy of Artfulpup using only peasywifi, no frisbee, no sns, no network-wizard. After trying a few configurations I was able to make it work by linking /etc/pwf/rc.network to /etc/init.d/rc.network. It wouldn't work linking to /etc/rc.d which seems odd because that is the usual location for rc.network and indeed is the location in BionicDog.
Also, I may be misremembering my choice, but pinstall.sh doesn't seem to have had any effect on the Woof build, so I set it up manually.
Anyway, it works a treat, much improved speed of connection.
Thank you very much, J
I have been very impressed using peasywifi in BionicDog. Very fast connections, both on ethernet and wifi. Very easy to use.
I am so impressed that I decided to Woof up a copy of Artfulpup using only peasywifi, no frisbee, no sns, no network-wizard. After trying a few configurations I was able to make it work by linking /etc/pwf/rc.network to /etc/init.d/rc.network. It wouldn't work linking to /etc/rc.d which seems odd because that is the usual location for rc.network and indeed is the location in BionicDog.
Also, I may be misremembering my choice, but pinstall.sh doesn't seem to have had any effect on the Woof build, so I set it up manually.
Anyway, it works a treat, much improved speed of connection.
Thank you very much, J
Thanks for the report.
"Traditionally", /etc/rc.d/rc.sysinit does some setup stuff, then calls rc.network. It contains a bunch of legacy networking cruft, so PWF replaces it with a link to its own /etc/pwf/rc.network.
Putting the link in /etc/init.d would also work, provided that no other network manager is allowed to start. But if you removed the other ones from your build, that can't happen.
"Traditionally", /etc/rc.d/rc.sysinit does some setup stuff, then calls rc.network. It contains a bunch of legacy networking cruft, so PWF replaces it with a link to its own /etc/pwf/rc.network.
Putting the link in /etc/init.d would also work, provided that no other network manager is allowed to start. But if you removed the other ones from your build, that can't happen.
I try to change MAC address
ifconfig wlan0 down
macchanger -m xx:xx:xx:xx:xx:xx wlan0
ifconfig wlan0 up
using Dpup Stretch 7.5
test1
wireless:frisbee
network work
ifconfig wlan0 down
ifconfig wlan0 up
network work
test2
wireless:PeasyWiFi
network work
ifconfig wlan0 down
ifconfig wlan0 up
Network is unreachable
ifconfig wlan0 down
macchanger -m xx:xx:xx:xx:xx:xx wlan0
ifconfig wlan0 up
using Dpup Stretch 7.5
test1
wireless:frisbee
network work
ifconfig wlan0 down
ifconfig wlan0 up
network work
test2
wireless:PeasyWiFi
network work
ifconfig wlan0 down
ifconfig wlan0 up
Network is unreachable
devuan ascii build by dog fredx181
after some tries, PeasyWifi 4.6 connect my wireless in devuan ascii build by dog fredx181
Frisbee would do it too, just disable ethernet because one fights the other.
Frisbee would do it too, just disable ethernet because one fights the other.
- Attachments
-
- bbox.jpg
- Only some are available not alll, mine is listed
- (45.38 KiB) Downloaded 734 times
Last edited by hamoudoudou on Wed 27 Jun 2018, 07:12, edited 1 time in total.