Hello, I have a RB493G that I’m trying to get working with PCC.
I have 2 new IPD-Slam connections from AT&T, they both seem to be connecting to the same subnet (108.200.248.###/22)
The internet works on the RB when I have one of these connections disabled, but dies when i turn the other one on. I think this is also the issue im having with getting PCC working.
Is there anything I can do to get this working with both connections??
I was looking at the same thing and had post on the forum here asking for the same and I don’t think it is possible just to be bonding those two connections. What you can do is to make some load balancing - or make a static route so specific IP’s on your lan use the second internet connection as gateway.
pilgrim
http://forum.mikrotik.com/t/need-help-to-understand-this-rule-routing-rule/48786/1
I was actually trying to do PCC on these 2 lines much like I’ve done w/ 4 DSL lines in the past. But when I set it up, nothing works.
ether1 → LAN has ip of 192.168.24.1
ether2 → DSL1 has DHCP’d address from AT&T 108.###.###.14#/22
ether3 → DSL2 has DHCP’d address from AT&T 108.###.###.15#/22
Both ether2 and ether3 are on the same subnet.
Here’s the code im using
/ ip firewall mangle
add chain=input in-interface=ether2 action=mark-connection new-connection-mark=wan1_conn
add chain=input in-interface=ether3 action=mark-connection new-connection-mark=wan2_conn
add chain=output connection-mark=wan1_conn action=mark-routing new-routing-mark=to_wan1
add chain=output connection-mark=wan2_conn action=mark-routing new-routing-mark=to_wan2
add chain=prerouting dst-address-type=!local in-interface=ether1 per-connection-classifier=both-addresses-and-ports:2/0 \
action=mark-connection new-connection-mark=wan1_conn passthrough=yes
add chain=prerouting dst-address-type=!local in-interface=ether1 per-connection-classifier=both-addresses-and-ports:2/1 \
action=mark-connection new-connection-mark=wan2_conn passthrough=yes
add chain=prerouting connection-mark=wan1_conn in-interface=ether1 action=mark-routing new-routing-mark=to_wan1
add chain=prerouting connection-mark=wan2_conn in-interface=ether1 action=mark-routing new-routing-mark=to_wan2
/ ip route
add dst-address=0.0.0.0/0 gateway=ether2 routing-mark=to_wan1 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=ether3 routing-mark=to_wan2 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=ether2 distance=1 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=ether3 distance=2 check-gateway=ping
/ ip firewall nat
add chain=srcnat out-interface=ether2 action=masquerade
add chain=srcnat out-interface=ether3 action=masquerade
/ip route
add dst-address=0.0.0.0/0 gateway=1.1.1.1%ether2 routing-mark=to_wan1 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=1.1.1.1%ether3 routing-mark=to_wan2 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=1.1.1.1%ether2 distance=1 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=1.1.1.1%ether3 distance=2 check-gateway=ping
Setting your route to an interface doesn’t really work unless your using a PPP interface. So try the above replacing the 1.1.1.1 with your gateway. Your gateway should generally stay the same even though assigned by DHCP.