04-01-2014
(The grep is a bit loose.) Maybe it is a proxy, router or firewall. A proxy hides and handles many users' browser connections. A common home/wifi router uses one IP for all the 192.168.*.* hosts behind it. A firewall can support several kinds of proxy-like features. OF course, a browser not using http/1.0 persistent can have many connections, but they are transient.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
In my organization in order for anyone to go to any Unix server they have to go through "SERVER A" and login as themselves.
Then people are free to go enywhere they please.
For example:
SERVER A, loggs in as himself
telnets to SERVER B, loggs in as guest
telnets to SERVER C, loggs in as... (8 Replies)
Discussion started by: jraitsev
8 Replies
2. UNIX for Dummies Questions & Answers
Can someone please explain the difference between a connection and a thread. Any explanation will help!
Thanks (3 Replies)
Discussion started by: suntan
3 Replies
3. UNIX for Dummies Questions & Answers
Hello there, just a quick question.....Can someone please explain the concept that enables you to establish a connection using the same userId
Thanx (1 Reply)
Discussion started by: BigTool4u2
1 Replies
4. UNIX for Dummies Questions & Answers
Say, for instance, that you are running a website. You are playing around, using netstat, etc. You notice all the people whom are connected to the site. You then wonder if there is a way to kill one or more of these connections. However, they are not PIDs so could you use the kill command? I was... (1 Reply)
Discussion started by: Phobos
1 Replies
5. HP-UX
Hello All,
I have 2 qries about X connections on HP-UX :
1.How/where to determine whether "X connections" to the server are controlled.
2. How/where to determine whether "X11 connection" are tunnelled via ssh.
3. How/where to determine the "Time in minutes before unattended X terminals... (0 Replies)
Discussion started by: abhayh
0 Replies
6. SCO
Hi There
Is there a maximum number of concurrent incoming uucp connections to a server?
SCO Openserver 5.07
Is there a parameter in some config file where this can be changed?
Thanx (5 Replies)
Discussion started by: wjace
5 Replies
7. Red Hat
Hi,
I am running JBOSS 6 ona RHEL5 server put it continuously crashes due to the number of CLOSE_WAIT connections on port 8080.
How can I kill the several hundred CLOSE_WAIT connections without killing the actual live "LISTENING" connection?
R,
D. (2 Replies)
Discussion started by: Duffs22
2 Replies
8. AIX
I am using AIX 5.3, its a application server, i am giving the support of OS & Hardware only, now i want to check how many connections are connected to my server, means how many people using my server.:confused: (4 Replies)
Discussion started by: reply.ravi
4 Replies
9. Solaris
Hi All!
Please help me with this situation:
I have 3 servers configured with the following network 10.100.48.xx and I have configured on the passwordless connection, and it is working fine.
Now the app vendor ask me to configure a 2nd IP address on each of the 3 servers with a different IP... (4 Replies)
Discussion started by: fretagi
4 Replies
10. UNIX for Advanced & Expert Users
I have a static IP 47.21.154.146 and two computers which I wish to talk to each other. The two IPs are 198.168.1.5 and 198.168.1.6.
How do I do it. For example ls from one computer to the other.
TIA (8 Replies)
Discussion started by: Meow613
8 Replies
LEARN ABOUT OPENSOLARIS
systemd-socket-proxyd
SYSTEMD-SOCKET-PROXYD(8) systemd-socket-proxyd SYSTEMD-SOCKET-PROXYD(8)
NAME
systemd-socket-proxyd - Bidirectionally proxy local sockets to another (possibly remote) socket.
SYNOPSIS
systemd-socket-proxyd [OPTIONS...] HOST:PORT
systemd-socket-proxyd [OPTIONS...] UNIX-DOMAIN-SOCKET-PATH
DESCRIPTION
systemd-socket-proxyd is a generic socket-activated network socket forwarder proxy daemon for IPv4, IPv6 and UNIX stream sockets. It may be
used to bi-directionally forward traffic from a local listening socket to a local or remote destination socket.
One use of this tool is to provide socket activation support for services that do not natively support socket activation. On behalf of the
service to activate, the proxy inherits the socket from systemd, accepts each client connection, opens a connection to a configured server
for each client, and then bidirectionally forwards data between the two.
This utility's behavior is similar to socat(1). The main differences for systemd-socket-proxyd are support for socket activation with
"Accept=false" and an event-driven design that scales better with the number of connections.
OPTIONS
The following options are understood:
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
--connections-max=, -c
Sets the maximum number of simultaneous connections, defaults to 256. If the limit of concurrent connections is reached further
connections will be refused.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
EXAMPLES
Simple Example
Use two services with a dependency and no namespace isolation.
Example 1. proxy-to-nginx.socket
[Socket]
ListenStream=80
[Install]
WantedBy=sockets.target
Example 2. proxy-to-nginx.service
[Unit]
Requires=nginx.service
After=nginx.service
Requires=proxy-to-nginx.socket
After=proxy-to-nginx.socket
[Service]
ExecStart=/lib/systemd/systemd-socket-proxyd /tmp/nginx.sock
PrivateTmp=yes
PrivateNetwork=yes
Example 3. nginx.conf
[...]
server {
listen unix:/tmp/nginx.sock;
[...]
Example 4. Enabling the proxy
# systemctl enable --now proxy-to-nginx.socket
$ curl http://localhost:80/
Namespace Example
Similar as above, but runs the socket proxy and the main service in the same private namespace, assuming that nginx.service has PrivateTmp=
and PrivateNetwork= set, too.
Example 5. proxy-to-nginx.socket
[Socket]
ListenStream=80
[Install]
WantedBy=sockets.target
Example 6. proxy-to-nginx.service
[Unit]
Requires=nginx.service
After=nginx.service
Requires=proxy-to-nginx.socket
After=proxy-to-nginx.socket
JoinsNamespaceOf=nginx.service
[Service]
ExecStart=/lib/systemd/systemd-socket-proxyd 127.0.0.1:8080
PrivateTmp=yes
PrivateNetwork=yes
Example 7. nginx.conf
[...]
server {
listen 8080;
[...]
Example 8. Enabling the proxy
# systemctl enable --now proxy-to-nginx.socket
$ curl http://localhost:80/
SEE ALSO
systemd(1), systemd.socket(5), systemd.service(5), systemctl(1), socat(1), nginx(1), curl(1)
systemd 237 SYSTEMD-SOCKET-PROXYD(8)