We've currently got a provider that only does multihop BGP. My setup looks something like the following to get the bgp peer established:
/ip address add address=192.168.100.18/30 interface=ether5 /ip route add check-gateway=ping disabled=no distance=21 dst-address=0.0.0.0/0 gateway=192.168.100.17 scope=30 target-scope=10 /routing bgp peer add address-families=ip as-override=no default-originate=never disabled=no hold-time=3m instance=peer1 multihop=yes name=to_upstream nexthop-choice=default passive=no remote-address=10.0.0.1 remote-as=65531 route-reflect=no tcp-md5-key="" ttl=default update-source=ether5 use-bfd=no In theory, could I change the "/ip route" statement to the line below and get the BGP session up and running? /ip route add disabled=no distance=1 dst-address=10.0.0.1/32 gateway=192.168.100.17 scope=30 target-scope=10 I ask that question because we had our BGP session drop. The static 0.0.0.0/0 route was still "check-gateway" pinging making the router try to send traffic out static 0.0.0.0/0 route causing any failover to not happen. I've changed the remote-as # and ip addressing for example's sake :) -- Micah Miller Network/Server Administrator Network Business Systems, Inc. Phone: 309-944-8823 _______________________________________________ Mikrotik mailing list [email protected] http://mail.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
