[GH-ISSUE #4398] [Feature Request] is it possible to support multiple mqtt clients if its not already supported #3473

Closed
opened 2026-05-05 14:13:59 -06:00 by gitea-mirror · 5 comments
Owner

Originally created by @Anzal-calixto on GitHub (Aug 22, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4398

Describe the feature request

Now i am able to connect an mqtt gateway to the tunnel server but could not find any methods to support multiple clients. Similiar to connecting multiple ssh clients

Describe alternatives you've considered

No response

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @Anzal-calixto on GitHub (Aug 22, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4398 ### Describe the feature request Now i am able to connect an mqtt gateway to the tunnel server but could not find any methods to support multiple clients. Similiar to connecting multiple ssh clients ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [X] Security - [ ] User Experience - [X] Test and Release - [X] Developer Infrastructure - [X] Client Plugin - [X] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 14:13:59 -06:00
Author
Owner

@JanzenJohn commented on GitHub (Sep 10, 2024):

MQTT runs via TCP, this is already supported

<!-- gh-comment-id:2341390310 --> @JanzenJohn commented on GitHub (Sep 10, 2024): MQTT runs via TCP, this is already supported
Author
Owner

@Anzal-calixto commented on GitHub (Sep 26, 2024):

Hello @JanzenJohn yes it is but i wasnt able to tunnel multiple connections using tcpmux

<!-- gh-comment-id:2376110372 --> @Anzal-calixto commented on GitHub (Sep 26, 2024): Hello @JanzenJohn yes it is but i wasnt able to tunnel multiple connections using tcpmux
Author
Owner

@github-actions[bot] commented on GitHub (Oct 18, 2024):

Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

<!-- gh-comment-id:2420952402 --> @github-actions[bot] commented on GitHub (Oct 18, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Author
Owner

@JanzenJohn commented on GitHub (Oct 18, 2024):

@Anzal-calixto

This project proxies raw TCP/UDP connections. The content doesn't matter, but it won't provide tcpmux if that's your question.

I'm not that familiar with tcpmux, the Wikipedia Page only told me it's been deprecated for ~8 Years. And that it works via TCP (which frp provides)

Also the error description "it didn't work" isn't very helpful.

  1. Please describe your Network configuration, and how frp fits in that configuration

You can use a tool like paint to make this easier

  1. Please explain your expected behavior
  2. Please explain the actual behavior you encountered

When possible the error case should have real error messages attached.

<!-- gh-comment-id:2421544702 --> @JanzenJohn commented on GitHub (Oct 18, 2024): @Anzal-calixto This project proxies raw TCP/UDP connections. The content doesn't matter, but it won't provide tcpmux if that's your question. I'm not that familiar with tcpmux, the [Wikipedia Page](https://en.m.wikipedia.org/wiki/TCP_Port_Service_Multiplexer) only told me it's been deprecated for ~8 Years. And that it works via TCP (which frp provides) Also the error description "it didn't work" isn't very helpful. 1. Please describe your Network configuration, and how frp fits in that configuration You can use a tool like paint to make this easier 2. Please explain your expected behavior 3. Please explain the actual behavior you encountered When possible the error case should have real error messages attached.
Author
Owner

@github-actions[bot] commented on GitHub (Nov 9, 2024):

Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

<!-- gh-comment-id:2465941642 --> @github-actions[bot] commented on GitHub (Nov 9, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
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: github-starred/frp#3473
No description provided.