I've only been following this loosely, and may have missed the clear
statement. I apologise for that.
Windows 10 is inherently IPV6, and IPV4 is only bolted on. That has
occasional odd effects with routing (and with network timeouts and
discovery and other stuff), where the IPV4 follows an IPV6
6 months ago or so I have set up a system where I have two fiber connected LAN
segments in different locations tied together with OpenVPN into one single LAN
using addresses 192.168.117.x and 192.168.119.x.
The two segments have routers configured such that the 117 LAN connects with
OpenVPN to my
This may be a stupid question, but in the remote office, do you have a
route for 10.8.139.0/25? If not, then the clients can get packets to
the remote network, but the remote network can't get packets back to
the clients.
On Sun, Oct 2, 2022 at 7:44 AM Bo Berglund wrote:
>
> 6 months ago or so I
On Sun, 2 Oct 2022 07:55:42 -0400, Joe Patterson
wrote:
>This may be a stupid question, but in the remote office, do you have a
>route for 10.8.139.0/25? If not, then the clients can get packets to
>the remote network, but the remote network can't get packets back to
>the clients.
>
I think the
On 10/2/22 07:42, Bo Berglund wrote:
What could I change to make it work?
I suggest you use traceroute to see what paths the data are taking.
Doug
___
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
On Sun, 02 Oct 2022 09:59:59 -0400, Bo Berglund wrote:
>Now being outside both of these LAN sections over in the USA I can connect my
>laptop to my main vpn server on the 119 LAN and it works just fine for
>everything on the 119 LAN, but now the 117 segment is inaccessible
>
>This is the
