WAN subnet with gateway outside subnet

We have a subnet from our provider stated 66.159.4.104/29 (addresses 66.159.4.104-110)
The default gateway is 66.159.5.254 ??
If I enter this in a SonicWall it works.

But when I want to program this ISP in a mikrotik it failes.
I add address 66.159.4.110/29 to ether1.
An add the route to 0.0.0.0/0 to 66.159.5.254, the MKT responds this is not reachable?

Can anybody help me with this.

PS. an ARP ping to 66.159.5.254 on ether1 replies and also resolves in a mac address and. A normal icmp ping does not reply.

Add a route specifically to 66.159.5.254 via ether1.

@docmarius

I tried this. But no result?
First add route 66.159.5.254/32 → ether1
Then add route 0.0.0.0/0 → 66.159.5.254 (not reachable)

Also no result :frowning:

Thank you for your suggestion.

Hmmmm, the gateway should be reachable…
Instead of that route, you could also extend the mask on eth1 to include the gateway, something like 66.159.4.104/23.
This won’t affect your ability to use the assigned addresses, unless you need to access other subnets in the same /23 range.
Or at least get connectivity up.

It works with point-to-point addresses:
/ip address
add address=66.159.4.110/32 interface=ether3 network=66.159.5.254
/ip route
add distance=1 gateway=66.159.5.254where it creates dynamic entry for gw:

#      DST-ADDRESS        PREF-SRC        GATEWAY            DISTANCE
 0 A S  0.0.0.0/0                          66.159.5.254              1
 1 ADC  66.159.5.254/32    66.159.4.110    ether3                    0

But with regular subnet and the same route for gw added manually:
/ip address
add address=66.159.4.110/29 interface=ether3 network=66.159.4.104
/ip route
add distance=1 gateway=66.159.5.254
add distance=1 dst-address=66.159.5.254/32 gateway=ether3 pref-src=66.159.4.110no luck:

#      DST-ADDRESS        PREF-SRC        GATEWAY            DISTANCE
 0   S  0.0.0.0/0                          66.159.5.254              1
 1 ADC  66.159.4.104/29    66.159.4.110    ether3                    0
 2 A S  66.159.5.254/32    66.159.4.110    ether3                    1

It looks like distance value might be the problem (it’s the only difference), but ROS won’t let you set it to 0.

It seems to work, when you combine both, i.e.:
/ip address
add address=66.159.4.110/29 interface=ether3 network=66.159.4.104
add address=66.159.4.110/32 interface=ether3 network=66.159.5.254
/ip route
add distance=1 gateway=66.159.5.254

#      DST-ADDRESS        PREF-SRC        GATEWAY
 0 A S  0.0.0.0/0                          66.159.5.254
 2 ADC  66.159.4.104/29    66.159.4.110    ether3
 3 ADC  66.159.5.254/32    66.159.4.110    ether3

@sob

Thank you, I am going to try this.