The first thing it will look for is route cost/weight.
Then the IP addresses. I am not sure what rules it uses for your issue,
but for most things MT likes to start with the highest valued item.
On 7/1/2013 3:02 PM, Rory McCann wrote:
On this particular router, my upstream assigned two IPs from different
subnets, so I technically have two default routes. One is just
disabled since the default gateways in question are assigned to the
same device. (I can communicate over each IP fine and everything was
working fine in 5.x).
When referencing the terminal, I was under the understanding (per
Butch's explanation) that when you issue /ip address print, the first
publicly routable IP listed is the IP that the router will use for
communication. In my case, the IP I WANT the router to use comes
before the IP that it actually uses in the terminal listed of the IP
addresses, however upon reboot it uses the other IP.
Rory McCann
Minn-Kota Ag Products
P: 701-403-4877 | E: [email protected]
On 7/1/2013 1:46 PM, Grand Avenue Broadband wrote:
Can you not utilize "pref-src" in the routing table to ensure the
behavior you desire?
I may not be understanding your question -- particularly, your
mention of "the terminal" increases my doubt.
On Jul 1, 2013, at 11:17 AM, Rory McCann <[email protected]> wrote:
Has something changed recently in routerOS v6.x that involves how
the router chooses its IP address for outbound (router to internet
or router to router) connectivity?
In the past, the router would always choose the first public IP
address listed in the terminal for its outbound communications. In
v6.1 (which I installed to utilize untagged VLAN support) I've
noticed that it appears to be choosing the lowest integer IP rather
than the first assigned.
Eg: I have a router with 10.10.10.1 and 10.10.10.10 assigned to it.
10.10.10.10 was the first one programmed and my "preferred" router
communication IP for IPSec, EoIP, etc.
Upon reboot, the router starts talking on 10.10.10.1 instead of
10.10.10.10. I have to remove and re-add the IP in order to change
this behavior. Upon reboot it again chooses 10.10.10.1.
Are there some new firewall/NAT rules that affect this behavior or a
setting somewhere or is this some kind of obscure bug?
--
Rory McCann
Minn-Kota Ag Products
P: 701-403-4877 | E: [email protected]
_______________________________________________
Mikrotik mailing list
[email protected]
http://mail.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
_______________________________________________
Mikrotik mailing list
[email protected]
http://mail.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
_______________________________________________
Mikrotik mailing list
[email protected]
http://mail.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3345 / Virus Database: 3204/6453 - Release Date: 07/01/13
--
Scott Reed
Owner
NewWays Networking, LLC
Wireless Networking
Network Design, Installation and Administration
Mikrotik Advanced Certified
www.nwwnet.net
(765) 855-1060
(765) 439-4253
(855) 231-6239
_______________________________________________
Mikrotik mailing list
[email protected]
http://mail.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
