Skip to content
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: support custom control port #22

Closed
mantou132 opened this issue Apr 13, 2022 · 4 comments
Closed

Feature request: support custom control port #22

mantou132 opened this issue Apr 13, 2022 · 4 comments

Comments

@mantou132
Copy link

e.g: 443

@bolshoytoster
Copy link

@mantou132 you can change the constant in src/shared.rs:

bore/src/shared.rs

Lines 13 to 15 in 2d0dcf9

/// TCP port used for control connections with the server.
pub const CONTROL_PORT: u16 = 7835;

I could make it variable, probably through a command line option if there's no reason it can't be changed @ekzhang.

@ekzhang
Copy link
Owner

ekzhang commented Apr 13, 2022

Why would you change the control port to 443?

I would err on the side of strong conventions if there's no good reason to change or configure something.

@hkcomori
Copy link

hkcomori commented Jun 3, 2022

I want this feature too.
Currently, bore cannot be used in a network where the control port is blocked.
I want to avoid this by choosing a port that is less restrictive (eg 443).

@bolshoytoster
Copy link

@hkcomori as I suggested, if you don't mind compiling it yourself, you can change the CONTROL_PORT constant.

bore/src/shared.rs

Lines 16 to 18 in 9cd43f4

/// TCP port used for control connections with the server.
pub const CONTROL_PORT: u16 = 7835;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants