WAN problem on RB3011UiAS-RM

Just installed RB3011UiAS-RM to replace old CheckPoint Edge-X appliance and what is my surprise - I cannot set WAN address to static. Well I can, but then I loose any internet connection, I can’t even ping anything outside LAN.
Firstly I thought it was an issue with DNS, but I’m able to ping IPs too. Not from PC inside LAN, not from Mikrotik itself.
As soon as I setup WAN to Auto - everything works.

There are no any other configurations to routing, firewall or nat, except those, that were created by default config.

I’ve tried to setup router from scratch, without default config - no results. Connection to outside the world fails as soon, as I set WAN to static.

V.6.36. Same thing with current 6.37rc.

Any suggestions?

Hi. Can you confirm you have added the route via the ISP as well as the static IP?

/ip route add dst-address=0.0.0.0/0 gateway={isp gateway address}

Yes, it’s there.
Static IP config, when I can’t reach the internet.

 #      DST-ADDRESS        PREF-SRC        GATEWAY            DISTANCE
 0 A S  0.0.0.0/0                          192.168.140.1             1
 1 ADC  147.29.133.0/24    147.29.133.1    bridge                    0
 2 ADC  192.168.140.0/24   192.168.140.151 ether1                    0

Automatic DHCP config from ISP roouter DHCP server, when everything works (I have admin access to ISP router)

 #      DST-ADDRESS        PREF-SRC        GATEWAY            DISTANCE
 0 ADS  0.0.0.0/0                          192.168.140.1             1
 1 ADC  147.29.133.0/24    147.29.133.1    bridge                    0
 2 ADC  192.168.140.0/24   192.168.140.151 ether1                    0

I’ll try to recreate route manually

Is this router behind another router? The gateway address is a private one, not one that you would get from an ISP. If that is correct then are you trying to get out via the same next hop router? If so, you need 192.168.140.1 as the static gateway not 192.168.140.151.

yes, it is. for now, while testing.

EDIT:
and somehow it started to work in test environment

Solved! The problem was on ISP’s router - MAC address refresh was too slow and no tunnel to gateway was created for newly installed equipment.