Post Reply 
Forwarding: howto?
Oct. 08, 2007, 08:16 PM
Post: #1
Forwarding: howto?
I'm using BFilter on FreeBSD. Now I want to setup BFilter to forward requests to a Squid proxy. In earlier versions of BFilter, there was an example in the config file how to achieve this, but it's no longer there. Neither can it be found on the website. Can anyone give me a configuration example?
Quote this message in a reply
Oct. 08, 2007, 08:55 PM
Post: #2
RE: Forwarding: howto?
To be able to support proxy chains and multiple forwarding configurations (only useful in a GUI), I moved forwarding configuration from "config" to "forwarding.xml" file. I was too lazy to document it, besides I thought that almost no one uses the non-GUI version.
Here is an example forwarding.xml file:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<forwarding>
    <option name="Direct">
    </option>
    <option name="ISP Proxy" selected="selected">
        <bypass>
            <simple-hostnames/>
            <host-mask>*.isp.com</host-mask>
            <host-mask>192.168.*</host-mask>
        </bypass>
        <proxy-chain>
            <proxy>
                <type>http</type>
                <host>proxy.isp.com</host>
                <port>3128</port>
            </proxy>
        </proxy-chain>
    </option>
</forwarding>
BTW, the old method still works, so you can just keep your old configuration.
Add Thank You Quote this message in a reply
Jun. 02, 2009, 09:12 PM
Post: #3
RE: Forwarding: howto?
Hi,

please advise, how to define forwarding (IP/port of upstream proxy) in file config.
Because I am using Bfilter in a server on the web, I do not use the GUI.
Thanx in advance.
Add Thank You Quote this message in a reply
Oct. 13, 2009, 10:37 PM
Post: #4
RE: Forwarding: howto?
OK, solved; found it in an old BF-version, which I had in stock somewhere <g>.
Add the following to the distributed /etc/bfilter/config:
;[forwarding]
;use_proxy = yes | no
;use_proxy = yes
; When use_proxy is set to yes, you may specify a proxy for bfilter to
; forward requests onto.
;
; proxy_type = http | socks4 | socks4a | socks5
;proxy_type = http
; proxy_host = host
;proxy_host = 127.0.0.1
; proxy_port = port
; proxy_user = username
; proxy_pass = password
; Upstream proxy authentication is currently implemented only for SOCKS
; proxies. Note that socks4 and socks4a don.t use password, just the
; username.
;
; no_proxy_for = host, host, host
; When use_proxy is set to yes, you may specify some hosts to be con-
; tacted directly. The separator may be either a comma or a semicolon. If
; a host starts or ends with a dot it is assumed that any prefix or suf-
; fix can be appended to it, so for example "no_proxy_for = .mydo-
; main.com, 192.168."). Note however that .mydomain.com won.t cover mydo-
; main.com itself but only its subdomains. (When matching no_proxy_for
; hosts, no DNS queries are being made. That means 127.0.0.1 won.t act as
; localhost or the other way around.)
; BFilter allows you to block an arbitrary URL (web address) and to
; assign hints to URL.s in order to influence the heuristic analyzer. To
; do so you assign a tag to a URL allowing both blocking and hinting (and
; more).
;
Add Thank You Quote this message in a reply
Post Reply 


Forum Jump: