Sunday, March 12, 2017

Lab.4 How To Configure External BGP Peering Mikrotik (Loopback Interface)

Just like before we're going to configure External BGP Peering with Loopback interface,The difference is just to make 2 loopback on every router.and this Lab is to learn configuration proccess of eBGP Peering in 2 different AS  to use 2 loopback Address

We're just need this topology Again : 
Below are the configuration for MikroR-1 :
[admin@MikroTik] >  system identity set name=R-1
[admin@R-1] > ip address add address=10.10.10.1/24 interface=ether1
[admin@R-1] > ip address add address=192.168.1.1/24 interface=ether2
[admin@R-1] > interface bridge add name=Loopback1
[admin@R-1] > interface bridge add name=Loopback2
[admin@R-1] > ip address add address=1.1.1.1/32 interface=Loopback1
[admin@R-1] > ip address add address=11.11.11.11/32 interface=Loopback2
[admin@R-1] > ip route add dst-address=2.2.2.2/32 gateway=10.10.10.2
[admin@R-1] > routing bgp peer add name=peer1 remote-address=2.2.2.2 remote-as=200 multihop=yes update-source=Loopback1
[admin@R-1] > routing bgp instance set default as=100 router-id=1.1.1.1
[admin@R-1] > routing bgp network add network=11.11.11.11/32
And Below are for R-2 Configuration: 
[admin@MikroTik] > system identity set name=R-2
[admin@R-2] > ip address add address=10.10.10.2/24 interface=ether1
[admin@R-2] > ip address add address=192.168.2.1/24 interface=ether2
[admin@R-2] > interface bridge add name=Loopback1
[admin@R-2] > interface bridge add name=Loopback2
[admin@R-2] > ip address add address=2.2.2.2/32 interface=Loopback1
[admin@R-2] > ip address add address=22.22.22.22/32 interface=Loopback2
[admin@R-2] > routing bgp instance set default as=200 router-id=2.2.2.2
[admin@R-2] > routing bgp peer add name=peer1 remote-address=10.10.10.1 remote-as=100 update-source=Loopback1
multihop=yes
[admin@R-2] > routing bgp network add network=22.22.22.22/32
 
after we finish configuring eBGP we can verified with this command and i use it on R-2 :
[admin@R-2] > routing bgp peer print status
Flags: X - disabled, E - established
 0 E name="peer1" instance=default remote-address=10.10.10.1 remote-as=100 tcp-md5-key=""
     nexthop-choice=default multihop=yes route-reflect=no hold-time=3m ttl=255 in-filter="" out-filter=""
     address-families=ip update-source=Loopback1 default-originate=never remove-private-as=no
     as-override=no passive=no use-bfd=no remote-id=1.1.1.1 local-address=2.2.2.2 uptime=15s prefix-count=1
     updates-sent=1 updates-received=1 withdrawn-sent=0 withdrawn-received=0 remote-hold-time=3m
     used-hold-time=3m used-keepalive-time=1m refresh-capability=yes as4-capability=yes state=established

[admin@R-2] > ip route print detail where dst-address=11.11.11.11/32
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 ADb  dst-address=11.11.11.11/32 gateway=10.10.10.1 gateway-status=10.10.10.1 reachable via  ether1
        distance=20 scope=40 target-scope=30 bgp-as-path="100" bgp-origin=igp received-from=peer1

[admin@R-2] > ip route print
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
 #      DST-ADDRESS        PREF-SRC        GATEWAY            DISTANCE
 0 ADC  2.2.2.2/32         2.2.2.2         Loopback1                 0
 1 ADC  10.10.10.0/24      10.10.10.2      ether1                    0
 2 ADb  11.11.11.11/32                     10.10.10.1               20
 3 ADC  22.22.22.22/32     22.22.22.22     Loopback2                 0
 4 ADC  192.168.2.0/24     192.168.2.1     ether2                    0


EmoticonEmoticon