mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #4398] [Feature Request] is it possible to support multiple mqtt clients if its not already supported #3473
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#3473
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
@JanzenJohn commented on GitHub (Sep 10, 2024):
MQTT runs via TCP, this is already supported
@Anzal-calixto commented on GitHub (Sep 26, 2024):
Hello @JanzenJohn yes it is but i wasnt able to tunnel multiple connections using tcpmux
@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.
@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.
You can use a tool like paint to make this easier
When possible the error case should have real error messages attached.
@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.