Recent content by dardar

Thanks, @ZebMcKayhan. Now that my remote system is powered up again, I took your advice and reverted the 192.168.50.1's WG Client Allowed IPs to 10.6.0.0/24,192.168.25.0/24. Everything works as expected, both locally and when connected by a roaming client. Hurray! Thanks again also to...

Hmmm. I'll get back to you after I am able to access my WG server again, but I am pretty sure that was the change I had to make in order to access the 192.168.50.0/24 subnet from a roaming client connected to the 10.6.0.1/32 WG server. It looks like @philote also included the 192.168.50.0/24...

Thanks to you both, @ThomsBe and @ZebMcKayhan, for your comments. I think you have helped me solve both of my main issues. I had been so focused on the roaming WG client configuration (both on my WG server router (192.168.25.1) and on the roaming WG client itself) that I didn't notice that the...

Thanks so much to @ZebMcKayhan, @Stick, and @ThomsBe for all of the details on their WG configurations. I have struggled with a similar setup for the last week, but I now have things working more-or-less as I would like them to work, thanks primarily to this discussion. Sorry to hijack the...

Thanks @L&LD. I don't see a difference in accessing the remote router when I turn off the VPN server on my local router, but the remote router is probably in an unstable condition at this point, so I wouldn't draw any conclusions from that. I discovered yesterday that my local router is also...

@L&LD I discovered today that the default IP address for these routers after a hard factory reset is actually 192.168.50.1, which is what I coincidentally chose to use for my remote router configuration. Could that be a problem? It wasn't an issue in 384.19. The more I think about this, the...

I am using 192.168.25.1 for my local router with 192.168.26.0/255.255.255.0 as the VPN subnet, and I am using 192.168.50.1 for my remote router with 192.168.51.0/255.255.255.0 as the VPN subnet. Is that okay? These two routers are serving pretty symmetric purposes, so I think the duplicated...

@L&LD Thanks so much for your reply. In view of comments I have read here, I did NOT restore from my backed up config file after the reset. I have the identical router locally, so once I had WAN access to the remote router, I opened side-by-side browser windows and used the settings pages from...

I told my sad story about losing access to a remote RT-AC86U during an update from 384.19 here: https://www.snbforums.com/threads/asuswrt-merlin-386-1-is-now-available.69783/post-661970 I had a friend stop by the house today, and she did a hard reset of the router (WPS hold during...

Thanks, bbunge. That was a good suggestion, although it didn't quite solve my problem. My home router uses the 192.168.25.0 subnet, and the VPN server assigns addresses for remote connections to 192.168.26.0. I tried to SSH with putty to my remote Pi's local address (192.168.26.2) and saw an...

Thanks, ATLga. You're right about trying the easy things first. I'll see if I can track down a neighbor to restart it. I just hope I don't need to do a full reset.

I have two RT-AC86U routers that were both running fine on 384.19 since last September or so. One of them is at a remote vacation house, and both were set up to run OpenVPN servers (using the same VPN settings for each) so that I can connect to them remotely through an OpenVPN client from my...