Solaris Jedi: A quick way to check UDP ports on Solaris

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Script to check numerous ports / servers (Solaris native)

Hi I'd like to check that a bunch of firewall rules have been applied and, therefore, want to write a script that basically does the following: telnet serverA port1 telnet serverA port2 telnet serverB port1 telnet serverB port2 I would just compile the list in excel and run it as a...

2. Solaris

Solaris Question - How to find outgoing traffic on UDP ports

Hello All, I am trying find a command that would show me the stats of outgoing traffic on UPD ports on a Solaris 10 box. I would appreciate if anybody could help me out on this. Thank you much!!! Best Regards Sudharma.

3. Solaris

Solaris Ports

Hi can someone Explain me about Solaris Ports orientation, Like which all ports OS uses and which all is left for applications?

4. UNIX for Dummies Questions & Answers

UDP server on Solaris 9

So I am attempting to implement a UDP server on an older Solaris 9 box; the server will be handling packets at a rate of about 12/sec and will be constructing acknowledgment messages on the fly. I've found snippets of sample code here and there on the net... should I be writing this from scratch...

5. Solaris

Ports on Solaris

please provide info. @ how to open ports in solaris? and how to check that which port assigns with which process.

6. Solaris

Quick question about Solaris =)

:D Just curious, I know that solaris 2.0-2.x_present are System V UNIX... But, I have only used Solaris 10, 9 and 2.5... On a 2.5 Sparc box, after you login you get presented with the usual SunOS 5.5.1 then UNIX(R) System V Release 4.0 I know Solaris 9 and 10 do not include this banner... ...

7. IP Networking

Quick Poll: Solaris IP Multipathing

I've setup Solaris IP Multipathing under Solaris whenever the hardware to do so was available. I find it amazing though that so few places I've worked at don't use it until I arrive. I wanted to find out if I'm running into all the exceptions, or is it really not being used? ...

8. 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...

9. 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....

LEARN ABOUT MOJAVE

udp

UDP(4)							   BSD Kernel Interfaces Manual 						    UDP(4)

NAME

     udp -- Internet User Datagram Protocol

SYNOPSIS

     #include <sys/socket.h>
     #include <netinet/in.h>

     int
     socket(AF_INET, SOCK_DGRAM, 0);

DESCRIPTION

     UDP is a simple, unreliable datagram protocol which is used to support the SOCK_DGRAM abstraction for the Internet protocol family.  UDP
     sockets are connectionless, and are normally used with the sendto and recvfrom calls, though the connect(2) or connectx(2) call may also be
     used to fix the destination for future packets (in which case the recv(2) or read(2) and send(2) or write(2) system calls may be used).

     UDP address formats are identical to those used by TCP.  In particular UDP provides a port identifier in addition to the normal Internet
     address format.  Note that the UDP port space is separate from the TCP port space (i.e. a UDP port may not be ``connected'' to a TCP port).
     In addition broadcast packets may be sent (assuming the underlying network supports this) by using a reserved ``broadcast address''; this
     address is network interface dependent.

     Options at the IP transport level may be used with UDP; see ip(4).

DIAGNOSTICS

     A socket operation may fail with one of the following errors returned:

     [EISCONN]	      when trying to establish a connection on a socket which already has one, or when trying to send a datagram with the destina-
		      tion address specified and the socket is already connected;

     [ENOTCONN]       when trying to send a datagram, but no destination address is specified, and the socket hasn't been connected;

     [ENOBUFS]	      when the system runs out of memory for an internal data structure;

     [EADDRINUSE]     when an attempt is made to create a socket with a port which has already been allocated;

     [EADDRNOTAVAIL]  when an attempt is made to create a socket with a network address for which no network interface exists.

SEE ALSO

     connect(2), connectx(2), getsockopt(2), recv(2), send(2), socket(2), inet(4), intro(4), ip(4)

HISTORY

     The udp protocol appeared in 4.2BSD.

4.2 Berkeley Distribution					  March 18, 2015					 4.2 Berkeley Distribution

Solaris BigAdmin RSS