-
Notifications
You must be signed in to change notification settings - Fork 205
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
Feature request: separately run Daedalus service and VPN interface #105
Comments
Nice suggestion! |
now working on it |
Excellent! We are all looking forward for this feature, thank you! |
I am wondering which ip address should DNS Server listening on? |
@PeratX Simple. Daedalus DNS server should definetely listen on 127.0.0.1, and optionally on enumerated NICs ip's, like 192.168.0.1, 10.1.10.1 etc. The best (and most suitable option) could be letting user make a choice: ip's to run on, and port number to serve. In my case, 127.0.0.1 and Port 5353 will do the trick (NetGuard defaults). Thank you for your prompt answer! |
Seems I need to write a separate server with different handlers again! |
@PeratX Humm... I did not know that an option that seems so simple and obvious could require so much efforts to implement.. apk size is not any problem for majority of contemporary devices though. IP should be selected from enumerated interfaces list (127.0.0.1 included), while the serving port indeed should be selected arbitrary by user from higher ports (>1024). Thank you very much for your ongoing interest in this valuable feature! |
Starting implementing it to Android |
@PeratX Hurray! |
@krissada983 Hi, I did not really understand why this quotation, it was me whò addressed the #10t, but as far as I know, it is not released yet, although PeratX invested much efforts into it. |
Hi all!
I would like to suggest a change in how user can use D.,
Consider this: if a possibility to run D. service and VPN interface separately existed (the way it is implemented in Orbox), we could use D. as a DNS proxy server, and forward DNS requests to it without occupying VPN. So, I can see how D. can be used side-by-side a firewall app, or SSH client or VPN client etc., which all occupy VPN (and only one is available on non-rooted devices).
The text was updated successfully, but these errors were encountered: