udp breaks without bindaddr defined

[adufray]

If you do not define a bindaddr and have multiple IP addresses, umurmur will not send UDP data back via the same source port as the user connected from, causing the client to not receive any UDP (because it doesn't match the tuple). For example:

Server has 1.1.1.1 and 2.2.2.2 configured.

Client (3.3.3.3) connects to 2.2.2.2.

Client (3.3.3.3) sends UDP data to 2.2.2.2.

Server replies to client via 1.1.1.1.

Client (3.3.3.3) not expecting data from 1.1.1.1 ignores it.

UDP breaks.

I think the solution would be for umurmur to keep track of the address the user connected to, and then reply via that address. Workaround is to simply define a bindaddr.

[fatbob313]

I think if the above scenario causes the described breakage, the problem is most likely with network/routing setup. See http://linux-ip.net/html/routing-saddr-selection.html