# Problems to open port 162 (SNMP-TRAP)

**URL:** <https://discourse.nodered.org/t/problems-to-open-port-162-snmp-trap/31555>\
**Category:** General\
**Created:** [14 August 2020 10:09 UTC](https://discourse.nodered.org/t/problems-to-open-port-162-snmp-trap/31555 "2020-08-14T10:09:50Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [14 August 2020 10:32 UTC](https://discourse.nodered.org/t/problems-to-open-port-162-snmp-trap/31555/2 "2020-08-14T10:32:01Z")

</div>

Hi @fernandezjm, welcome to the forum.  
This question is not really node-red specific and has been asked and answered many times (a quick search would reveal that).

So, you are right in that on linux, ports 1 - 1024 are privileged. The best way is to permit regular user/process to bind the port without sudo

Here are a few posts that might help...

> [@Node Red on Port 80](https://discourse.nodered.org/t/node-red-on-port-80/2211/5):
>
> So to follow that link then sudo setcap 'cap\_net\_bind\_service=+ep' $(eval readlink -f `which node`) should do it (for Linux) - sets the node.js executable to be able to do this. To follow up on the running as root... while probably not the end of the world on small single user systems it generally considered a bad thing to run services that are quite as powerful as Node-RED as root as they could be corrupted and wipe disks, install bad apps, etc as they have full admin rights to the machine.…

> <https://serverfault.com/questions/112795/how-to-run-a-server-on-port-80-as-a-normal-user-on-linux>

> <https://stackoverflow.com/questions/413807/is-there-a-way-for-non-root-processes-to-bind-to-privileged-ports-on-linux>

---

_[View the full topic](https://discourse.nodered.org/t/problems-to-open-port-162-snmp-trap/31555)._