| 1 |
Q: I'm not real sure what httptunnel can be used for exactly? |
| 2 |
|
| 3 |
A: It's a generic tool for sending data in and out through an HTTP proxy. |
| 4 |
This is not very useful in itself, so you must run another program |
| 5 |
which uses this data "tunnel". For example, you could use telnet |
| •6 |
to log in on a computer outside the proxy. |
| 7 |
|
| •8 |
Q: How do I get this going through a proxy? |
| 9 |
|
| 10 |
A: On the server you must run hts. If I wanted to have port |
| 11 |
80 (http) redirect all traffic to port 23 (telnet) then |
| 12 |
it would go something like: |
| 13 |
|
| 14 |
hts -F server.test.com:23 80 |
| 15 |
|
| 16 |
On the client you would run htc. If you are going through |
| 17 |
a proxy, the -P option is needed,otherwise omit it. |
| 18 |
|
| 19 |
htc -P proxy.corp.com:80 -F 22 server.test.com:80 |
| 20 |
|
| 21 |
Then telnet localhost and it will redirect the traffic out |
| 22 |
to port 80 on the proxy server and on to port 80 of the |
| 23 |
server, then to port 23. |
| 24 |
|
| •25 |
Q: httptunnel crashes my SuSE 5.3 box, why? |
| 26 |
|
| 27 |
A: I don't know, but upgrading to 6.0 seems to help. |
| 28 |
|
| 29 |
Q: I'm responsible for network security in our company. My question |
| 30 |
is: are there any characteristics of the communication that may be |
| 31 |
detected at the proxy? |
| 32 |
|
| 33 |
A: Maybe. I make no guarantees. Use the source. |
| 34 |
|
| 35 |
Q: I wrote 'hts -d /dev/ptyq1' but 'cat </dev/ptyq1' returns an error. |
| 36 |
|
| 37 |
A: Use 'cat </dev/ttyq1' instead. |
| 38 |
|
| 39 |
Q: My friend runs hts at port 8888, but when I try to connect to it, |
| 40 |
there is no response. |
| 41 |
|
| 42 |
A: As for now, hts can't handle multiple tunnels. You must run your |
| 43 |
own instance of hts listening to another port. |
| 44 |
|
| 45 |
Q: Is there a Windows/95/98/NT version? |
| 46 |
|
| 47 |
A: It's possible to build and run httptunnel in the Cygwin environment. |
| 48 |
See http://sourceware.cygnus.com/cygwin/. |
| 49 |
|
| 50 |
Q: Are there binaries of httptunnel for win32(Windows/95/98/NT) anywhere? |
| 51 |
|
| 52 |
A: On the homepage, there is a link to someone maintaining |
| 53 |
win32 binaries. |
| 54 |
|
| •55 |
Q: Is there a Macintosh version? |
| 56 |
|
| 57 |
A: Not that I know of. |
| 58 |
|
| 59 |
Q: My firewall requires HTTP user authentication (which is currently |
| 60 |
not supported by httptunnel). Do you plan to add something like |
| 61 |
that? |
| 62 |
|
| 63 |
A: Yes. |
| 64 |
|
| 65 |
Q: How hard would it be to implement "hts" as a cgi running on a |
| 66 |
normal web server? |
| 67 |
|
| 68 |
A: hts can't be called directly from the HTTP server, because hts will |
| 69 |
service many connections during the lifetime of the tunnel. If the |
| 70 |
HTTP server executed a new instance of hts every time a new request |
| 71 |
was made, each new hts wouldn't have access to the prior state of |
| 72 |
the tunnel. |
| 73 |
|
| 74 |
However, a CGI proxy which forwards the requests to a normal hts |
| 75 |
listening to a port != 80 whould most probably be quite trivial to |
| 76 |
implement. |
| 77 |
|
| 78 |
Q: Have you thought of using HTTPS? |
| 79 |
|
| 80 |
A: It has been suggested, but I'd rather avoid all the nasty export |
| 81 |
restrictions. You can use external software to get an encrypted |
| 82 |
tunnel. |
| 83 |
|
| 84 |
Q: On REMOTE (brugd.ctrl-c.liu.se) I do the following: |
| 85 |
hts -F localhost:23 8888 |
| 86 |
|
| 87 |
This worked the first time, but never since... now I only get: |
| 88 |
hts: couldn't create tunnel |
| 89 |
|
| 90 |
A: The first hts is still running in the background. |
| 91 |
|
| 92 |
Q: On LOCAL (dhcp-XXX.enea.se) I do: |
| •93 |
htc -F 2323 -P internwebb/proxy2.pac:8000 brugd.ctrl-c.liu.se:8888 |
| 94 |
|
| 95 |
Now, I try: |
| 96 |
[root@localhost httptunnel-1.101]# telnet localhost 2323 |
| 97 |
Trying 127.0.0.1... |
| 98 |
telnet: Unable to connect to remote host: Connection refused |
| 99 |
|
| 100 |
A: [Christian Brideau] http://internwebb/proxy2.pac:8000 is not |
| •101 |
exactly the proxy's address. This is the location of the |
| 102 |
Proxy-Auto-Configure (PAC) file. This file contains the address of |
| 103 |
the proxy server. To discover the real address, just go to an |
| 104 |
external web page using a browser and then use netstat to figure |
| •105 |
out what address your browser is using. |
| 106 |
|
| 107 |
Q: Why does 'configure' fail on HP-UX? |
| 108 |
|
| 109 |
A: Because you haven't installed gcc. If |
| 110 |
CFLAGS=-O ./configure |
| 111 |
doesn't work, you must get gcc, or at least an ANSI C compiler. |
| •112 |
|
| 113 |
Q: When I use SSH (or VNC, or <insert other program here>) over GNU |
| 114 |
httptunnel, the program locks up after a few minutes (or hours). |
| 115 |
When I close the program and attempt to reconnect, SSH times out. |
| 116 |
What's wrong? |
| 117 |
|
| 118 |
A: Your httptunnel connection has failed on the client end (possibly |
| 119 |
due to network congestion), but the server end has not recognized |
| 120 |
that the connection has been lost and won't allow another |
| 121 |
connection until the first connection times out. To establish a |
| 122 |
more stable tunnel, try experimenting with the various options for |
| 123 |
the htc and hts programs. The following settings seem to work |
| 124 |
pretty well for me, but your mileage may vary: |
| 125 |
|
| 126 |
hts -S --max-connection-age 20000 -F localhost:22 8890 |
| 127 |
|
| 128 |
htc -F 8890 --strict-content-length -B 5k --max-connection-age 2000 \ |
| 129 |
-P proxy.mycompany.com:8080 10.1.1.1:8890 |
| 130 |
|
| 131 |
Q: Okay, I've found some settings that seem to work for me, but I |
| 132 |
still get "locked out" on occasion and have to wait for the server |
| 133 |
end (hts) to time out. Is there any way to reestablish the tunnel |
| 134 |
without waiting for hts to timeout? |
| 135 |
|
| 136 |
A: Set up at least two tunnels. After the first tunnel hangs, connect |
| 137 |
to the ffserver machine using SSH (or Telnet if you don't care |
| 138 |
about security) and manually kill the instance of the hts server |
| 139 |
that is hung and recreate the tunnel by running hts again. Then |
| 140 |
you should be able to reconnect to the original tunnel. BE SURE TO |
| 141 |
KILL THE TUNNEL THAT IS HUNG UP, NOT THE ONE TO WHICH YOU ARE |
| 142 |
CONNECTED! How do you do this? Here is an example of how to do |
| 143 |
this on Linux. [On a Windows server, a similar technique should |
| 144 |
work, but it may be more difficult to distinguish between separate |
| 145 |
instances of hts on Windows because Task Manager only displays the |
| 146 |
name of the program (hts) and not the full command that launched |
| 147 |
it.] |
| 148 |
|
| 149 |
$ ps aux w|grep hts #Use the 'w' option to see the entire line |
| 150 |
#so that you can determine which instance of |
| 151 |
#hts to kill depending on the port number. |
| 152 |
|
| 153 |
my_user_name 7268 0.0 0.3 1692 768 ? S Sep24 0:00 hts -S -F localhost:22 8890 |
| 154 |
my_user_name 7270 0.0 0.2 1692 744 ? S Sep24 0:00 hts -S -F localhost:22 8891 |
| 155 |
my_user_name 10515 0.0 0.2 1692 720 ? S 15:37 0:00 hts -S -F localhost:22 8889 |
| 156 |
my_user_name 10549 0.0 0.2 1624 616 pts/2 S 15:40 0:00 grep hts |
| 157 |
|
| 158 |
$ kill 10515 #assuming that the httptunnel on port 8889 is the one |
| 159 |
#that has hung up |
| 160 |
|
| 161 |
$ hts -S -F localhost:22 8889 #restart hts with the same options to |
| 162 |
#reestablish the tunnel. |
| 163 |
|
| 164 |
Once you have reestablished the tunnel, your existing instance of htc on |
| 165 |
the client should be able to reestablish the tunnel without any additional |
| 166 |
steps. If in doubt, you could also kill htc on the client and rerun htc, |
| 167 |
but I have not generally found that to be necessary. |
| 168 |
|
| 169 |
Q: Why do I keep getting errors like the ones listed below in my |
| 170 |
Application Event Log while using htc on Windows? What does "HTTP |
| 171 |
error -503" mean? |
| 172 |
|
| 173 |
9/24/2001 2:10:15 PM htc Error None 0 N/A MYPC_NAME The description for |
| 174 |
Event ID ( 0 ) in Source ( htc ) cannot be found. The local computer may not |
| 175 |
have the necessary registry information or message DLL files to display |
| 176 |
messages from a remote computer. The following information is part of the |
| 177 |
event: htc : Win32 Process Id = 0x6BC : Cygwin Process Id = 0x6BC : exit |
| 178 |
with status = 1. |
| 179 |
|
| 180 |
9/24/2001 2:10:15 PM htc Error None 0 N/A MYPC_NAME The description for |
| 181 |
Event ID ( 0 ) in Source ( htc ) cannot be found. The local computer may not |
| 182 |
have the necessary registry information or message DLL files to display |
| 183 |
messages from a remote computer. The following information is part of the |
| 184 |
event: htc : Win32 Process Id = 0x6BC : Cygwin Process Id = 0x6BC : couldn't |
| 185 |
open tunnel: I/O error. |
| 186 |
|
| 187 |
9/24/2001 2:10:15 PM htc Error None 0 N/A MYPC_NAME The description for |
| 188 |
Event ID ( 0 ) in Source ( htc ) cannot be found. The local computer may not |
| 189 |
have the necessary registry information or message DLL files to display |
| 190 |
messages from a remote computer. The following information is part of the |
| 191 |
event: htc : Win32 Process Id = 0x6BC : Cygwin Process Id = 0x6BC : |
| 192 |
http_error_to_errno: HTTP error -503. |
| 193 |
|
| 194 |
9/24/2001 2:10:15 PM htc Error None 0 N/A MYPC_NAME The description for |
| 195 |
Event ID ( 0 ) in Source ( htc ) cannot be found. The local computer may not |
| 196 |
have the necessary registry information or message DLL files to display |
| 197 |
messages from a remote computer. The following information is part of the |
| 198 |
event: htc : Win32 Process Id = 0x6BC : Cygwin Process Id = 0x6BC : |
| 199 |
tunnel_in_connect: HTTP error 503. |
| 200 |
|
| 201 |
A: HTTP 503 is the standard HTTP error that means "Service |
| 202 |
Unavailable." In this case, it means that the htc client cannot |
| 203 |
connect to the server. In the example above, the hts program had |
| •204 |
not yet been started on their server side, but the same error might |
| 205 |
indicate other types of network or server errors. |