03-14-2013
two listens seems wrong. The proxy listens on 8080, the web server is already on 80. Usually proxies just tcp connect for you, tunnels are for ssh.
Last edited by DGPickett; 03-14-2013 at 04:47 PM..
7 More Discussions You Might Find Interesting
1. IP Networking
Does any one know how to block HTTP Tunnel in squid proxy server.
Pls reply (1 Reply)
Discussion started by: vishwanathhcl
1 Replies
2. Shell Programming and Scripting
Hi there
I am currently trying to access an http site using the wget utility from a solaris box. I am going through proxies to do this and we have two types of proxies.
For the first one, which is a netcache proxy, I am able to use the wget command to export the proxy information
export... (2 Replies)
Discussion started by: memonks
2 Replies
3. Programming
I am having problems receiving data from a remote server. It seems that I can send an HTTP request to any host such as http://www.google.com, but I can't get a reply.
I'm sending the host a HTTP 1.0 request that is formatted as such:
GET / HTTP/1.0
Host: http://www.google.com
Connection:... (0 Replies)
Discussion started by: shubham92
0 Replies
4. Shell Programming and Scripting
Simple Http Proxy Server Checker Script with curl
mirror proxies-scripts/proxc at master * Anoncheg1/proxies-scripts * GitHub
output in terminal
HTTP, HTTP Connect (HTTPS not supported)
command line:
proxc filename
where filename is file like
119.110.69.185:8080
119.235.16.41:8080... (4 Replies)
Discussion started by: 654321
4 Replies
5. Emergency UNIX and Linux Support
I need to setup a proxy that will sit in front of a websockets server and proxy websockets communication both to and from the server. There will only be one specific client trying to access this server using the websockets protocol. We can configure the proxy settings for port and IP on the... (3 Replies)
Discussion started by: glev2005
3 Replies
6. UNIX for Dummies Questions & Answers
Hello, i setup an open socks proxy on my remote vps:
ssh -f -N -D 0.0.0.0:1080 localhost
and then allowed only connections from IP of my home computer
iptables -A INPUT --src myhomeip -p tcp --dport 1080 -j ACCEPT
iptables -A INPUT -p tcp --dport 1080 -j REJECT
but it appears that im... (3 Replies)
Discussion started by: postcd
3 Replies
7. AIX
Hi,
I am trying to configure an HTTP_PROXY so that suma can reach out beyond our intranet and pull updates from the IBM website. Currently, our suma config is the default as it's not been used before. When I attempt to issue the following command sudo suma... (7 Replies)
Discussion started by: JAR1
7 Replies
LEARN ABOUT NETBSD
tftp-proxy
TFTP-PROXY(8) BSD System Manager's Manual TFTP-PROXY(8)
NAME
tftp-proxy -- Internet Trivial File Transfer Protocol proxy
SYNOPSIS
tftp-proxy [-v] [-w transwait]
DESCRIPTION
tftp-proxy is a proxy for the Internet Trivial File Transfer Protocol invoked by the inetd(8) internet server. TFTP connections should be
redirected to the proxy using the pf(4) rdr command, after which the proxy connects to the server on behalf of the client.
The proxy establishes a pf(4) rdr rule using the anchor facility to rewrite packets between the client and the server. Once the rule is
established, tftp-proxy forwards the initial request from the client to the server to begin the transfer. After transwait seconds, the pf(4)
NAT state is assumed to have been established and the rdr rule is deleted and the program exits. Once the transfer between the client and
the server is completed, the NAT state will naturally expire.
Assuming the TFTP command request is from $client to $server, the proxy connected to the server using the $proxy source address, and $port is
negotiated, tftp-proxy adds the following rule to the anchor:
rdr proto udp from $server to $proxy port $port -> $client
The options are as follows:
-v Log the connection and request information to syslogd(8).
-w transwait
Number of seconds to wait for the data transmission to begin before removing the pf(4) rdr rule. The default is 2 seconds.
CONFIGURATION
To make use of the proxy, pf.conf(5) needs the following rules. The anchors are mandatory. Adjust the rules as needed for your configura-
tion.
In the NAT section:
nat on $ext_if from $int_if -> ($ext_if:0)
no nat on $ext_if to port tftp
rdr-anchor "tftp-proxy/*"
rdr on $int_if proto udp from $lan to any port tftp ->
127.0.0.1 port 6969
In the filter section, an anchor must be added to hold the pass rules:
anchor "tftp-proxy/*"
inetd(8) must be configured to spawn the proxy on the port that packets are being forwarded to by pf(4). An example inetd.conf(5) entry fol-
lows:
127.0.0.1:6969 dgram udp wait root
/usr/libexec/tftp-proxy tftp-proxy
SEE ALSO
tftp(1), pf(4), pf.conf(5), ftp-proxy(8), inetd(8), syslogd(8), tftpd(8)
CAVEATS
tftp-proxy chroots to /var/chroot/tftp-proxy and changes to user ``_proxy'' to drop privileges.
BSD
May 31, 2007 BSD