mirror of
https://github.com/quasar/Quasar.git
synced 2026-04-25 23:35:58 +03:00
[GH-ISSUE #238] MultiPort Listener [Server Side] & Backup DNS [Client Side] #109
Labels
No labels
bug
bug
cant-reproduce
discussion
duplicate
easy
enhancement
help wanted
improvement
invalid
need more info
pull-request
question
wont-add
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Quasar#109
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DragonzMaster on GitHub (May 29, 2015).
Original GitHub issue: https://github.com/quasar/Quasar/issues/238
I suggest to add multi-port listener to the server
and each port can have its own PW
We also can add backup DNS TO reduce the case of losing clients
@rabbitsmith commented on GitHub (May 29, 2015):
i support this idea.
@DragonzMaster commented on GitHub (May 29, 2015):
we will wait to know MaxXor opinion about that
@MaxXor commented on GitHub (May 29, 2015):
I already saw this in some other RATs. My question is: Has anyone actually used this? I didn't.
@DragonzMaster commented on GitHub (May 29, 2015):
I can understand this @MaxXor
You didn't use it but it would be useful for someone else
@rabbitsmith commented on GitHub (May 29, 2015):
what about adding freedns.afraid.org support as it requires only a secret key and does not need username and password for updating
@yankejustin commented on GitHub (May 29, 2015):
MultiPort listeners are not possible to implement on a TCP connection...
@DragonzMaster commented on GitHub (May 30, 2015):
What I mean Is making the server accept connection from (for Example) 2 clients one of them connecting through Port 4782 and the other connected to port 5782
the second point I mean to add a backup DNS to the Client and if the client can not connect to the primary DNS It will try to connect to Backup DNS @MaxXor
So how it can be impossible ?? as It is already implemented in other RATs ? @yankejustin
@yankejustin commented on GitHub (May 30, 2015):
@DragonzMaster I have looked into it more since my last comment and I just must say... What a mess trying to maintain it. It just is not at all convenient, especially for the difficulty of managing it with the lack of benefits.
@yankejustin commented on GitHub (May 30, 2015):
And about "the other RATs" that do this and that, just remember that because other projects have it, we may not have a use for it so it is not implemented.
Instead of comparing xRAT (as I unfortunately see often), please give a little bit of insight as to why some of these things are important to the project and perhaps a little cost (time, effort, etc.)-benefit analysis on it.
Above all, remember you can always implement it yourself. I knew almost nothing about computers and how they function, and I knew nothing about databases, websites, or coding at all only 2 years ago. ✏️
@yankejustin commented on GitHub (May 30, 2015):
As for the back-up DNS, that should be a separate enhancement for itself. I actually think it is useful thing to implement just so a client may know where to go. Perhaps it could be in a drop-down in the Builder Form and can be edited when connected to the server.
@DragonzMaster commented on GitHub (May 30, 2015):
Thanks Guys For Your Valuable Time
And I'AM NOT COMPARING IT WITH (ANOTHER RAT) BUT I AM HOPING TO SEE THIS PROJECT THE BEST EVER
I am SORRY I will Close this untill I finish my exams and see if i can implement it myself as you said @yankejustin
@yankejustin commented on GitHub (May 30, 2015):
I'd like it if you would open another issue only for the back-up DNS, though. That is something I am actually going to implement because I dislike relying on one unchangeable one. :)
@DragonzMaster commented on GitHub (May 30, 2015):
OK I will do it