(Solved) RB450G will not route

RouterOS General
1

Solved now, routes were needed in the Gateway to reach the edge but a reboot was also required before they would function

I have a problem here which is driving me nuts. I have two RB450Gs sitting on my table, testing before deployment.
They are both running ROS 5.20/Routerboard 2.41

The first will act as a simple gateway (eth 2= 172.16.1.1/28)
The second will be an edge router, (eth1=172.16.1.14/28)
The two routers refuse to communicate with eachother, the gateway cannot ping the edge, nor the other way around.
The only time the edge router will communicate with the gateway is if I add a NAT Masquerade rule in the edge router, which should not be necessary. I have other routers routing without problem without NAT.
However the routers themselves are able to ping eachother when using the built in ping utility.
Can anyone help me out here?
Below are the details of the edge router:

/ip address print detail
Flags: X - disabled, I - invalid, D - dynamic 
 0   address=10.1.1.1/26 network=10.1.1.0 interface=bridge_LAN 
     actual-interface=bridge_LAN 

 1   address=172.16.1.14/28 network=172.16.1.0 
     interface=ether1-Rocket M5_backhaul actual-interface=bridge_LAN 

 2   address=172.16.1.17/28 network=172.16.1.16 interface=bridge_LAN 
     actual-interface=bridge_LAN




/ip route print detail
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 
 0 A S  dst-address=0.0.0.0/0 gateway=172.16.1.1 
        gateway-status=172.16.1.1 reachable via  bridge_LAN distance=1 scope=30 
        target-scope=10 

 1 ADC  dst-address=10.1.1.0/26 pref-src=10.1.1.1 gateway=bridge_LAN 
        gateway-status=bridge_LAN reachable distance=0 scope=10 

 2 ADC  dst-address=172.16.1.0/28 pref-src=172.16.1.14 gateway=bridge_LAN 
        gateway-status=bridge_LAN reachable distance=0 scope=10 

 3 ADC  dst-address=172.16.1.16/28 pref-src=172.16.1.17 gateway=bridge_LAN 
        gateway-status=bridge_LAN reachable distance=0 scope=10




/interface print detail
Flags: D - dynamic, X - disabled, R - running, S - slave 
 0  R  name="ether1-Rocket M5_backhaul" type="ether" mtu=1500 l2mtu=1520 
       max-l2mtu=1520 

 1     name="ether2-5ghz sector120-S" type="ether" mtu=1500 l2mtu=1520 
       max-l2mtu=1520 

 2  R  name="ether3-5ghz sector 90-NE" type="ether" mtu=1500 l2mtu=1520 
       max-l2mtu=1520 

 3     name="ether4-NanoBridge test" type="ether" mtu=1500 l2mtu=1520 
       max-l2mtu=1520 

 4  X  name="ether5" type="ether" mtu=1500 l2mtu=1520 max-l2mtu=1520 

 5  R  name="bridge_LAN" type="bridge" mtu=1500 l2mtu=1520




/ip firewall export
# jan/02/1970 00:36:28 by RouterOS 5.20
# software id = 6WN8-SFN0
#
/ip firewall connection tracking
set enabled=yes generic-timeout=10m icmp-timeout=10s tcp-close-timeout=10s \
    tcp-close-wait-timeout=10s tcp-established-timeout=1d tcp-fin-wait-timeout=\
    10s tcp-last-ack-timeout=10s tcp-syn-received-timeout=5s \
    tcp-syn-sent-timeout=5s tcp-syncookie=no tcp-time-wait-timeout=10s \
    udp-stream-timeout=3m udp-timeout=10s
/ip firewall service-port
set ftp disabled=no ports=21
set tftp disabled=no ports=69
set irc disabled=no ports=6667
set h323 disabled=no
set sip disabled=yes ports=5060,5061 sip-direct-media=yes
set pptp disabled=no
2



However the routers themselves are able to ping each other when using the built in ping utility

??? which is it now, can they ping each other or not?

draw a simple map to specify what is “pingable” and what isn’t..

Regards

3

Sorry, I should have clarified that. The RB450G won’t seem to route 172.16.1.0 to anything connected to it (I can’t ping that network from my computers),
but the router itself is able to ping that network using the built in ping utility.
The Bridge is not the problem either, I reset the routers completely and setup the same thing without bridges and it still will not route to 172.16.1.0
Apparently Winbox is able to discover both routers though.

Also, It seems that when I plug my computer into the gateway router it can ping the edge now, but I can’t ping the gateway when connected to the edge.

Solved now, routes were needed in the Gateway to reach the edge but a reboot was also required before they would function
winbox discovery.jpg
diagram.jpg