I have several l2tp tunnels to simplify VOIP connections at remote sites that if the tunnel drops the connection reestablishes with the wrong reply dst address. After it reconnects the reply-dst address is the public IP not the tunnel ip. I can bounce these by going into firewall connections, filter to traffic that is going over the tunnel and look for the public IP in the reply dst address column, kill that connection and it immidiatly reestablishes correctly. The one I just bounced is 6.30.1
Any ideas for a fix?
Example config
/interface l2tp-client
add connect-to=216.x.x.x disabled=no name=l2tp-out1 password=clientpass user=clientuser
/ip address
add address=10.10.100.1/24 interface=ether2 network=10.10.100.0
add address=10.5.50.1/24 interface=ether3 network=10.5.50.0
/ip firewall nat
add action=masquerade chain=srcnat comment="masquerade hotspot network" src-address=10.5.50.0/24
add action=masquerade chain=srcnat comment="masquerade voice traffic" dst-address=10.10.30.0/24 out-interface=l2tp-out1 src-address=10.10.100.0/24
add action=masquerade chain=srcnat out-interface=ether1
/ip address print
Flags: X - disabled, I - invalid, D - dynamic
# ADDRESS NETWORK INTERFACE 0 10.10.100.1/24 10.10.100.0 ether2
1 10.5.50.1/24 10.5.50.0 ether3
3 D 70.182.254.146/25 70.182.254.128 ether1
4 D 192.168.109.54/32 192.168.109.1 pptp-out1
/ip route
add distance=1 dst-address=10.0.0.0/8 gateway=10.9.0.1