# Missing basic features on routerOS : netstat and nmap/nc

**URL:** <https://forum.mikrotik.com/t/missing-basic-features-on-routeros-netstat-and-nmap-nc/163200>\
**Category:** General\
**Created:** [December 29, 2022, 3:36pm UTC](https://forum.mikrotik.com/t/missing-basic-features-on-routeros-netstat-and-nmap-nc/163200 "2022-12-29T15:36:02Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Amm0](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/amm0/32/1630_2.png) [@Amm0](https://forum.mikrotik.com/u/Amm0)\
**Post date:** [January 2, 2023, 5:29pm UTC](https://forum.mikrotik.com/t/missing-basic-features-on-routeros-netstat-and-nmap-nc/163200/4 "2023-01-02T17:29:26Z")

</div>

It’s just different. And pointing out there is a long list of “missing commands” with slow progress from 2018: [http://forum.mikrotik.com/t/built-in-function-library/117288/1](http://forum.mikrotik.com/t/built-in-function-library/117288/1)

Now if your trying to scan _other_ hosts, you can use a container on ARM-based Mikrotik with “nmap”, “nc” or whatever, that might help some here.

“netstat” is tricker… Certainly no “netstat -l” – since you’re right someone does have to connect to see if it’s open connection… Now I guess “nmap” from a container could find all the open ports on the Mikrotik 😉.

---

_[View the full topic](https://forum.mikrotik.com/t/missing-basic-features-on-routeros-netstat-and-nmap-nc/163200)._
