Problems with tcp dynamic proxy

[k359792067]

Hello, I deployed the decoupled mode by default (APISIX version 3.9.1) with Helm (bitnami/apisix 3.2.2). Then I enableb tcp proxy and created stream_routes like this:

proxy_mode: http&stream
      stream_proxy:                 # TCP/UDP proxy
        tcp:                        # TCP proxy port list
          - 9101
          - 9102

curl http://127.0.0.1:9180/apisix/admin/stream_routes/1 \
-H 'X-API-KEY: 0000000000' -X PUT -d '
{
    "plugins": {
        "mqtt-proxy": {
            "protocol_name": "MQTT",
            "protocol_level": 4
        }
    },
    "upstream": {
        "type": "roundrobin",
        "nodes": [{
            "host": "127.0.0.1",
            "port": 1883,
            "weight": 1
        }]
    }
}'

curl http://127.0.0.1:9180/apisix/admin/stream_routes/1 \
-H 'X-API-KEY: 0000000000' -X PUT -d '
{
    "server_port": 9102,
    "upstream": {
        "nodes": {
            "127.0.0.1:31306": 1
        },
        "type": "roundrobin"
}'

The routes for the mqtt server and mysql server, both created successfully. But try to access port 9101 or 9102 of the apisix-dataplane pod, it's still not working, mqtt and mysql server. (10.42.0.34 is pod's internal IP). Http port 9080 is everything ok.

bash-5.1# telnet 10.42.0.34 9101
telnet: can't connect to remote host (10.42.0.34): Connection refused
bash-5.1# telnet 10.42.0.34 9102
telnet: can't connect to remote host (10.42.0.34): Connection refused
bash-5.1# telnet 10.42.0.34 9080
Connected to 10.42.0.34

[dosubot[bot]]

I found a similar closed issue regarding the mqtt-proxy plugin configuration, but no solution was found in the comments ^[1].

To troubleshoot the connection refusal issue with your TCP dynamic proxy in APISIX, consider the following steps:

1. Verify Stream Proxy Configuration: Ensure that the stream_proxy is correctly configured in your config.yaml file. The ports you specified (9101 and 9102) should be properly set up to listen for TCP connections.

2. Check Route Configuration: Make sure that your stream_routes are correctly configured. Verify that the server_port and upstream nodes are correctly defined and that the upstream services (MQTT and MySQL) are running and reachable.

3. Network Policies and Firewall: Check if there are any network policies or firewall settings in your Kubernetes cluster that might be blocking the connections to the apisix-dataplane pod on ports 9101 and 9102.

4. Pod and Service Connectivity: Ensure that the apisix-dataplane pod is correctly configured to accept connections on the specified ports. You can use tools like kubectl port-forward to test connectivity to the pod.

5. Logs and Error Messages: Review the APISIX logs for any error messages or warnings that might indicate what is going wrong with the stream routing.

By following these steps, you should be able to identify and resolve the connection refusal issue with your TCP dynamic proxy setup.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[k359792067]

Resolved, the problem was dataPlane.networkPolicy.extraIngress