Services that require both TCP and UDP on the same port only allow TCP. (Such as Mumble server)
Is there a workaround for this?
Originally created by @kapsikkum on GitHub (May 12, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/711
Services that require both TCP and UDP on the same port only allow TCP. (Such as Mumble server)
Is there a workaround for this?
You should be able to create two Pangolin resources of different protocols. Let me know if there are any issues with this.
<!-- gh-comment-id:2873881497 -->
@miloschwartz commented on GitHub (May 12, 2025):
You should be able to create two Pangolin resources of different protocols. Let me know if there are any issues with this.
Currently using the murmur mumble server with port 64738 open on both TCP and UDP with pangolin, and the server can only use TCP. UDP does not go through.
<!-- gh-comment-id:2876017608 -->
@kapsikkum commented on GitHub (May 13, 2025):
Currently using the murmur mumble server with port 64738 open on both TCP and UDP with pangolin, and the server can only use TCP. UDP does not go through.
I had a similar issue recently with a StorJ node not detecting quic support despite port 28967 TCP+UDP being forwarded, at least TCP working and everything set correctly in the compose and Traefik configuration.
What solved it for me was running Newt with network_mode: host.
<!-- gh-comment-id:2876697286 -->
@Momi-V commented on GitHub (May 13, 2025):
I had a similar issue recently with a StorJ node not detecting quic support despite port 28967 TCP+UDP being forwarded, at least TCP working and everything set correctly in the compose and Traefik configuration.
What solved it for me was running Newt with `network_mode: host`.
I tried with two Pangolin resources set to the TCP and UDP ports and I can't seem to reach mumble through it, I just migrated from Nginx so I think that the issue lies with Pangolin. Are there any log files I should provide? I don't containerize newt.
<!-- gh-comment-id:2895523327 -->
@TheRealTrip commented on GitHub (May 20, 2025):
I tried with two Pangolin resources set to the TCP and UDP ports and I can't seem to reach mumble through it, I just migrated from Nginx so I think that the issue lies with Pangolin. Are there any log files I should provide? I don't containerize newt.
Setting network_mode: host made no difference for me. UDP services are very spotty in general, for example, running a wireguard server has client handshake issues. Doesn't seem to be any errors either.
<!-- gh-comment-id:2897194750 -->
@kapsikkum commented on GitHub (May 21, 2025):
Setting `network_mode: host` made no difference for me. UDP services are very spotty in general, for example, running a wireguard server has client handshake issues. Doesn't seem to be any errors either.
@github-actions[bot] commented on GitHub (Jun 5, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
<!-- gh-comment-id:2942185052 -->
@github-actions[bot] commented on GitHub (Jun 5, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Jun 19, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
<!-- gh-comment-id:2986124507 -->
@github-actions[bot] commented on GitHub (Jun 19, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @kapsikkum on GitHub (May 12, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/711
Services that require both TCP and UDP on the same port only allow TCP. (Such as Mumble server)
Is there a workaround for this?
@miloschwartz commented on GitHub (May 12, 2025):
You should be able to create two Pangolin resources of different protocols. Let me know if there are any issues with this.
@kapsikkum commented on GitHub (May 13, 2025):
Currently using the murmur mumble server with port 64738 open on both TCP and UDP with pangolin, and the server can only use TCP. UDP does not go through.
@Momi-V commented on GitHub (May 13, 2025):
I had a similar issue recently with a StorJ node not detecting quic support despite port 28967 TCP+UDP being forwarded, at least TCP working and everything set correctly in the compose and Traefik configuration.
What solved it for me was running Newt with
network_mode: host.@TheRealTrip commented on GitHub (May 20, 2025):
I tried with two Pangolin resources set to the TCP and UDP ports and I can't seem to reach mumble through it, I just migrated from Nginx so I think that the issue lies with Pangolin. Are there any log files I should provide? I don't containerize newt.
@kapsikkum commented on GitHub (May 21, 2025):
Setting
network_mode: hostmade no difference for me. UDP services are very spotty in general, for example, running a wireguard server has client handshake issues. Doesn't seem to be any errors either.@github-actions[bot] commented on GitHub (Jun 5, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Jun 19, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.