-
-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using a local WG server when you have a stupid modem. #1720
Comments
Hi there. Sorry, I don't think I fully understand your problem. You've got 2 peers. Only one is reachable at any given point in time. And you expect Rethink to connect via either of them (whichever is reachable) without needing to restart / edit the WireGuard configuration? If so, what is the role of NAT reflection here? And can you confirm if the official WireGuard app behaves the way you expect Rethink to? If not, can you explain what you expect to happen? Thanks. |
Normally I don't have this problem because I'm using hardware that's not brain dead and so whatever client or service I'm trying to use I just use my DDNS and either have it taken care of with the routers DNS server or with NAT reflection in that ABC123.DDNS.com always routes. Right now I'm stuck with a very stupid piece of hardware, So I can either directly use the LAN IP when I'm on the Wi-Fi, or when I leave the Wi-Fi, I previously had to change the config to use the DDNS. What currently seems to be mostly working, but is semi-automatic, is I have made a config with two peers, one for the local IP, and one for the external IP. And if I leave, if I'm not paying attention to my phone, for the most part the tunnel is coming up because rethink --I believe-- is trying both peers simultaneously and connects to one of them and eventually deems the tunnel to be up. I'm just wondering if this could be a little faster. It seems to retry the one, the pier that was working for longer than I would like before trying both of them. Or maybe it's only trying both of them because my cellular connection has reset a couple times. My building has an elevator. Unless the tunnel never gets up and I go into config and I toggle wireguard off and then I toggle it back on. At which point it tries both piers and the tunnel comes up. I guess I'm wondering would it make more sense for there to be a config option to specify a one peer as a backup for another peer? To tell, rethink, I want you to try this and then immediately try something else if it doesn't work. Or if you just make this more parallel and it's a bit faster to pick one. My hardware sucks. Can you help me with software make my user experience better? Is this too much trouble? Thanks. |
My modem doesn't do NAT reflection.
I was hoping by making a tunnel with 2 peers one for 192.168.etc.etc and one myWg.ddns.org it would just always try to connect to one of them.
And this works, but very manually. I have to toggle the tunnel or edit a peer to change the order they are listed in.
How should I be doing this?
Or can you allow a local IP alternative in Endpoint= ?
The text was updated successfully, but these errors were encountered: