| Summary: | net-proxy/bfilter needs forwarding.xml if gui is not used | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Lorinc Czegledi <lorinc.czegledi> |
| Component: | Current packages | Assignee: | Gentoo Network Proxy Developers (OBSOLETE) <net-proxy+disabled> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://blog.cpst.hu/article20 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
the maintainer has a strange opinion about documenting this feature, see here: http://prxbx.com/forums/showthread.php?tid=1004 "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." Fixed in version 1.1.4-r1 by installing a default forward.xml configured for direct forwarding along with a forwarding-proxy.xml example installed in the doc directory. |
bfilter without gui has no forwarding.xml , please provide a forwarding.xml.example with the ebuild files Reproducible: Always Steps to Reproduce: 1. emerge bfilter 2. look in /etc/bfilter for forwarding.xml, none found 3. create forwarding.xml add forwarding.xml.example to files for ebuild example code (works for me with tor): <?xml version="1.0" encoding="UTF-8"?> <forwarding> <option name="Direct"> </option> <option name="TOR Proxy" selected="selected"> <bypass> <simple-hostnames/> <host-mask>*.isp.com</host-mask> <host-mask>192.168.*</host-mask> </bypass> <proxy-chain> <proxy> <type>socks4a</type> <host>localhost</host> <port>9050</port> </proxy> </proxy-chain> </option> </forwarding>