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

RCON-port when running mc-router #126

Open
Elespecia opened this issue Oct 15, 2022 · 3 comments
Open

RCON-port when running mc-router #126

Elespecia opened this issue Oct 15, 2022 · 3 comments

Comments

@Elespecia
Copy link

Found mc-router when I was searching for a way to force the container to a subnet and it works great.
So now I'm getting into stacks with Portainer and have set up two different MC-servers. Also works great.

However, seems like the RCON-port is'nt forwarded through the mc-router. I've even tried exposing the ports as usal (different ports though since the bridge is same), but it doen't even work with that.
Is there a magic --mapping command to map those ports same as with the mc-ports?

@itzg
Copy link
Owner

itzg commented Oct 15, 2022

It's not possible to route rcon. There is no header packet that specifies which host is intended for connection.

@Elespecia
Copy link
Author

Oh, bummer. Feature request?

Seems it's not working on it's own either? Meaning 25565 goes through router to subdomain and the two RCON (26675 & another) directly to IP. Shouldn't it work?

@itzg
Copy link
Owner

itzg commented Oct 16, 2022

Oh, bummer. Feature request?

Feature request for whom? It's an established protocol.

Seems it's not working on it's own either? Meaning 25565 goes through router to subdomain and the two RCON (26675 & another) directly to IP. Shouldn't it work?

Do you mean with port mapping each container to a different port? That should work.

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

2 participants