Sponsored Content
Top Forums UNIX for Dummies Questions & Answers what is the advantage of unix sockets? Post 302525367 by DGPickett on Thursday 26th of May 2011 12:55:41 PM
Old 05-26-2011
TCP and UDP are different facilities under IP, but UNIX sockets are local to the host and simpler, like pipes.

TCP creates a reliable one on one session between a client and server, with full duplex streams of data.

UDP is a user-level packet facility, without 'reliability' but with broadcast and mixed correspondent capability as well as a 'connection' facility, just a fd with a filter and default correspondent. For instance, DNS uses UDP, and a DNS server sits there receiving packets, and for every packet in, makes a packet out. The packet in may be a request for local data, a request for remote data or a response to a past inquiry sent by this server to other DNS servers. The server sends a response to the inquiry, or if tasked with recursion, an inquiry for the inquiry. For responses, the server sends them on to the requestor and caches them locally. The server does all this with one not-connected UDP socket.
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Does automount have an advantage over hard mount?

? (1 Reply)
Discussion started by: 98_1LE
1 Replies

2. HP-UX

fd passing between Independent processes using unix domain sockets

Hi, I am having some error handling issues with and fd passed between Independent processes using unix domain sockets (On HPUX). Here is the scnerio ================= Step 1: TPC/Client (connect()) ---Connects to ------TCP/Server(Gateway) (server gets fd) Step 2: ... (2 Replies)
Discussion started by: Debasisb2002
2 Replies

3. UNIX for Advanced & Expert Users

UNIX Message Queues vs. Sockets

If I use sockets for IPC, and can easily distribute my applications. UNIX Message Queues are local to the processor. As I understand it, Message Queues still incur system call overhead, just like socket calls. What advantage does a UNIX Message Queue provide versus a TCP or UDP Socket,... (2 Replies)
Discussion started by: zen29sky
2 Replies

4. UNIX for Advanced & Expert Users

UNIX domain sockets vs FIFOs

Is there a performance advantage of one of these over the other? Obviously, it makes no sense to use normal TCP sockets or UDP sockets w/ the overhead they carry. But what about UNIX domain sockets vs FIFOs? I'd think they'd be very similar, in terms of performance and in terms of how they're... (2 Replies)
Discussion started by: mgessner
2 Replies

5. Shell Programming and Scripting

bash: one advantage of the ability to look for either synonym?

Hi I'm reading <learning the bash shell>. And in the section - 3.1. The .bash_profile, .bash_logout, and .bashrc Files bash allows two synonyms for .bash_profile: .bash_login, derived from the C shell's file named .login, and .profile, derived from the Bourne shell and Korn shell files... (1 Reply)
Discussion started by: password636
1 Replies

6. Solaris

advantage of v490 over 480R

What are the advantages for Sun Fire 490 over Sun Fire 480 R just from a server performance perspective? Or, are they both just about the same? (1 Reply)
Discussion started by: jtamminen
1 Replies

7. Red Hat

Cobbler - what is the advantage?

Hi guys, new user here, so please be gentle. I need to build a lot of servers at work on a weekly basis with various versions of RH and additional applications. We use PXE/Kickstart to do this with selections made from a simple menu structure. However, I keep hearing about Cobbler and... (0 Replies)
Discussion started by: hankpym
0 Replies
RADCLIENT(1)							 FreeRADIUS Daemon						      RADCLIENT(1)

NAME
radclient - send packets to a RADIUS server, show reply SYNOPSIS
radclient [-4] [-6] [-d raddb_directory] [-c count] [-f file] [-F] [-h] [-i id] [-n num_requests_per_second] [-p num_requests_in_parallel] [-q] [-r num_retries] [-s] [-S shared_secret_file] [-t timeout] [-v] [-x] server {acct|auth|status|disconnect|auto} secret DESCRIPTION
radclient is a radius client program. It can send arbitrary radius packets to a radius server, then shows the reply. It can be used to test changes you made in the configuration of the radius server, or it can be used to monitor if a radius server is up. radclient reads radius attribute/value pairs from it standard input, or from a file specified on the command line. It then encodes these attribute/value pairs using the dictionary, and sends them to the remote server. The User-Password and CHAP-Password attributes are automatically encrypted before the packet is sent to the server. OPTIONS
-4 Use IPv4 (default) -6 Use IPv6 -c count Send each packet count times. -d raddb_directory The directory that contains the RADIUS dictionary files. Defaults to /etc/raddb. -f file File to read the attribute/value pairs from. If this is not specified, they are read from stdin. This option can be specified mul- tiple times, in which case packets are sent in order by file, and within each file, by first packet to last packet. A blank line separates logical packets within a file. -F Print the file name, packet number and reply code. -h Print usage help information. -i id Use id as the RADIUS request Id. -n num_requests_per_second Try to send num_requests_per_second, evenly spaced. This option allows you to slow down the rate at which radclient sends requests. When not using -n, the default is to send packets as quickly as possible, with no inter-packet delays. Due to limitations in radclient, this option does not accurately send the requested number of packets per second. -p num_requests_in_parallel Send num_requests_in_parallel, without waiting for a response for each one. By default, radclient sends the first request it has read, waits for the response, and once the response is received, sends the second request in its list. This option allows you to send many requests at simultaneously. Once num_requests_in_parallel are sent, radclient waits for all of the responses to arrive (or for the requests to time out), before sending any more packets. This option permits you to discover the maximum load accepted by a RADIUS server. -q Go to quiet mode, and do not print out anything. -r num_retries Try to send each packet num_retries times, before giving up on it. The default is 10. -s Print out some summaries of packets sent and received. -S shared_secret_file Rather than reading the shared secret from the command-line (where it can be seen by others on the local system), read it instead from shared_secret_file. -t timeout Wait timeout seconds before deciding that the NAS has not responded to a request, and re-sending the packet. The default timeout is 3. -v Print out version information. -x Print out debugging information. server[:port] The hostname or IP address of the remote server. Optionally a UDP port can be specified. If no UDP port is specified, it is looked up in /etc/services. The service name looked for is radacct for accounting packets, and radius for all other requests. If a service is not found in /etc/services, 1813 and 1812 are used respectively. The RADIUS attributes read by radclient can contain the special attribute Packet-Dst-IP-Address. If this attribute exists, then that IP address is where the packet is sent, and the server specified on the command-line is ignored. If the RADIUS attribute list always contains the Packet-Dst-IP-Address attribute, then the server parameter can be given as -. The RADIUS attributes read by radclient can contain the special attribute Packet-Dst-Port. If this attribute exists, then that UDP port is where the packet is sent, and the :port specified on the command-line is ignored. acct | auth | status | disconnect | auto Use auth to send an authentication packet (Access-Request), acct to send an accounting packet (Accounting-Request), status to send an status packet (Status-Server), or disconnect to send a disconnection request. Instead of these values, you can also use a decimal code here. For example, code 12 is also Status-Server. The RADIUS attributes read by radclient can contain the special attribute Packet-Type. If this attribute exists, then that type of packet is sent, and the type specified on the command-line is ignored. If the RADIUS attribute list always contains the Packet-Type attribute, then the type parameter can be given as auto. secret The shared secret for this client. It needs to be defined on the radius server side too, for the IP address you are sending the radius packets from. EXAMPLE
A sample session that queries the remote server for Status-Server (not all servers support this, but FreeRADIUS has configurable support for it). $ echo "Message-Authenticator = 0x00" | radclient 192.0.2.42 status s3cr3t Sending request to server 192.0.2.42, port 1812. radrecv: Packet from host 192.0.2.42 code=2, id=140, length=54 Reply-Message = "FreeRADIUS up 21 days, 02:05" SEE ALSO
radiusd(8), AUTHORS
Miquel van Smoorenburg, miquels@cistron.nl. Alan DeKok <aland@freeradius.org> 2 April 2009 RADCLIENT(1)
All times are GMT -4. The time now is 11:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy