-
Notifications
You must be signed in to change notification settings - Fork 565
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
Reverse Tethering with custom DNS doesn't work #4
Comments
In the released version, UDP connections are not logged correctly (fixed by 2ee5367), but I guess that some UDP packets are sent to 192.168.168.42. Could you please verify that the DNS server works from your computer by calling:
? Also, could you give more details about the device and its Android version? |
Also, could you give the device Android version, please? |
Oh, I noticed a similar issue when the heap size is set too small. I discovered that 200 MB is needed for it to work properly for the length of it use. The version of my Android OS is 5.1. |
@rom1v
|
Ah, that's it! Yes, all the HTTP requests are initiated by the Android device, so Android must be aware of the HTTP proxy. You can either change the proxy in your mobile browser settings, or configure it for the whole system (as soon as the applications read these settings) by executing this command:
or:
(but it is quite limited, e.g. you cannot provide login/password). To delete these settings:
Note: Deleting the settings does not remove the http proxy immediately, but only after a reboot, which makes its usage cumbersome. |
still have troubles with this one. Setting proxy settings from shell didn't help. |
Would this log help to pin point what am I doing wrong?
|
Yes, you should still use the custom DNS. To validate that the proxy settings are used, disable gnirehtet, connect to some wifi network from where the proxy is not accessible, and configure the proxy settings: you should not be able to load webpages.
For now, I think it does not help :-( |
I executed following command:
./gnirehtet rt -d 192.168.168.42
and here is the look of my stdout:
after some time browser on phone shows "Offline / Internet unavailable" message
The text was updated successfully, but these errors were encountered: