Did upgrading to v3.3 from 2.9.50 change the routes?

RouterOS Beginner Basics
1

I’m not sure if this is the right forum, but this seems like such a basic question, I’ll post it here anyway.

On Friday, I upgraded my RB532 from v2.9.50 to v3.3. I have two connections at the moment, one via a VSAT with a static IP address and the other via ADSL with a DHCP address. Before the upgrade, the VSAT connection worked fine. After the upgrade, with the same configuration (as far as I can tell), it doesn’t work. The ADSL connection still works. I’ve tested the VSAT connection with a Windows box and a consumer Linksys router and it works fine on both. I think the problem with my routes.

Here are the IP details I got from the VSAT ISP:
Modem IP: 46.xxx.xxx.69
Router IP: 46.xxx.xxx.70
Subnet: 255.255.255.252

Here’s what I have under IP > Addresses:

Flags: X - disabled, I - invalid, D - dynamic 
 #   ADDRESS            NETWORK         BROADCAST       INTERFACE                   
 0   ;;; added by setup
     192.168.20.1/24    192.168.20.0    192.168.20.255  LAN                         
 1   ;;; VSAT static IP
     46.xxx.xxx.70/30    46.xxx.xxx.69    46.xxx.xxx.71    Internet-VSAT                
 2 D 192.168.1.3/24     192.168.1.0     192.168.1.255   Internet-ADSL

And here’s what I have under IP > Routes:

Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, 
B - blackhole, U - unreachable, P - prohibit 
 #      DST-ADDRESS        PREF-SRC        GATEWAY-STATE GATEWAY                       DISTANCE INTERFACE              
 0   S  ;;; Static route for internal network
       0.0.0.0/0                          reachable     192.168.20.4                  1        LAN                    
 1   S  ;;; Static route for VSAT
       0.0.0.0/0                          reachable     46.xxx.xxx.69                 1        Internet-VSAT          
 2 ADS  0.0.0.0/0                          reachable     192.168.1.1                   0        Internet-ADSL          
 3 ADC  46.xxx.xxx.68/30   46.xxx.xxx.70                                               0        Internet-VSAT          
 4 ADC  192.168.1.0/24     192.168.1.3                                                 0        Internet-ADSL          
 5 ADC  192.168.20.0/24    192.168.20.1                                                0        LAN

So what’s happening? I have no idea… I can ping the VSAT modem from the Mikrotik box, but nothing goes beyond that. Like I said, I’ve set up these configs on a Linksys box and a windows machine, just to make sure the connection was still good.

Any help would be greatly appreciated! Next on my list is some kind of failover setup… but one thing at a time.

Thanks!

Seth

2

This is your default route:

2 ADS 0.0.0.0/0 reachable 192.168.1.1 0 Internet-ADSL

This will be used for any communication with any ip/subnet not listed as a localnet (distance=0), unless you use a routing-mark to select another. I find it odd that this route has a distance=0. It should be distance=1. ??

ADD: And its status shows “ADS”. That is dynamic and static?

3

Even when I disable the ADSL interface completely, it still doesn’t route through.

Also, I think that any DHCP-enabled interfaces are automatically given distances of 0. The default for static addresses is 1.

Seth

Edit: when I disable the DHCP-enabled interface, it obviously removes the two relevant routes (192.168.1.0-related).

4

If you disable that rule, then this rule should become active:

0 S ;;; Static route for internal network
0.0.0.0/0 reachable 192.168.20.4 1 LAN

Does that route go to the internet?

5

Wow. I inherited this job from someone else, and I’ve already spent a bunch of time clearing out bad/useless rules/routes/configs. For some reason, the upgrade must have brought this particular bad rule to light. I didn’t even notice that when I disabled the ADSL connection, it was the 192.168.x.x connection that became active, not the 46.xxx.xxx.69. I figured that 192.168 route was necessary for the internal network to work.

As soon as I disabled the rule you mention above, it worked. Here’s the current config, with the ADSL and bad route disabled.

Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, 
B - blackhole, U - unreachable, P - prohibit 
 #      DST-ADDRESS        PREF-SRC        GATEWAY-STATE GATEWAY                       DISTANCE INTERFACE              
 0 X S  ;;; Static route for internal network
        0.0.0.0/0                                        192.168.20.4                  1       
 1 A S  ;;; Static route for VSAT
        0.0.0.0/0                          reachable     46.xx.xxx.69                  1        Internet-VSAT          
 2 ADC  46.xx.xxx.68/30    46.xx.xxx.70                                                0        Internet-VSAT          
 3 ADC  192.168.20.0/24    192.168.20.1                                                0        LAN
6

Now you should be able to use load balancing or routing marks to use both default routes.

7

Right. I’ll just need to learn how to do that.

Is it a problem that I use two different sets of DNS servers for both connections, or doesn’t it really matter? The ADSL DNS servers are local, so they’re probably about 5 k’s away. The VSAT DNS servers are local to the earthstation of the satellite, but that’s way up in Italy (I’m down in southern Africa).

I’ll leave this to figure out tomorrow.

Thank you!

8

I use the closest DNS servers, but they are the best for me. If the request comes from a source ip that is in the ISP range, they will provide the dns response, despite what route you use for downloading the webpage.

Thanks for karma! :smiley:

9

The two IP ranges are completely different, so I’ll try a script to see if we can change the DNS servers. Thanks again for the help.

10

i have satellite internet or dsl AZTEC605eu modem i want to route my satellite ip into mikrotik router 3.30 for satellite is downlink and dsl for up link

11

Hi Rafi, do you mind making a new thread for this?

Thanks!

12

Also, earlier you showed:

1 ;;; VSAT static IP
46.xxx.xxx.70/30 46.xxx.xxx.69 46.xxx.xxx.71 Internet-VSAT

Normally the network portion of that would be 46.xxx.xxx.68 (and since you’re .70 the remote end’s IP would remain .69).

13

Ah. I thought network = remote end IP, but that makes sense, esp as the internal is 192.168.20.0.

So even though it’s working now, I could safely change it to 46.x.x.68?

Thanks!

14

On point to point links (like PPPoE) you may see the remote end IP show up as the network IP, but this should not normally be the case on broadcast networks, like ethernet (even though there are only two hosts in this case).

You should be able to safely change it, but the interface or anything relying on that interface will possibly bounce. Having it wrong may not be breaking anything in this case, but there might be non-obvious effects.

15

I’ll try it this morning, while everyone is out.

Thanks!

16

sorry friend ihave the problem ip routing on dsl and oneway satellite downlink configration
Adsl upstream & satellite downstream…

17

Just to let everyone know things are working ok now for my setup.

Thanks to everyone for the help!

@rafiullah61, you may want to start your own thread.