LocalProxy 'Add plugin service' example
Let's say you want to add a Socks4 service listening on (LP's) localhost:11080,
to a running localProxy.
LP must already be running (though maybe it's half way around the world!)
The Simple Window is open.
- Click 'Go advanced'.
- Click 'Add plugin service'. A new window should appear.
- Select 'Socks4' from the 'Type of service' list.
- Enter 11080 in the 'local port' field. For this service, leave the
'Remote service (addr:port)' field empty (LP will select the remote Socks
servers for you). More about this field below.
- Click OK. Wait for the window to disappear and take you back to the
Advanced window - which should repaint.
You should see the new service listed in the 'Services' list along with
all the others. That's it!
Usually, LP's localhost will be your localhost, so now you can use any Sock4
client by telling it there is a Socks service on localhost:11080.
If your localProxy back end is running on some other computer at IP address
(say, ipAddr), then tell your clients that their Socks proxy is at
ipAddr:11080.
Your web browser, IRC client etc. should be able to work with this.
LP 'abstracts' services in two conceptually different ways:
- a direct abstraction of a single remote service: Example: ccnews.thu.edu.tw:119
is abstracted to localhost:10119 in the default config files.
- an abstraction of a 'distributed' remote service: Example: an uncensored
http proxy service is provided at localhost:10080 by LP using many different
remote http proxies. Another example is the Socks4 service we added above.
For 'distributed' services there is no need to fill in the 'Remote service'
field. LP selects the fastest, most reliable, highest uptime services to
use from hosts.xml, and fills the layers appropriately. For any of these
'distributed' services, you should be able to fill in the 'Remote services'
and LP will only use that one, thus changing it from a 'distributed' to
a 'direct' abstraction.