About

Who I am

I'm Manoranjan Behera, a network and infrastructure engineer. I work with the systems I write about — MikroTik and Cisco on the network side, TIBCO messaging and integration infrastructure on the middleware side, and the Unix hosts underneath both.

I have been doing this for over ten years. The environments I have run include a twenty-site MPLS WAN for a logistics company, middleware and site-to-site VPN infrastructure for a bank, and a campus wireless network with AAA authentication. Day to day that has meant around forty servers, five layer-3 switches, edge routers, and the workstations behind them.

On the TIBCO side I have administered BusinessWorks 5 and 6, BusinessConnect, EMS and Rendezvous, with Hawk for monitoring. That is administration and infrastructure work — installs, upgrades, domain and container configuration, tuning, and being the person on the call when a queue stops draining — rather than integration development.

I hold CCNA and MTCNA. Neither certification is the point — they are just evidence that I sat down and learned the fundamentals properly rather than picking things up from forum posts. What actually shows up in these articles is what the equipment did when I ran the command.

Why this site exists

Vendor documentation describes what a feature does. It rarely tells you what is already switched on. RouterOS ships with services listening that never appear in /export, because an export only records what you changed. So the configuration you review is not the configuration you are running.

That gap is what this publication is about. Every guide starts from a real device in a real state, not a clean lab install that nobody actually operates.

What gets published

Two articles a month, 1,500 to 2,500 words, across four tracks:

• NET — Networking. Hardening, firewall design, and the defaults that ship enabled but never appear in an export.
• EMS — TIBCO. Administration and infrastructure for TIBCO messaging — EMS and Rendezvous, BusinessWorks 5 and 6, BusinessConnect, and Hawk monitoring. Written from running it, not from integrating with it.
• NIX — Unix & Linux. Disks, processes, memory and logs — finding the cause while the incident bridge is still open.

Tracks open as content arrives rather than all at once, so nothing on this site is a section with a heading and nothing under it. Currently published: 2.

What does not get published

No news, no product launches, no roundups of other people's links. That material is worthless a week later, and this site is built to still be useful in three years. No sponsored posts, and no article about a system I have not run myself.

How the writing is done

I use AI tools for drafting and background research, the same way I use a search engine. Nothing is published without human editing, fact-checking, and first-hand observation added — every command in every article has been run, and the output you see is the output I got. The testing methodology is written up in full.

Corrections

If something here is wrong, I want to know. Send it to hello@codesecho.com and I will retest and correct the page, with the update date changed so readers can see it moved.