Open paulproteus opened 8 years ago
@kentonv curious for your +1/-1 on the above plan.
I guess this could conceivably go wrong if someone has configured a reverse proxy to sit in front of their server and therefore configured Sandstorm to listen on localhost only. I think this case could be handled by not using BIND_IP if it is in 127.0.0.0/8 -- clearly, using it in this case wouldn't work anyway.
Other than that case, this seems like clearly the right thing to do.
The two alternate plans both seem like the wrong solution to me, and overcomplicated in any case.
Is there a milestone or an idea of date resolution for this item? Thank you.
Hi @gpl34 ,
There isn't at the moment. I suspect that's not the answer you were looking for, but at least it is an answer. :)
Hope that helps! Let me know if you have any other questions.
Hi @paulproteus No, it's ok, it was just to be sure the problem was not going off radar. :-) Thank you!
Context:
BIND_IP=
to bind their Sandstorm to the right one.Plan:
sandcats.js
so that the UDP communication and HTTPS communication preferBIND_IP
.Other possible plans: