Sponsored Content
Top Forums UNIX for Dummies Questions & Answers How to check the TCP/UDP port of a connection Post 302073776 by amro1 on Wednesday 17th of May 2006 12:46:06 PM
Old 05-17-2006
Here...

Can you specify the question please as there are standard and ephemeral ports on client and server? Which one you have in mind the port for default incoming/outgoing connection or a port for an actual connection?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

TCP/UDP Ports

Just starting to work with unix, wondering if there is any good on-line documentation explaining TCP/UDP ports, how to use them, etc... Thanks.... (1 Reply)
Discussion started by: eugene_mayo
1 Replies

2. IP Networking

TCP/UDP Ports

Just wondering if anyone knows of any good on-line documentation on TCP/UDP Ports. Basically i want to know how to check if they are in use, learn how to close them, etc... Thanks... (5 Replies)
Discussion started by: eugene_mayo
5 Replies

3. UNIX for Advanced & Expert Users

3600 tcp/udp, trap-daemon, text relay-answer

3600 tcp/udp, trap-daemon, text relay-answer Does anyone know what this service is responsible for, or how significant it is? Thanks.....James (1 Reply)
Discussion started by: cassj
1 Replies

4. UNIX for Dummies Questions & Answers

How can I check UDP connection to other server?

Hi, My network dep. telles me that they have opened the FW but my application still can not get through to other server. If it was TCP I could simply test it myself with "telnet", but how can I check it when the connection is UDP? Tnx (1 Reply)
Discussion started by: mehrdad68
1 Replies

5. UNIX for Advanced & Expert Users

bind 9 forwarders: use UDP or TCP?

I use forwarders for a subzone, but TCP 53 is blocked, So does forwarders really need TCP? If forwaders use UDP, I can't get following scenario to work: main zone is master, but subzone is forwad. Is it possible? (On name sever itself, resolution of xx.stub.abc.com worked fine.) #sub zone... (2 Replies)
Discussion started by: honglus
2 Replies

6. Infrastructure Monitoring

UDP Port 161

hi guys My linux server have SNMP configure port by default is 161 (UDP) now my monitor team - who are using Nagios - say the server are not being monitor so check netstat -lnu and I see all is OK and snmp service is running fine what else should I check about this port 161? to see if it is... (0 Replies)
Discussion started by: karlochacon
0 Replies

7. AIX

TCP/UDP port range for default AIX NFS?

May I know what is the TCP/UCP port range for any default AIX NFS? Based on rpcinfo -p, I got the following output: program vers proto port service 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100000 4 ... (4 Replies)
Discussion started by: famasutika
4 Replies

8. Programming

TCP connection check

Hi. I am writing client - server application using TCP sockets. I need some very basic functionality, namely: how to check if another "participant" of the connection is still present? I want to handle situations, when client is gone, or server breaks down, etc. (25 Replies)
Discussion started by: Shang
25 Replies

9. Shell Programming and Scripting

How to check UDP port example = 31011?

We have open port UDP port 31011, how to verify if port were working or traffic were receive. (2 Replies)
Discussion started by: avtalan
2 Replies

10. IP Networking

Tcp ip port open but no such process (merged: Release A Port)

i want to kill a tcp connection by killing its pid with netstat -an i got the tcp ip connection on port 5914 but when i type ps -a or ps-e there is not such process running on port 5914 is it possible that because i do not log on with proper user account i can not see that process running? (30 Replies)
Discussion started by: alinamadchian
30 Replies
aconnect(1)						      General Commands Manual						       aconnect(1)

NAME
aconnect - ALSA sequencer connection manager SYNOPSIS
aconnect [-d] [-options] sender receiver aconnect -i|-o [-options] aconnect -x DESCRIPTION
aconnect is a utility to connect and disconnect two existing ports on ALSA sequencer system. The ports with the arbitrary subscription permission, such as created by aseqview(1), can be connected to any (MIDI) device ports using aconnect. For example, to connect from port 64:0 to 65:0, run as follows: % aconnect 64:0 65:0 The connection is one-way, and the whole data to the sender port (64:0) is redirected to the receiver port (65:0). When another port (e.g. 65:1) is attached to the same sender port, the data is sent to both receiver ports. For disconnection, use -d option. % aconnect -d 64:0 65:0 The address can be given using the client's name. % aconnect External:0 Emu8000:1 Then the port 0 of the client matching with the string "External" is connected to the port 1 of the client matching with the "Emu8000". Another function of aconnect is to list the present ports on the given condition. The input ports, which may become sender ports, can be listed with -i option. % aconnect -i client 0: 'System' [type=kernel] 0 'Timer ' 1 'Announce ' client 64: 'External MIDI-0' [type=kernel] 0 'MIDI 0-0 ' Similarly, to see the output ports, use -o flag. You can remove all existing exported connections using -x option. This function is useful for terminating the ALSA drivers, because the modules with sequencer connections cannot be unloaded unless their connections are removed. OPTIONS
CONNECTION MANAGEMENT -d, --disconnect Disconnect the given subscription. -e, --exclusive Connect ports with exclusive mode. Both sender and receiver ports can be no longer connected by any other ports. -r, --real queue Convert time-stamps of event packets to the current value of the given real-time queue. This is option is, however, not so useful, since the receiver port must use (not necessarily own) the specified queue. -t, --tick queue Like -r option, but time-stamps are converted to the current value of the given tick queue. LIST PORTS -i, --input List existing input (readable) ports. This option is exclusive to -o. -o, --output List existing output (writable) ports. This option is exclusive to -i. -l, --list List the current connection status. The connected and connecting ports from/to each port are listed together. The suffix flag [ex] means the connection is exclusive. The suffix flag [real:#] and [tick:#] mean the connection includes real-time and tick conversion on the listed queue, respectively. REMOVE ALL CONNECTIONS -x, --removeall Remove all exported connections. SEE ALSO
aseqnet(1), aseqview(1) AUTHOR
Takashi Iwai <tiwai@suse.de> August 31, 2000 aconnect(1)
All times are GMT -4. The time now is 03:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy