TCP Proxy Support?

[ccwxl]

I see the supported application layer protocol proxy. So does TCP support? There are scenarios based on Netty's TCP persistent connection applications. IoT scenarios.

[benja-wu]

Hi @siaron
Currecntly，Easegress is an L7 traffic orchestration system.

• It doesn't support work as a TCP proxying right now. However, as being a modern traffic orchestration system, I believe it should be TCP supported in the future.

• We are working on support MQTT proxy. And WebSocket proxy supporting had been done. MQTT proxy is aiming for IoT scenarios too, if u are also interested, feel free to join in our design issue [feature] MQTT Proxy for Message Queue #187.

• quick brainstorm I think TCP supporting should be implemented into the TrafficController of Easegress. Then the whole raw TCP connections can be managed in one place, so the WebSocket proxy and MQTT proxy can benefit from this low-level feature too.

[jxd134]

Hi @siaron
Currecntly，Easegress is an L7 traffic orchestration system.

* **It doesn't support work as a TCP proxying right now**. However, as being a modern traffic orchestration system, I believe it should be TCP supported in the future.

* We are working on support `MQTT proxy`. And `WebSocket proxy` supporting had been done. `MQTT proxy` is aiming for IoT scenarios too, if u are also interested, feel free to join in our design issue [[feature] MQTT Proxy for Message Queue #187](https://github.com/megaease/easegress/issues/187).

* **quick brainstorm** I think `TCP supporting` should be implemented into the `TrafficController` of Easegress. Then the whole raw TCP connections can be managed in one place, so the `WebSocket proxy` and `MQTT proxy` can benefit from this low-level feature too.

Agree with you.
But if you want to put tcp proxy in TrafficController, it should have a good design.

[benja-wu]

Hi @siaron
Currecntly，Easegress is an L7 traffic orchestration system.

* **It doesn't support work as a TCP proxying right now**. However, as being a modern traffic orchestration system, I believe it should be TCP supported in the future.

* We are working on support `MQTT proxy`. And `WebSocket proxy` supporting had been done. `MQTT proxy` is aiming for IoT scenarios too, if u are also interested, feel free to join in our design issue [[feature] MQTT Proxy for Message Queue #187](https://github.com/megaease/easegress/issues/187).

* **quick brainstorm** I think `TCP supporting` should be implemented into the `TrafficController` of Easegress. Then the whole raw TCP connections can be managed in one place, so the `WebSocket proxy` and `MQTT proxy` can benefit from this low-level feature too.

Agree with you.
But if you want to put tcp proxy in TrafficController, it should have a good design.

Yes!, I was thinking about treating the TCP proxy as the HTTPServer in TrafficController. Indeed, it will be a big project. I think we will build up enough scenes when finishing WebSocketProxy and MQTTProxy, then it's time to bring Easegress into the L4 scenario.

Welcome to join us for this big, excited feature!

[benja-wu]

Since we had opened a design discussion issue #229 for this topic, let me close this one.
Welcome to join us in #229 .