Page 1 of 1
force ip cloud to update from WAN1
Posted: Mon Sep 07, 2015 1:32 pm
by freemannnn
i am using ip cloud reguraly to connect remotely to my customer routers.
in an installation i have to add an extra dsl (ether5=WAN2-dhcp) for more bandwidth.
my first wan (WAN1-PPPOE) modem is in bridge mode.
when wan2 is enable ip cloud is using this one to update and i have no remote access.
is it possible to tell ip-cloud to use only pppoe-out1 ?
Re: force ip cloud to update from WAN1
Posted: Thu Sep 10, 2015 3:00 pm
by CyberT
This may not be the most elegant way, But you can have a look at the server that the IpCloud speaks to and create a route for that out the first interface, the issue i would guess is that the wan2 device has a 0.0.0.0/0 in the main table that has a higher preference\lowwer metric than the wan2 device, another work around is to disable the add default route setting under the PPPOE dialer or the DHCP client, and then that would resolve your issue, you can then create your balancing 0.0.0.0/0 with a higher metric, say 2 if your other one is 1, in your main routing table.
force ip cloud to update from WAN1
Posted: Thu Sep 10, 2015 3:08 pm
by freemannnn
Wouldnt be easier to exist an option in ip cloud to ask from which wan will be routed?
Re: force ip cloud to update from WAN1
Posted: Thu Sep 10, 2015 3:11 pm
by CyberT
If that option existed you would very easily force cyclic data, Its better for the Tik to communicate back out the interface it receives the data especially for secure data.
Re: force ip cloud to update from WAN1
Posted: Thu Sep 10, 2015 3:21 pm
by marrold
If that option existed you would very easily force cyclic data, Its better for the Tik to communicate back out the interface it receives the data especially for secure data.
I dont understand what you're saying, sorry
Re: force ip cloud to update from WAN1
Posted: Thu Sep 10, 2015 3:29 pm
by CyberT
Its Caused when your data comes in the one interface, and leave via the other interface(taking a different path back), that in theory can happen/and does happen on the internet, but when you have secure sessions a lot of the security is based on the session that requires the data to come from the original IP's that the session was authenticated on, otherwise it view it as "session injection" as some data is now coming from another IP, and it wont be matched with the right session, and so forth... This is just such a loose and open ended way to try and explain the idea behind it, it is by no means factually correct.
Re: force ip cloud to update from WAN1
Posted: Thu Sep 10, 2015 3:51 pm
by marrold
The statement is true, but I dont understand how it applies to forcing IP Cloud to use a specific interface? Traffic would go in and out the same IP.
Re: force ip cloud to update from WAN1
Posted: Fri Sep 11, 2015 9:42 am
by CyberT
that statement is flawed, traffic will always leave the interface that has the lowest metric for the dst in the routing table, thats how you can send traffic to one WAN or the other based on routing, so with that you can easily create an issue where trafic comes in the one interface and leaves the other. If you have an isp that support
http://wiki.mikrotik.com/wiki/Manual:ML ... iple_links Then your whole problem goes away.
http://www.mikrotik.com/testdocs/ros/3. ... ontent.php
Re: force ip cloud to update from WAN1
Posted: Fri Sep 11, 2015 4:33 pm
by marrold
you can easily create an issue where trafic comes in the one interface and leaves the other.
If this happens unintentionally, you've made a mistake I'm your config.