Raspberry Pi and UDP?

General
1

Hey! I made a program in Node-Red that sends messages through UDP and recives a respons through a local port. I´ve testet the software on Windows and had no problem, although switching to Raspberry Pi some interference occure.

I guess it has to do with the UDP socket, but i would think Node-Red should take care of that. I´ve also tried changing ports.. Any suggestions?

Windows:
Node-RED version: v0.19.5
Node.js version: v10.13.0
Windows_NT 6.1.7601 x64 LE

Raspberry Pi 3
Node-RED version: v0.19.5
Node.js version v10.14.2
Linux 4.14.79-v7+ arm LE

Log from the Node-Red
Raspberry Pi ---->

21 Jan 14:52:09 - [info]

Welcome to Node-RED

21 Jan 14:52:09 - [info] Node-RED version: v0.19.5
21 Jan 14:52:09 - [info] Node.js version: v10.14.2
21 Jan 14:52:09 - [info] Linux 4.14.79-v7+ arm LE
21 Jan 14:52:10 - [info] Loading palette nodes
21 Jan 14:52:15 - [info] Settings file : /home/pi/.node-red/settings.js
21 Jan 14:52:15 - [info] Context store : 'default' [module=memory]
21 Jan 14:52:15 - [info] User directory : /home/pi/.node-red
21 Jan 14:52:15 - [warn] Projects disabled : editorTheme.projects.enabled=false
21 Jan 14:52:15 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
21 Jan 14:52:15 - [info] Server now running at http://127.0.0.1:1880/
21 Jan 14:52:15 - [warn]

Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.

21 Jan 14:52:15 - [info] Starting flows
21 Jan 14:52:15 - [info] [udp out:658dd9f9.7bf278] udp re-use socket: 45 -> 192.168.83.178:1
21 Jan 14:52:15 - [info] [udp in:98a7fa80.ffee78] udp: port 45 already in use
21 Jan 14:52:15 - [info] Started flows
21 Jan 14:52:15 - [error] [udp in:de89c496.1f41f8] UDP access error, you may need root access for ports below 1024
21 Jan 14:52:15 - [error] [udp in:98a7fa80.ffee78] UDP access error, you may need root access for ports below 1024
21 Jan 14:52:15 - [red] Uncaught Exception:
21 Jan 14:52:15 - Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
at healthCheck (dgram.js:605:11)
at Socket.close (dgram.js:487:3)
at Socket. (/usr/lib/node_modules/node-red/nodes/core/io/32-udp.js:78:20)
at Socket.emit (events.js:187:15)
at state.handle.lookup (dgram.js:243:14)
at process._tickCallback (internal/process/next_tick.js:63:19)

2

The error is exactly what it says:

If you want to use a port number < 1024, you need to run as root.

We generally recommend not to run as root, so if you can, pick a port higher than 1024.

3

I´ve runned numerous ports from all ranges, maybe i didnt clarify that

4

so what is the error message when the port number is more than 1024?

5

Ah reinstalling made the cut!