MikroTik cheat sheet equivalent on Cisco

Because I’m still newbie on both router devices, I will write simple cheat sheet to simplify my daily usage.

Cisco

$ show ip bgp routes detail 103.8.78.1
  Number of BGP Routes matching display condition : 14
       S:SUPPRESSED F:FILTERED s:STALE
1       Prefix: 103.8.78.0/24,  Status: BE,  Age: 1d3h33m29s
         NEXT_HOP: 202.79.197.212, Metric: 0, Learned from Peer: 202.79.197.122 (24115)
          LOCAL_PREF: 100,  MED: 1,  ORIGIN: igp,  Weight: 0
         AS_PATH: 58389 58551

MikroTik

[dewangga@border] >/ip route print detail where dst-address="103.8.78.0/24"
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=103.8.78.0/24 gateway=218.100.27.xxx 
        gateway-status=218.100.27.xxx reachable via  etherX distance=20 
        scope=40 target-scope=10 bgp-as-path="7717,58551" bgp-weight=20 
        bgp-origin=igp received-from=OIX

Updated: May 13th, 2015
Tested on MikroTik CCR-1036 EM RoS 6.27

Nginx + Apache Reverse Proxy on CentOS 7

On CentOS 6 or EL6 it will be easy because of mod_rpaf and mod_extract_forwarded, why it is needed if you are using reverse proxy? By default, on EL6, the apache version (2.2) is not bundled with mod_remoteip (available and introduced on apache 2.41). The function from mod_rpaf, mod_extract_forwarded and other similiar modules are to make sure real ips came from visitor, not the front end server(s).

If you are not using this modules on your apache backend, your logs always shows only ips front end server(s).

That modules (mod_rpaf and mod_extract_forwarded) no longer available on EL7 distribution (since the apache version is 2.4). Apache 2.4 have bundled modules called mod_remoteip

Continue…