-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
DNS not working #859
Comments
I have had this same issue for the past few releases |
Former release 1.4.3 was working well for me. Re-Imaged 1.5.3 several times now but the problem persists. Also tryied a fresh 1.5.3 install and 1.5.3 with restore from backup. Both variants have the same problem. Reverted back to 1.4.3 and there it works without problems. |
+1 |
Derek assign: dadav |
As far as I know, we didnt rly change anything related to dns. But we used a new raspbian, so maybe something changed there |
Omg, dnsmasq!!? |
@dadav
for some reason now rpi can't get dns from win10.. |
try: systemctl disable dnsmasq then reboot |
v1.5.3 still having problems with DNS. UPD: I have never used this DNS. Perhaps it was picked up via bt from a smartphone (I don't know where it came from), and google DNS from a PC, and because of this, such a problem arose. |
@LowSkillDeveloper I was looking at the bt-tether code for other reasons and remembered your message, because it looks like it was added in #279. I'm not exactly sure why this is the case... maybe @dadav could clarify. |
Yes! This is it. When i setting up, I turned ON "share_internet" to unload handshakes. |
It does seem odd that it ended up after your current DNS settings, considering it's supposed to |
Has any progress been made on this issue as I just had to re-flash my pwnagotchi due to a bad SD card and are running into the same issue. If I manually edit the /etc/resolv.conf file it doesn't solve the problem and disabling dnsmasq doesn't work either. |
i am also having this same issue. |
Adding "server=8.8.8.8@usb0" to /etc/dnsmasq.conf seems to help. |
I've had this issue since setting up my panagotchi about a month ago. Several reflashes later and I still have to edit resolv.conf every time I connect the unit to my pc or laptop (both windows 10). |
I found a thread somewhere that allowed a permanent fix: |
Neither disabling dnsmasq nor adding "server=8.8.8.8@usb0" did work for me. |
I can also confirm that adding "server=8.8.8.8@usb0" didn't work for me. |
Any new ideas about a solution? I'm really struggling to get it to work... |
fixed the issue for me. |
Try adding The resolveconf program is responsible for auto-generating the resolve.conf file during boot based on the files in Since raspbian is based on debian, see Debian Wiki: Defining The Nameservers It has been working stable for me, I hope this helps. |
Hello, fixed the issue for me. |
None of the solutions working for me , but I have Win7 |
@dadav very nice of you forking the repo, using the issues here to fix your own fork and not sending a PR back 👍🏻 |
So I have been having issues with this forever, but finally seem to have it worked out such that any of my units will auto connect to the web when I plug them in without going through a bunch of crud. I use windows 10: Connect the unit via usb. Go to network adapter settings, ipv4, and set up the pwnagotchi as 10.0.0.1, 255.255.255.0, 8.8.8.8 Go to settings of the network you use to connect to the web. Unshare then share that connection with the pwnagotchi. Then go back to check the ipv4 for the pwnagotchi and make sure they are correct. Should be able to ssh into the unit after that and use WinSCP or putty to find dnsmasq.conf and resolv.conf in /etc/. I changed resolv.conf to contain only: nameserver 8.8.8.8nameserver 8.8.4.4nameserver 9.9.9.9 I then disabled dnsmasq using: systemctl disable dnsmasq My dnsmasq.conf now says only: interface=br0 expand-hosts domain=example.com dhcp-range=192.168.20.100,192.168.20.150,12h |
It seems that issues seem to go unfixed for long periods of time. To me, this indicates that the lead developer is too busy to maintain the project anymore. Why would he send a PR back if it doesn't seem like you're trying very hard to "service" the community that is trying to use a product you made? After dealing with the issue of not being able to go into AI mode for days now, I've realized that there isn't much interest in resolving this issue. The newest image of pwnagotchi is broken and wont' go into AI mode. People have opened bugs about it. Looks like some are over a year old now without a viable fix. |
or maybe he trusts the community, that already did an amazing job in contributing, to help with the fixes given he has literally dozens of other projects he's working on ... who knows :D
oh, i didn't know that who's releasing unpaid software used by hundreds of people for free has an obligation to "service" the community, especially considering that such community is filled with other developers that can contribute with their code, fixes and PRs that get periodically merged ... noted!
this is not a product, otherwise you'd be paying for it and you'd get all the fixes you want as soon as you want. this is free software.
wow you're full of realizations and assumptions! i wish i was as informed as you seem to be about this whole thing :D |
one might also argue that the more people with your attitude are around (and unfortunately there're plenty), the less one is willing to actually work on anything they're asking for |
^^ are you suggesting that you haven't fixed this because you have a community of people "with the wrong attitude"? Or is it something more normal like, you're too busy with other things? The former would be an incredibly poor choice to have people believe. |
How much can the community pay you to fix this critical bug that cripples your project in the most recent version? I'm sure we could muster up something for your attention on this matter. |
let's say 10/90, but you're free to believe whatever you want :D adios |
I bet with all the time spent thinking out the replies here you could have made a patch to fix the not going into AI issue today. |
Describe the bug
When using internet connection sharing (Windows 10) I cannot get DNS working. Pwnagotchi always tells me "ping: google.com: Temporary failure in name resolution." when I try to ping google for example. I can ping the direct IP though, so internet connection sharing is in principle working.
I can temporarily fix the problem by editing "/etc/resolv.conf" and replace 127.0.0.1 with 8.8.8.8 in there. It will instantly start working after that. However the resolv.conf will be overwritten on each boot with 127.0.0.1 again.
Also tried setting a DNS server in the RNDIS Ethernet Interface in windows (8.8.8.8) but that has no effect. Tips are welcome!
Thanks!
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: