How to make a ppp client see network 22 through proxy-arp and a common bridge from Windows on Mikrotik?

Question

VPN

There is a bridge with LAN, it has a network 192.168.60/22. sstp clients are given addresses from the pool 192.168.63/24.
The ppp profile says to shove clients into the bridge and proxy arp is enabled. But here the client does not see the addresses on the network, he sees only from his pool, looked at the addresses, the route 192.168.63/24 and ptp 192.168.60.1 <=> 192.168.63.254 are added, for example
How would I shove the 22 grid to him? Or will it not work that way? My servers are hanging on 192.168.60/24, I won’t shove clients there, they spoil all the beauty.
Of course, everything works if I write the route manually on the client, but I just want to escape from this and I want to, Windows itself does not know how to write routes with a script when raising the vpn, fencing batch files with a rasdial is generally a perversion.
In arp, the entire network on the bridge is visible, and clients too.

Answer 1

it is not very clear what you have there and how.
But if briefly and essentially, then.
For a remote computer to go to the local network through any type of VPN tunnel, it is necessary that
1. The computer had an address in the tunnel
2. The router had an address in the tunnel
3. The remote network was routed on the computer through the router's address in the tunnel and such traffic should be allowed.
You seem to have a problem with routes. Because the remote computer does not have a default route (as far as it can be seen from the description) through the router address in the tunnel, it is logical that it tries to find a mesh next to it, and not in the tunnel.
Outputs:
1. Assign a default gateway
2. Or issue addresses directly from the LAN pool
3. Assign routes dynamically \ script

Answer 2

The train of thought is correct, but clients, as you wrote, will only see the 192.168.63.0/24 network, because it is this mask that is issued with the IP address There
are two ways to solve the problem:
1. Issue a static route by the dhcp server:
/ip dhcp-server option
add code=121 name="stroute" value="0x16c0a800c0a83ffe"
/ip dhcp-server network set dhcp -option=stroute #in
this example, the route was assumed: 192.168.0.0/22 ​​gw 192.168.63.254
#value - the sequence of netmask and gateway values ​​in hexadecimal form
#id number of the corresponding rule #about
dhcp options is well described here
2. Give clients ip- address with subnet 22
/ip dhcp-server network set netmask=22
#id number of the corresponding rule #by default
, the mask of the specified network is given