Skip to content

Doesn't work with ENET Server in Docker Container #42

@bearrito

Description

@bearrito

I'm trying to use this so that I can tunnel an ENET service over TCP. https://github.com/lsalzman/enet

I'm building and running in a docker container.

My service runs with no issue while tcp2udp is not running, but when it is running I get an error, my error appears to originate from not being able to create a host/server. I'm guessing this is some sort of binding conflict. However, I've forced my server to use a completely different port than one below.

I've tried invoking tcp2udp in the following two ways.

/usr/local/bin/tcp2udp --threads=2 --tcp-listen 0.0.0.0:7446 --udp-bind=127.0.0.1 --udp-forward 127.0.0.1:6446 --tcp-recv-timeout=130 --nodelay

and

/usr/local/bin/tcp2udp --threads=2 --tcp-listen 0.0.0.0:7446 --udp-forward 127.0.0.1:6446  --nodelay

I do not have this issue on my local workstation.

Is there some sort of start-up or ordering condition of which to be aware? Namely, if I do not start tcp2udp allow my app to start, then exec inside the docker and run the above command, then I don't seem to have an issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions