[GH-ISSUE #621] Set a fixed local Port on the client #375

Closed
opened 2026-02-27 15:50:06 +03:00 by kerem · 3 comments
Owner

Originally created by @Gyzzorn on GitHub (Oct 5, 2017).
Original GitHub issue: https://github.com/quasar/Quasar/issues/621

I have seen that the client will cycle through a list of ports attempting to connect to the server with each - so far I have not been able to set this to a fixed port that I intend to use for testing. Anyone able to advise?

Originally created by @Gyzzorn on GitHub (Oct 5, 2017). Original GitHub issue: https://github.com/quasar/Quasar/issues/621 I have seen that the client will cycle through a list of ports attempting to connect to the server with each - so far I have not been able to set this to a fixed port that I intend to use for testing. Anyone able to advise?
kerem 2026-02-27 15:50:06 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@yankejustin commented on GitHub (Oct 6, 2017):

This was mentioned in the old Quasar chat room that we had -- does anyone remember?

<!-- gh-comment-id:334626484 --> @yankejustin commented on GitHub (Oct 6, 2017): This was mentioned in the old Quasar chat room that we had -- does anyone remember?
Author
Owner

@MaxXor commented on GitHub (Oct 9, 2017):

I'm not sure if I understand your question correctly, but when you only enter one host:port combination, the client will always try to connect to this and not cycle through others.
github.com/quasar/QuasarRAT@15b01116bf/Client/Config/Settings.cs (L14)

Or do you mean the local tcp client port? This is being decided by the system (see here) and I'm not sure why you would like to stick with one port there.

<!-- gh-comment-id:335271487 --> @MaxXor commented on GitHub (Oct 9, 2017): I'm not sure if I understand your question correctly, but when you only enter one host:port combination, the client will always try to connect to this and not cycle through others. https://github.com/quasar/QuasarRAT/blob/15b01116bf87a49742d4e6d65652d37fd34641cb/Client/Config/Settings.cs#L14 Or do you mean the local tcp client port? This is being decided by the system ([see here](https://stackoverflow.com/questions/5435779/is-the-port-used-by-a-tcp-client-to-connect-to-a-server-unavailable-for-other-tc)) and I'm not sure why you would like to stick with one port there.
Author
Owner

@Gyzzorn commented on GitHub (Oct 10, 2017):

It was mostly for testing purpose to test around outgoing firewall issues but that is fine thanks.

<!-- gh-comment-id:335577137 --> @Gyzzorn commented on GitHub (Oct 10, 2017): It was mostly for testing purpose to test around outgoing firewall issues but that is fine thanks.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Quasar#375
No description provided.