Attachment #2149 for bug #2004




	uint32	request id
	uint32	forwarding type
	string	listen host
	uint32	listen port
	string	connect host
	uint32	connect port

forwarding type may be MUX_FWD_LOCAL, MUX_FWD_REMOTE, MUX_FWD_DYNAMIC.


	uint32	request id
	uint32	forwarding type
	string	listen host
	uint32	listen port
	string	connect host
	uint32	connect port

A server may reply with a MUX_S_OK, a MUX_S_PERMISSION_DENIED or a
MUX_S_FAILURE.
- 

Return to bug 2004

Lines 110-118 A client may request the master to establish a port forward: Link Here

(-)a/PROTOCOL.mux (-5 / +4 lines)
110	uint32 request id	110	uint32 request id
111	uint32 forwarding type	111	uint32 forwarding type
112	string listen host	112	string listen host
113	string listen port	113	uint32 listen port
114	string connect host	114	string connect host
115	string connect port	115	uint32 connect port
116		116
117	forwarding type may be MUX_FWD_LOCAL, MUX_FWD_REMOTE, MUX_FWD_DYNAMIC.	117	forwarding type may be MUX_FWD_LOCAL, MUX_FWD_REMOTE, MUX_FWD_DYNAMIC.
118		118
Lines 135-143 A client may request the master to close a port forward: Link Here
135	uint32 request id	135	uint32 request id
136	uint32 forwarding type	136	uint32 forwarding type
137	string listen host	137	string listen host
138	string listen port	138	uint32 listen port
139	string connect host	139	string connect host
140	string connect port	140	uint32 connect port
141		141
142	A server may reply with a MUX_S_OK, a MUX_S_PERMISSION_DENIED or a	142	A server may reply with a MUX_S_OK, a MUX_S_PERMISSION_DENIED or a
143	MUX_S_FAILURE.	143	MUX_S_FAILURE.
144	-