ROUTE wont stick.

RouterOS Beginner Basics
1

I am having a problem thats very weird.
The route I am setting wont stick as in in /ip route the gateway route loses its “interface” thats used to communicate with my satellite modem.
When i come to ping the modem from RouterOS (winbox) it timesout.

I am left then doing resets on the server until its able to find its way through.

[admin@MikroTik] > /ip route print
Flags: X - disabled, A - active, D - dynamic, 
C - connect, S - static, r - rip, b - bgp, o - ospf 
 #     DST-ADDRESS        PREF-SRC        G GATEWAY         DIS INTERFACE     
 0 ADC 10.0.0.0/24        10.0.0.1                              wlan1         
 1 ADC 10.223.167.96/27   10.223.167.111                        eth3-T-INET-IN
 2 ADC 172.16.0.0/16      172.16.0.1                            eth2-B-LAN    
 3 A S 0.0.0.0/0                          r 10.223.167.97       eth3-T-INET-IN
[admin@MikroTik] >

This is a pain because when the route doesnt work right my hotspot dies and i get no inet access.

My routeros version is 2.9.50

2

Is 10.223.167.97 a dynamic address?

3

No.
Its assigned to my Satellite Modem when its active.
Some times the modem has to be reset because of power outages and the server may start before the modem and so on

4

Do you have the MT box connected directly to the modem? Or is there a hub/switch between them? I have a box that does not like to bring up its ethernet port unless there is a “hot” connection on the port. Hubs come up fastest and allow the port to indicate connected to something. I think it has something to do with my O.S. nic “hot connect” setting. After a power failure recovery, the nic would not come up without the hub.

Just a thought…

5

ya i am using a switch.

perhaps i should try without the switch? :slight_smile:

6

If it doesn’t work with it, I don’t think it will make a difference if you remove it.

Is there any other box on that interface you can ping besides the modem? Maybe the modem has decided it no longer likes you. :smiley:

I use the CLI, so I would check
/interface ethernet print
and
/interface bridge print
after a failed reboot and check the port status.

EDIT: I went through about half dozen cablemodems before I got a good one!
Second major cause of port boot problems: “Duplicate IP on network”