b23r0 / udppp Goto Github PK

it would be useful to have tcp protocol too

I have launched mmproxy with the following parameters: ./go-mmproxy -l 10.228.228.2:25565
the game server is running on 192.168.0.215, 10.228.228.2 is the ip wireguard
10.228.228.1 is on vds
10.228.228.2 on home pc.
how do I configure mmproxy to log in to a server with the proxy-protocol function enabled in nginx?
home pc:





(server minecraft run on 192.168.0.215)
How can I do so that I can log in to the server with the proxy-protocol in nginx option?

Hey - it seems like the "MMProxy" part is not working as expected.

I'm getting the below panic.

Using https://github.com/path-network/go-mmproxy it works as expected, so the issue is only in the -m 2 code not -m 1.

I would much prefer using udppp as Go's GC pauses are not desirable for my usecase.

Happy to help investigate and fix this further, but would need some guidance as I'm very unfamiliar with Rust 🙂

$ sudo $HOME/.cargo/bin/udppp -m 2 -b 0.0.0.0 -l 27016 -h 127.0.0.1 -r 27018 -p
2022-11-22T01:34:14.255Z INFO [udppp::mmproxy] listen mmproxy to 0.0.0.0:27016
2022-11-22T01:34:14.255Z INFO [udppp::mmproxy] listen mmproxy to 0.0.0.0:27016
2022-11-22T01:34:19.058Z INFO [udppp::mmproxy] recv from [92.232.X.X:44130] size : 51
2022-11-22T01:34:19.058Z INFO [udppp::mmproxy] bind new forwarding address [0.0.0.0:40403]
2022-11-22T01:34:19.058Z INFO [udppp::mmproxy] send to upstream [127.0.0.1:27018] real address [192.168.Y.Y:27005] size : 23
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 101, kind: NetworkUnreachable, message: "Network is unreachable" }', /home/mark/.cargo/registry/src/github.com-1ecc6299db9ec823/udppp-0.4.0/src/mmproxy.rs:101:84
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Any { .. }', /home/mark/.cargo/registry/src/github.com-1ecc6299db9ec823/udppp-0.4.0/src/main.rs:126:43

Related proxy command for mode 1 udppp -m 1 -b 0.0.0.0 -l 27016 -h 77.68.X.X -r 27016 -p

Server and client can simply be nc -ul 127.0.0.1 27018 and nc -u proxy-host 27016 respectively

Note that it seems to work when -m 1 is also running on the same host as -m 2 and the server - but of course this is not practical.