The route for 1.1.1.1/32 is Xs, like if it was manually disabled? When you actually disconnect the cable It should not becomes X, only s. I double-checked, status becomes Xs with WAN1 cable disconnected: Flags: D - DYNAMIC; X - DISABLED, I - INACTIVE, A - ACTIVE; c - CONNECT, s - STATIC; H - HW-OFF...
OK, part of my confusion is that I was looking at /routing/route instead of /ip/route . But the /routing/route active and unreachable properties aren't set: [admin@Palace] /ip/route> :put [/routing/route/get [find comment="WAN2_default"] disabled ] true [admin@Palace] /ip/route> :put [/rou...
I'm running RouterOS 7.17.2 and have dual WAN with recursive routing failover and DHCP set up: [admin@Palace] > /ip/route/print detail Flags: D - dynamic; X - disabled, I - inactive, A - active; c - connect, s - static, r - rip, b - bgp, o - ospf, i - is-is, d - dhcp, v - vpn, m - modem, y - bgp-mpl...
My configuration after upgrading to routeros 7.17.2 has these commands: /ip dhcp-server network add address=10.1.10.0/32 comment=defconf dns-server=10.1.10.1 gateway=\ 10.1.10.1 netmask=24 add address=10.1.10.0/24 comment=defconf dns-server=10.1.10.1 gateway=\ 10.1.10.1 netmask=24 Is this correct?
Im a bit confused by the approach. Why are you putting script on LAN subnets DHCP when the proper place to address routing is the WANs?? Is it that you want users to always use the primary and if that is not available then use the backup WAN?? ... Yes. I followed these videos on recursive routing: ...
Right, I had things backward, and only one route is needed: # DST-ADDRESS GATEWAY DISTANCE ;;; LM1200 4 As 192.168.5.0/24 26.236.232.1 1 This allows the LM1200 management console to be accessed at its default IP, 192.168.5.1. This script on the WAN2 DHCP client updates the gateway addresses: # dhcp2...
I'm setting up an hAP ax2 with dual WAN failover. A Netgear LM1200 modem is on ether2, configured with a DHCP client. The DHCP client script updates the gateway for a route: :if ($bound=1) do={ /ip route set [find where comment="dhcp2"] gateway=$"gateway-address" disabled=no /ip ...
Resetting the router to the default configuration and then setting up only enough for port forwarding worked. Sort of. I think what's happening is that when I access the router from another Monkeybrains connection in the building, the router doesn't receive the packets via the WAN, so port forwardin...
I made the recommended changes, but port forwarding still fails. Updated configuration attached. I noticed these messages in the log: radvd warning invalid mtu 9100 on ether1 from fe80::c6b3:6aff:fe43:6b7a firewall info blueiris dstnat: in:ether1 out:(unknown 0), connection-state:new src-mac c4:b3:6...
Probably the ISPs are to blame if the WAN IPs aren't public or their devices aren't in bridge mode The ISP is Monkeybrains. They replied to the ticket I opened that port forwarding should work if properly configured. Also, I just realized that I have an Asus router on Monkeybrains elsewhere in the ...
Moving the firewall rules up didn't help: [admin@MikroTik] > /ip firewall filter print Flags: X - disabled, I - invalid; D - dynamic 0 D ;;; special dummy rule to show fasttrack counters chain=forward action=passthrough 1 ;;; defconf: accept established,related,untracked chain=input action=accept co...
I'm replacing a Comcast Business router with an hAP ax2. I have dual WAN failover from ether1 to ether2 with DHCP working, and need to forward TCP/UDP port 81 to cascaded router IP 10.1.10.151. Here's what I have configured that is not working: 2 [admin@MikroTik] > /ip firewall nat print Flags: X - ...
While debugging a problem with /tool/fetch I entered the command /system logging add topics=fetch . Now lots of unwanted messages are logged (attached). How can I reset logging to default settings? I tried: /system logging disable [find topics=fetch] /system logging reset 4 /system logging disable [...