PPTP VPN Bridge and PCC

People,

I have been trying to make the PCC Wiki working in my setup. It does work but break my PPTP VPN. My VPN is using a subnet range that is not in the same LAN subnet, since I have few LAN addresses available. Since I never was able to make the appropriate route to make the PPTP subnet work with the LAN subnet, I bridged those two. Everything work perfectly till I try to incorporate PCC.

If I tried to use my PCC using the LAN interface as the in-interface, packets stays to zero.
If I use the Bridge interface as the in-interface, packets do seem to increase on 0:2 and 1:2, but VPN is no longer able to get to LAN (maybe because the !local does not include the vpn)

Any help would be really welcome.

Martin

use ‘src-address’ instead of ‘in-interface’

in mangle prerouting, first accept packets with dst-address=your_local_addresses, then mark routing for balancing

Chupaka,

Will try this after operation hour. My IPSec tunnels are also no longer working. Are Mangle rules have priority over firewall rules?

mangle forward is before filter forward. the rest is at http://wiki.mikrotik.com/wiki/Packet_Flow

I knew you would send me to that DFD! :slight_smile: I manage to get all my subnet talking between them! Your help is very appreciated. I even created a rule that work for relaying my email by marking the route from any LAN with dstport 25 and unchecking passthrough.

Two last questions:

  1. When using !local in pcc what does local refer to? local subnet? Does it include IPSec or PPTP VPN? or maybe just packet that are shout and not route?

  2. lastly when a packet hit a mangle that applies to it, does it stops evaluating other mangle rules unless passthrough is selected. Is this a correct understanding of passthrough in marking?

I finally got 35 rules for all my VLAN, Subnet ans tunnels, I know its far from being optimized but its working, and finally turned off my Juniper Netscreen 25


Hope this would help other and be able to help in the future. Hope some Mikrotik training will be available in Canada in the future.


Martin

  1. dst-address-type=!local means “the destination address is not an IP address on a router interface”. You wouldn’t want to mark connections that will terminate on the router itself, they shouldn’t get a routing mark later on.
  2. yes.

in mangle prerouting, first accept packets with dst-address=your_local_addresses, then mark routing for balancing[/quote]

Though i am been posting requests in the last few days on my load balaning issue without response from the house…i hope i will on this one. I have gotten my network to work with PCC…but when i connect through VPN, i can’t reach inside address except the gateways(exactly the same problem this post creator had) @Chupaka/Rockyboa i tried what you suggested but did not work, maybe i did it wrongly could you please type me the complete statement? below is my mangle:
[user@MikroTik] > ip firewall mangle print
Flags: X - disabled, I - invalid, D - dynamic
0 chain=input action=mark-connection new-connection-mark=wan2.4_conn
passthrough=yes in-interface=wan2.4

1 chain=input action=mark-connection new-connection-mark=INTERNET_conn
passthrough=yes in-interface=INTERNET

2 chain=output action=mark-routing new-routing-mark=to_wan2.4
passthrough=yes connection-mark=wan2.4_conn

3 chain=output action=mark-routing new-routing-mark=to_INTERNET
passthrough=yes connection-mark=INTERNET_conn

4 chain=prerouting action=accept dst-address=62.56.107.20/29

5 chain=prerouting action=accept dst-address=10.2.0.0/24

6 chain=prerouting action=mark-connection new-connection-mark=wan2.4_conn
passthrough=yes dst-address-type=!local
per-connection-classifier=both-addresses:2/0

7 chain=prerouting action=mark-connection new-connection-mark=INTERNET_conn
passthrough=yes dst-address-type=!local
per-connection-classifier=both-addresses:2/1

8 chain=prerouting action=mark-routing new-routing-mark=to_wan2.4
passthrough=yes connection-mark=wan2.4_conn

9 chain=prerouting action=mark-routing new-routing-mark=to_INTERNET
passthrough=yes connection-mark=INTERNET_conn

I know this is an old issue but I just ran into the same thing. Which rule are you suggesting to change to src-address? the mangle rules for the actual #/0 entries?

actually, every rule that is using ‘in-interface’ matcher, where you don’t know what interface to use

Dear friend,

I know this is an old post but I have experienced the same problem. Of course, I searched a lot and this is closest to the solution but however, for me it doesn’t work. I did like You suggested here but no luck with that. I am using 2 x PPP WAN connections with dynamic addresses and everything works like a charm except PPTP VPN… Can’t even ping from my PC to VPN gateway.

Can You help?

I have the same problem, did someone have solution.
Pls help