Lines Matching +full:mux +full:- +full:int +full:- +full:port

2 ControlMaster connection-sharing.
18 Many multiplexing (mux) client requests yield immediate responses from
19 the mux process; requesting a forwarding, performing an alive check or
28 signaled or the mux server closes the session. This mode is so named as
29 the client waits around while the mux server does all the driving.
36 this mode, the mux client/server connection socket will stop speaking
57 The current version of the mux protocol is 4. A client should refuse
109 non-multiplexed ssh(1) connection. Two additional cases that the
120 3. Requesting passenger-mode stdio forwarding
128 	string	connect port
160 6. Requesting establishment of port forwards
162 A client may request the master to establish a port forward:
168 	uint32	listen port
170 	uint32	connect port
174 If listen port is (unsigned int) -2, then the listen host is treated as
177 If connect port is (unsigned int) -2, then the connect host is treated
183 For dynamically allocated listen port the server replies with
187 	uint32	allocated remote listen port
189 7. Requesting closure of port forwards
191 A client may request the master to close a port forward:
197 	uint32	listen port
199 	uint32	connect port
204 8. Requesting shutdown of mux listener
223 When a mux master receives this message, it will reply with a
235 	byte[packet length - 2] ...
237 The mux master will accept most connection messages and global requests,
287 XXX server->client error/warning notifications
288 XXX send signals via mux
290 XXX extensions for multi-agent
291 XXX extensions for multi-X11
293 XXX signals via mux request
294 XXX list active connections via mux
296 $OpenBSD: PROTOCOL.mux,v 1.14 2024/01/08 05:11:18 djm Exp $