Skip navigation.
Home
The QNX Community Portal

View topic - Need to know the Open Ports in QNX 6.2.0

Page 1 of 1

Need to know the Open Ports in QNX 6.2.0

PostPosted: Wed Aug 05, 2015 8:16 am
by bhaskara-r
hi

i am using QNX 6.2.0 OS in one Embedded Device.

I want to know the Open Ports in that Device..

But in Linux it has one utility "nmap" which is used to identify the Open ports in linux.

So please Suggest a Similar command for QNX 6.2.0 to know the Open Ports as Similar to "nmap"

Re: Need to know the Open Ports in QNX 6.2.0

PostPosted: Wed Aug 05, 2015 4:55 pm
by Tim
One way to do it is to use nmap on your Linux machine to scan your QNX embedded device and see what open ports it reports.

However by default *no* ports are open on QNX. Ports are only opened based on the services you start (ftp, telnet, qconn etc) in QNX. If you start no services, no ports are open.

What exactly are you starting on your device?

Tim

Re: Need to know the Open Ports in QNX 6.2.0

PostPosted: Thu Aug 06, 2015 4:58 am
by bhaskara-r
Hi Tim,

I am Not starting Any services.

In my QNX 6.2.0 Embedded DEvice i run this command "netstat -a"

it shows the below message

Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
udp 0 0 *.* *.*

what does it mean ??

It implicates any Port Opens on Udp

Re: Need to know the Open Ports in QNX 6.2.0

PostPosted: Thu Aug 06, 2015 2:59 pm
by Tim
I'd say that means nothing is open which is what you'd expect since you are running no services.

Here's what I get on my development system where I am running ftp and telnet daemons plus some other services.

Code: Select all
Active Internet connections (including servers)
Proto Recv-Q Send-Q  Local Address          Foreign Address        State
tcp        0      0  10.144.220.232.netbios 10.144.221.126.57607   ESTABLISHED
tcp        0      0  *.discard              *.*                    LISTEN
tcp        0      0  *.telnet               *.*                    LISTEN
tcp        0      0  *.ftp                  *.*                    LISTEN
tcp        0      0  *.netbios-             *.*                    LISTEN
tcp        0      0  *.8000                 *.*                    LISTEN
udp        0      0  localhost.locald.65534 *.*                   
udp        0      0  *.discard              *.*                   
udp        0      0  10.144.220.232.netbios *.*                   
udp        0      0  10.144.220.232.netbios *.*                   
udp        0      0  *.netbios-             *.*                   
udp        0      0  *.netbios-             *.*                   


The ones marked 'Listen' are listening for incoming connections. 'Established' are currently connected sockets and the ones with no state have simply been reserved by the process but aren't actively connected to any remote machine nor are they listening.

Tim