192.168.2.0/24 is simply a different segment.
Yes, it is. And that segment is not mentioned anywhere in OPs question. So why bring it up?
172.16.10.0/24 is also a separate subnet.
192.168.2.0/24 is simply a different segment.
Yes, it is. And that segment is not mentioned anywhere in OPs question. So why bring it up?
172.16.10.0/24 is also a separate subnet.
You’re describing NAT. There is no NAT in OPs question.
I’m talking about site to site VPN, not a client VPN with full tunnel that would get NAT’d. But ok Mr professor
How so? Your home computer gets a DHCP address from your home server. You VPN in and get assigned an address from the work DHCP.
I’m referring to both of your replies in this thread, in which you introduce a new subnet and NAT. This entire question is about both sites having the same subnet. You’re answering a different question.
What if you’re using the vpn connection specifically to make use of your home networks local DNS resolver and Ad blocking? Maybe there was no reason for my network to have anything other than the standard 192.168.1.1 but when I was initially configuring it, several people recommended changing that address for that use case.
“Those who can’t, teach.”
You might not have a lot of real world experience, I’m guessing then. Because there will be a lot
of things out of his control on his work network that could interfere with the routing. There’s a reason the typical advice is to go with an atypical DHCP range on your home network.