I
I
inogda_dobriy2015-12-14 17:26:48
VPN
inogda_dobriy, 2015-12-14 17:26:48

Mikrotik rb951g 2hnd VPN L2TP - the client does not see the LAN, how to fix it?

configured like this: bozza.ru/art-248.html , created a connection on win8. It connects, the connection is seen on the router, but the client does not see the local network and does not ping computers in the LAN, although the network address is the same as in the main LAN
d5e4b316378a463dab02cca5fbf0f72a.jpg

Answer the question

In order to leave comments, you need to log in

4 answer(s)
M
mequasar, 2015-12-14
@mequasar

try NAT from LAN to VPN.

M
Maksim, 2015-12-14
@chumayu

Hands fall off if you take screenshots?
1.IP-Firewall-Filter rules
2.IP-Firewall-NAT
3.IP-Routes

I
inogda_dobriy, 2015-12-15
@inogda_dobriy

of course they won't fall off:
[*****@MikroTik] /ip> route print
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibition
# DST-ADDRESS PREF-SRC GATEWAY DISTANCE
0 ADS 0.0.0.0/0 **.**.228.1 0
1 ADC **.**.228.0 /24 **.**.228.128 ether1-gateway 0
2 ADC 192.168.85.0/24 192.168.85.1 wlan2 0
3 ADC 192.168.88.0/24 192.168.88.1 bridge1-local 0
[*****@MikroTik] /ip firewall>> filter print
Flags: X - disabled, I - invalid, D - dynamic
0 ;;; icmp
chain=input action=accept protocol=icmp log=no log-prefix=""
1 ;;; established
chain=input action=accept connection-state=established log=no log-prefix=""
2 ;;; related
chain=input action=accept connection-state=related log=no log-prefix=""
3 ;;; manage
chain=input action=accept in-interface=bridge1-local log=no log-prefix=""
4 ;;; VPN
chain=input action=accept connection-state=new protocol=udp in-interface=ether1-gateway dst-port=1701,500,4500 log=no log-prefix=""
5 ;;; VPN
chain=input action=accept connection-state=new protocol=ipsec-esp in-interface=ether1-gateway log=no log-prefix=""
6 ;;;
chain=input action=accept protocol=tcp in-interface=ether1-gateway dst-port=443 log=no log-prefix=""
8 ;;; all other drop
chain=input action=drop in-interface=ether1-gateway log=no log-prefix=""
9 ;;; Drop invalid connection packets
chain=forward action=drop connection-state=invalid log=no log-prefix=""
10 ;;; Allow established connections
chain=forward action=accept connection-state=established log=no log-prefix=""
11 ;;; Allow related connections
chain=forward action=accept connection-state=related log=no log-prefix=""
12 ;;; Allow access to internet
chain=forward action=accept src-address-list=inet in-interface=bridge1-local out-interface=ether1-gateway log=no log-prefix=""
13 chain=forward action=accept src-address-list=inet2 in-interface=wlan2 out-interface=ether1-gateway log=no log-prefix=""
15 ;;; https NAS
chain=forward action=accept protocol=tcp dst-port=443 log=no log-prefix=""
16 ;;; VPN
chain=forward action=accept protocol=ipsec-esp log=no log-prefix=""
17 ;;; VPN
chain=forward action=accept protocol=udp dst-port=1701,500,4500 log=no log-prefix=""
18 ;;; All other drop
chain=forward action=drop log=no log-prefix=""
/ip firewall nat>>
Flags: X - disabled, I - invalid, D - dynamic
0 chain=srcnat action=masquerade out-interface=ether1-gateway log=no log-prefix=""
1 chain=dstnat action=dst-nat to-addresses=192.168 .88.111 protocol=tcp in-interface=ether1-gateway dst-port=443 log=no log-prefix=""
ada5a018a50d494fa907af205c66bfba.jpg1766b3f68d1f44e5bb421edab4c23266.jpg76eb32a2d21042bdaea1b9cb7c635856.jpgeae76120af724e9fa8f8b2a52e69ea4e.jpg70baebbbdef54784b230056be63b3ab3.jpg517f1b691592455ba7c1086ef3f46081.jpg9f9e97f854e14bae9b113ddd99313148.jpg

A
athacker, 2015-12-16
@athacker

Draw a better diagram of what is connected and what IP addresses are on the interfaces. Where does the client connect from - from the Internet, or from the same LAN where he should get access? :-)

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question