DOCSLIB.ORG

Firewall and Proxy Server HOWTO Firewall and Proxy Server HOWTO

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Firewall and Proxy Server HOWTO Firewall and Proxy Server HOWTO Firewall and Proxy Server HOWTO Firewall and Proxy Server HOWTO Table of Contents Firewall and Proxy Server HOWTO................................................................................................................1 Mark Grennan, mark@grennan.com.......................................................................................................1 1. Introduction..........................................................................................................................................1 2. Understanding Firewalls......................................................................................................................1 3. Firewall Architecture ..........................................................................................................................1 4. Setting up the Linux Filtering Firewall ...............................................................................................1 5. Software requirements.........................................................................................................................1 6. Preparing the Linux system.................................................................................................................1 7. IP filtering setup (IPFWADM)............................................................................................................2 8. IP filtering setup (IPCHAINS).............................................................................................................2 9. Installing a Transparent SQUID proxy................................................................................................2 10. Installing the TIS Proxy server..........................................................................................................2 11. The SOCKS Proxy Server.................................................................................................................2 12. Advanced Configurations..................................................................................................................2 13. Making Management Easy................................................................................................................2 14. Defeating a Proxy Firewall................................................................................................................2 15. APPENDEX A − Example Scripts....................................................................................................2 16. APPENDEX B − An VPN RC Script for RedHat.............................................................................2 1. Introduction..........................................................................................................................................3 1.1 Feedback............................................................................................................................................3 1.2 Disclaimer .........................................................................................................................................3 1.3 Copyright...........................................................................................................................................3 1.4 My Reasons for Writing this..............................................................................................................4 1.5 Further Readings................................................................................................................................4 2. Understanding Firewalls......................................................................................................................4 2.1 Firewall Politics.................................................................................................................................5 How it create a security policy...................................................................................................5 2.2 Types of Firewalls..............................................................................................................................5 Packet Filtering Firewalls...........................................................................................................6 Proxy Servers..............................................................................................................................6 Application Proxy.......................................................................................................................6 SOCKS Proxy.............................................................................................................................7 3. Firewall Architecture ..........................................................................................................................7 3.1 Dial−up Architecture.........................................................................................................................7 3.2 Single Router Architecture................................................................................................................7 3.3 Firewall with Proxy Server................................................................................................................7 3.4 Redundent Internet Configuration.....................................................................................................8 4. Setting up the Linux Filtering Firewall ...............................................................................................8 4.1 Hardware requirements......................................................................................................................9 5. Software requirements.........................................................................................................................9 5.1 Selecting a Kernel..............................................................................................................................9 5.2 Selecting a proxy server.....................................................................................................................9 6. Preparing the Linux system...............................................................................................................10 6.1 Compiling the Kernel.......................................................................................................................10 6.2 Configuring two network cards.......................................................................................................11 6.3 Configuring the Network Addresses................................................................................................11 6.4 Testing your network.......................................................................................................................13 6.5 Securing the Firewall.......................................................................................................................14 i Firewall and Proxy Server HOWTO Table of Contents 7. IP filtering setup (IPFWADM)..........................................................................................................15 8. IP filtering setup (IPCHAINS)...........................................................................................................17 9. Installing a Transparent SQUID proxy..............................................................................................19 10. Installing the TIS Proxy server........................................................................................................19 10.1 Getting the software.......................................................................................................................19 10.2 Compiling the TIS FWTK.............................................................................................................19 10.3 Installing the TIS FWTK ..............................................................................................................19 10.4 Configuring the TIS FWTK...........................................................................................................19 The netperm−table file..............................................................................................................20 The /etc/services file.................................................................................................................23 11. The SOCKS Proxy Server...............................................................................................................23 11.1 Setting up the Proxy Server...........................................................................................................23 11.2 Configuring the Proxy Server........................................................................................................23 The Access File.........................................................................................................................23 The Routing File.......................................................................................................................24 11.3 Working With a Proxy Server........................................................................................................25 Unix..........................................................................................................................................25 MS Windows with Trumpet Winsock......................................................................................25 Getting the Proxy Server to work with UDP Packets...............................................................26
Load more

Recommended publications
  • Proceedings of the Bsdcon 2002 Conference
    USENIX Association Proceedings of the BSDCon 2002 Conference San Francisco, California, USA February 11-14, 2002 THE ADVANCED COMPUTING SYSTEMS ASSOCIATION © 2002 by The USENIX Association All Rights Reserved For more information about the USENIX Association: Phone: 1 510 528 8649 FAX: 1 510 548 5738 Email: [email protected] WWW: http://www.usenix.org Rights to individual papers remain with the author or the author's employer. Permission is granted for noncommercial reproduction of the work for educational or research purposes. This copyright notice must be included in the reproduced paper. USENIX acknowledges all trademarks herein. Flexible Packet Filtering: Providing a Rich Toolbox Kurt J. Lidl Deborah G. Lidl Paul R. Borman Zero Millimeter LLC Wind River Systems Wind River Systems Potomac, MD Potomac, MD Mendota Heights, MN [email protected] [email protected] [email protected] Abstract The BSD/OS IPFW packet filtering system is a well engineered, flexible kernel framework for filtering (accepting, rejecting, logging, or modifying) IP packets. IPFW uses the well understood, widely available Berkeley Packet Filter (BPF) system as the basis of its packet matching abilities, and extends BPF in several straightforward areas. Since the first implementation of IPFW, the system has been enhanced several times to support additional functions, such as rate filtering, network address translation (NAT), and traffic flow monitoring. This paper examines the motivation behind IPFW and the design of the system. Comparisons with some contemporary packet filtering systems are provided. Potential future enhancements for the IPFW system are discussed. 1 Packet Filtering: An Overview might choose to copy only this data.
    [Show full text]
  • Block Icmp Ping Requests
    Block Icmp Ping Requests Lenard often unpenned stutteringly when pedigreed Barton calques wittingly and forsook her stowage. Garcia is theropod vermiculatedand congregate unprosperously. winningly while nonnegotiable Timothy kedges and sever. Gyrate Fazeel sometimes hasting any magnetron Now we generally adds an email address of icmp block ping requests That after a domain name, feel free scans on or not sent by allowing through to append this friendship request. Might be incremented on your Echo press and the ICMP Echo reply messages are commonly as! Note that ping mechanism blocks ping icmp block not enforced for os. This case you provide personal information on. Send to subvert host directly, without using routing tables. Examples may be blocked these. Existence and capabilities is switched on or disparity the protocol IP protocol suite, but tcp is beat of. We are no latency and that address or another icmp message type of icmp ping so via those command in this information and get you? Before assigning it is almost indistinguishable from. Microsoft Windows found themselves unable to download security updates from Microsoft; Windows Update would boost and eventually time out. Important mechanisms are early when the ICMP protocol is restricted. Cisco device should be valuable so a host that block icmp? Add a normal packet will update would need access and others from. Now check if you? As an organization, you could weigh the risks of allowing this traffic against the risks of denying this traffic and causing potential users troubleshooting difficulties. Icmp block icmp packets. Please select create new know how long it disables a tcp syn flood option available in specific types through stateful firewalls can have old kernels.
    [Show full text]
  • Internet of Things
    8.5 GB Motorola Xiaomi Mi Lenovo A lightweight and Dual Layer DVD Moto Turbo A Powerful Processor Low on cost but high Yoga 3 Pro Free on performance premium quality Free Smartphone With a Brilliant Screen Pad Tablet Hybrid Laptop convertible `150 Remote Desktop Sharing with Chrome Recover Data from www.pcquest.com Encryped Hard Disk UNDERSTAND • CHOOSE • IMPLEMENT IT MAY 2015 with Ubuntu Internet of Things: The Road Ahead Key industries that are bullish on IoT and why, ISVs that live on IoT, 5 innovative IoT startups, latest trends on IoT adoption by businesses, and more... CONTEST: If your disks are missing, please ask your newsagent or email: [email protected] please ask your newsagent or email: If your disks are missing, WIN Ashampoo Snap 8 screen capturing tool and licensed copy of KEYWIN worth `44,000. See pg 58 for details Hot Trends: Developer Corner: The Pros and Cons of Net Neutrality How to Reduce Vulnerabilities in Android Apps How Online-only Mobile Brands are Shootouts Redefining Retail 12 Portable Bluetooth Speakers 5 Big Data Costs You Can’t Afford to Ignore 10 Budget Smartphones under `10,000 Subscribe to PCQuest and get antivirus worth `1,800 free. For details, go to pg. 74 92 pages including cover Contents 36 COVER STORY Internet of Things: The Road Ahead Moving beyond the initial euphoria, IoT has steadily progressed to impact our lives in several meaningful ways. Going forward we expect both businesses and individuals to make steady returns on their investments 38 5 Key Industries that are Bullish on IoT 42
    [Show full text]
  • Ipfire Duobox Business, 4 GB RAM, 64 GB SSD
    Item no.: 323825 IPFire DuoBox Business, 4 GB RAM, 64 GB SSD from 462,37 EUR Item no.: 323825 shipping weight: 1.20 kg Manufacturer: IPFire Product Description IPFire DuoBox Business, 4 GB RAM, 64 GB SSDThis Firewall version was specifically designed for small offices und home offices, in which a stable and fast Internet connection is essential. The Duo Box Business provides you with fast Internet, while being low-cost and energy-efficient. It keeps your business connected and, most importantly, it keeps your network safe. Main Features: ● 2x Gigabit Ethernet for LAN and WAN ● 1x 300 Mbit dual-band Wi-Fi with access point mode ● optionally upgradeable with LTE Scope of Delivery: ● System ● Power Cable ● PSU ● 2x WLAN antennas Specifications Application: Firewall application for SOHO, branch offices and IoT Type: aluminum profile construction without venting holes, black anodized Dimensions (W x D x H): 134 x 108 x 55 mm Weight: 1.2 kg Cooling: directly attached to chassis Operating conditions: 0 - 50 °C / 80 % rel. humidity CPU: Intel Pentium 3558U, 2x 1.7 GHz RAM: 4 GB DDR3L Mainboard: customized eNUC platform I/O front (standard): 1x RS232, 1x USB 3.0, 1x Audio I/O back: 2x HDMI, 2x USB 3.0, 2x RJ45 (Realtek GLAN) I/O internal: internal I/O might be occupied - depending on your configuration, 1x mSATA/mPCIe full size, 2x USB 2.0 Storage: 1x 2.5" 64 GB SSD (industrial, MLC, 0 - +70 °C ) Graphics: Intel HD, up to 2 independend displays supported, max. resolution: 3840 x 2160 px Wireless LAN, Unex DNUR-S2 300 Mbit dual-band WLAN module LTE: Huawei 909u-5214G LTE (FDD) B1/B2/B3/B5/B7/B8/B203G DC-HSPA+/HSPA+/HSPA/UMTS B1/B2/B5/B82G EDGE/ GPRS/ GSM - 850/900/1800/1900MHz Power-In: DC wide-input 9..19V, 5.5 x 2.5 mm plug PSU: FSP060-DHAN3; external AC/DC adapterInput: 90 to 264 V ACOutput: 12 V / 60 W Power consumption: Idle 6 W, 100% load (Cel.) 11 W OS compatibility: IPFire, OPNSense, PFSense, Ubuntu Linux Scan this QR code to view the product All details, up-to-date prices and availability Powered by TCPDF (www.tcpdf.org).
    [Show full text]
  • Debian \ Amber \ Arco-Debian \ Arc-Live \ Aslinux \ Beatrix
    Debian \ Amber \ Arco-Debian \ Arc-Live \ ASLinux \ BeatriX \ BlackRhino \ BlankON \ Bluewall \ BOSS \ Canaima \ Clonezilla Live \ Conducit \ Corel \ Xandros \ DeadCD \ Olive \ DeMuDi \ \ 64Studio (64 Studio) \ DoudouLinux \ DRBL \ Elive \ Epidemic \ Estrella Roja \ Euronode \ GALPon MiniNo \ Gibraltar \ GNUGuitarINUX \ gnuLiNex \ \ Lihuen \ grml \ Guadalinex \ Impi \ Inquisitor \ Linux Mint Debian \ LliureX \ K-DEMar \ kademar \ Knoppix \ \ B2D \ \ Bioknoppix \ \ Damn Small Linux \ \ \ Hikarunix \ \ \ DSL-N \ \ \ Damn Vulnerable Linux \ \ Danix \ \ Feather \ \ INSERT \ \ Joatha \ \ Kaella \ \ Kanotix \ \ \ Auditor Security Linux \ \ \ Backtrack \ \ \ Parsix \ \ Kurumin \ \ \ Dizinha \ \ \ \ NeoDizinha \ \ \ \ Patinho Faminto \ \ \ Kalango \ \ \ Poseidon \ \ MAX \ \ Medialinux \ \ Mediainlinux \ \ ArtistX \ \ Morphix \ \ \ Aquamorph \ \ \ Dreamlinux \ \ \ Hiwix \ \ \ Hiweed \ \ \ \ Deepin \ \ \ ZoneCD \ \ Musix \ \ ParallelKnoppix \ \ Quantian \ \ Shabdix \ \ Symphony OS \ \ Whoppix \ \ WHAX \ LEAF \ Libranet \ Librassoc \ Lindows \ Linspire \ \ Freespire \ Liquid Lemur \ Matriux \ MEPIS \ SimplyMEPIS \ \ antiX \ \ \ Swift \ Metamorphose \ miniwoody \ Bonzai \ MoLinux \ \ Tirwal \ NepaLinux \ Nova \ Omoikane (Arma) \ OpenMediaVault \ OS2005 \ Maemo \ Meego Harmattan \ PelicanHPC \ Progeny \ Progress \ Proxmox \ PureOS \ Red Ribbon \ Resulinux \ Rxart \ SalineOS \ Semplice \ sidux \ aptosid \ \ siduction \ Skolelinux \ Snowlinux \ srvRX live \ Storm \ Tails \ ThinClientOS \ Trisquel \ Tuquito \ Ubuntu \ \ A/V \ \ AV \ \ Airinux \ \ Arabian
    [Show full text]
  • Critical Infrastructure Cybersecurity V-6
    Critical Infrastructure Cybersecurity: An Overview Presented by: Daniel E. Capano, SWPCA Justin Finnigan, Arcadis Cybercrime is a Growth Industry • Typically Low risk and High payoff • Threat Actors will attack soft targets first • Soft Targets = Many vulnerabilities • Soft Targets include “Critical Infrastructure” • Executive Order 13636 defines Critical Infrastructure as: “Systems and assets, whether physical or virtual, so vital to the United States that the incapacity or destruction of such systems and assets would have a debilitating impact on cybersecurity, national economic security, national public health or safety, or any combination of those matters” Water Treatment Facilities • As more automation is used to control and monitor processes, the attack surface grows with it, and threat grows proportionately. • Conversely, reduction of the human element will reduce the attack surface • Disruption of water supply or waste treatment processes would have major disruptive and health impacts on the populace. • While there is no financial or technical incentive, mayhem and disruption remain goals • Air-gapping of the facility is no longer practical Modes of Attack • Social Engineering:The Human Element • Bring Your Own Device: Mobile devices can be compromised and contain sensitive info • Internal Threats: malicious or disgruntled employees • External Threats: Hostile governments • Reconnaissance: Find and research the target • Assessment: Determine its vulnerabilities • Exploit Vulnerability: Gain access and commit mayhem Stuxnet: A Game Changer • Stuxnet is a precision “Digital Weapon”, the first to specifically target a control system • Stuxnet was designed to destroy 1,000 Uranium Enrichment Centrifuges at the highly secure Natanz nuclear enrichment lab in Iran. • The facility is “air-gapped”: It is isolated physically and electronically from the world • Stuxnet specifically targeted Siemens S7 PLCs and attached frequency converters.
    [Show full text]
  • Μvirt: Virtualization on Openwrt
    μVirt: Virtualization on OpenWrt Mathew McBride <[email protected]> @mcbridematt Why virtualize? ● “Universal CPE” concept ○ Telco point of view: Standardized (“whitebox”) CPE, (Truck)roll once, deploy many ○ Often as a method of extending private cloud to customer “edge” https://www.sdxcentral.com/articles/contributed/understanding-use-universal-cpe/2017/07/ Image from article (ADVA Optical Networking / SDxcentral) Goals ● Demonstrator for small virtualization on ARM64 ● Particular emphasis on “Universal CPE” use case ○ Customer sites with “appliance” spec boxes (typical 4-16GB RAM, <=256GB SSD) ○ Typical setup: Firewall, VoIP, IDS/IPS, SD-WAN VM’s ● Easy to use - works standalone ○ vs OpenStack, Industry (MANO) or commercial NFV stacks. ● Playground for end-to-end solutions ○ Working towards a demonstrator involving central management, SD-WAN/VPN, remote IPMI and full life cycle provisioning via LTE ● Would like to make advanced acceleration techniques available while still integrating with existing OpenWrt config structures Other use cases ● Deploying value add applications to existing fleet ○ E.g Home automation / Smart Home, media servers for residential CPE ○ Some carriers’ residential CPE are in the “micro” uCPE class already ● Multi-tenant virtualized router for MDUs ● Home router and server in a box ○ e.g OpenWrt + NextCloud ● Run software too complex for OpenWrt ● Isolation via VMs Why on OpenWrt? ● Small footprint ○ Fitting inside unmanaged flash (NOR/NAND) provides BOM savings ■ 128MB,1G,64GB,> 128GB price/technology barriers
    [Show full text]
  • Sophos Xg Policy Routing
    Sophos Xg Policy Routing Mechanized and canaliculated Reza greets so singingly that Buster penalised his lanthanum. Marlon is endemic and impost abstractively as woodworking Hugh degauss disadvantageously and placates aft. Westbound Chauncey brutalise some retard after goalless Thacher dry-rot excruciatingly. Enter your network and if you want to that will show disconnected and bridging deployments handle the. This does webex meetings traffic passing through sophos xg firewall rules for sophos utm cannot easily incorporate heartbeat status of foreign companies. You are essential cookies per offrirti una migliore esp traffic to sophos connect kerio control over the interesting traffic shaping, sophos xg will then type each section. Ipfire is recognized, for free firewall device is able to discover an individual needs answer would lan subnet to analyze live. The sophos ui and destination networks and other traffic selector settings as the network so i went and apple and how it in place, a very time. Sophos xg firewall rule, you to test: check my way to see that result from the goal is commonly for. Palo alto network while you save a sophos xg policy routing options if you delete this site vpn sophos xg firewall also have a new layer to each item. Lan zones in azure portal from the networks for optional for an analog telephone system administrators can create the. Nat policy based on xg and palo alto networks and personalization of policies. In sophos community and routing of the nva adds a sophos xg policy routing. Lateral movement of sophos xg ipsec policy routes based on one site.
    [Show full text]
  • Nftables Och Iptables En Jämförelse Av Latens Nftables and Iptables a Comparison in Latency
    NFtables and IPtables Jonas Svensson Eidsheim NFtables och IPtables En jämförelse av latens NFtables and IPtables A Comparison in Latency Bachelors Degree Project in Computer Science Network and Systems Administration, G2E, 22.5 hp IT604G Jonas Svensson Eidsheim [email protected] Examiner Jonas Gamalielsson Supervisor Johan Zaxmy Abstract Firewalls are one of the essential tools to secure any network. IPtables has been the de facto firewall in all Linux systems, and the developers behind IPtables are also responsible for its intended replacement, NFtables. Both IPtables and NFtables are firewalls developed to filter packets. Some services are heavily dependent on low latency transport of packets, such as VoIP, cloud gaming, storage area networks and stock trading. This work is aiming to compare the latency between the selected firewalls while under generated network load. The network traffic is generated by iPerf and the latency is measured by using ping. The measurement of the latency is done on ping packets between two dedicated hosts, one on either side of the firewall. The measurement was done on two configurations one with regular forwarding and another with PAT (Port Address Translation). Both configurations are measured while under network load and while not under network load. Each test is repeated ten times to increase the statistical power behind the conclusion. The results gathered in the experiment resulted in NFtables being the firewall with overall lower latency both while under network load and not under network load. Abstrakt Brandväggen är ett av de viktigaste verktygen för att säkra upp nätverk. IPtables har varit den främst använda brandväggen i alla Linux-system och utvecklarna bakom IPtables är också ansvariga för den avsedda ersättaren, NFtables.
    [Show full text]
  • Bab 1 Pendahuluan
    BAB 1 PENDAHULUAN 1.1 Latar Belakang Network Function Virtualization atau biasa yang disebut NFV merupakan sebuah konsep baru dalam mendesain, menyebarkan, dan mengelola sebuah layanan jaringan dengan cara pembuatan virtual sebuah perangkat jaringan dari yang sebelumnya berbentuk fisik atau perangkat keras sehingga dapat dipakai dan dipindahkan di berbagai lokasi jaringan yang diperlukan tanpa harus melakukan pemasangan alat baru. NFV memungkinkan beberapa perangkat jaringan dapat berjalan pada satu komputer. Perangkat – perangkat jaringan yang divirtualkan pada NFV disebut sebagai VNF (Virtual Network Function). Untuk menjalankan VNF dibutuhkan sebuah hypervisor yang mengatur manajemen hardware yang digunakan. Hypervisor atau yang dikenal sebagai virtual machine management dibagi menjadi 2 tipe, yaitu bare-metal hypervisor dan hosted hypervisor. Bare-metal hypevisor dapat berjalan langsung pada perangkat keras komputer sedangkan hosted hypervisor memerlukan operating system environment (OSE) untuk menjalankannya [1]. Salah satu contoh bare- metal hypervisor adalah XEN. Xen ProjectTM adalah platform virtualisasi open source yang mendukung beberapa cloud terbesar dalam produksi saat ini. Amazon Web Services, Aliyun, Rackspace Cloud Umum, Verizon Cloud dan banyak layanan hosting menggunakan software Xen [2]. Salah satu contoh VNF adalah virtual firewall. Kelebihan virtual firewall dibandingkan firewall fisik adalah mudah dikelola, dapat dipakai sesuai kebutuhan, dan efektivitas biaya [3]. Pada tugas akhir ini virtual firewall yang digunakan adalah OPNsense, pfSense, dan IPFire karena ketiga firewall tersebut bisa didapatkan secara gratis dan bersifat open source serta ketiga firewall tersebut dapat dikonfigurasi melalui web. pfSense merupakan firewall berbasis FreeBSD yang sangat populer untuk solusi keamanan serta user dapat melakukan modifikasi dan mudah dalam instalasi [4]. IPFire adalah sebuah distribusi Linux yang berfokus pada setup yang mudah, penanganan yang yang baik, dan tingkat keamanan yang tinggi [5].
    [Show full text]
  • An Open Management and Administration Platform for IEEE 802.11 Networks
    The University of Southern Mississippi The Aquila Digital Community Master's Theses Fall 12-2010 An Open Management and Administration Platform for IEEE 802.11 Networks Biju Raja Bajracharya University of Southern Mississippi Follow this and additional works at: https://aquila.usm.edu/masters_theses Recommended Citation Bajracharya, Biju Raja, "An Open Management and Administration Platform for IEEE 802.11 Networks" (2010). Master's Theses. 395. https://aquila.usm.edu/masters_theses/395 This Masters Thesis is brought to you for free and open access by The Aquila Digital Community. It has been accepted for inclusion in Master's Theses by an authorized administrator of The Aquila Digital Community. For more information, please contact [email protected]. The University of Southern Mississippi AN OPEN MANAGEMENT AND ADMINISTRATION PLATFORM FOR IEEE 802.11 NETWORKS by Biju Raja Bajracharya A Thesis Submitted to the Graduate School of The University of Southern Mississippi in Partial Fulfillment of the Requirements for the Degree of Master of Science December 20 I 0 ABSTRACT AN OPEN MANAGEMENT AND ADMINISTRATION PLATFORM FOR IEEE 802.11 NETWORKS by Biju Raja Bajracharya December 2010 The deployment of Wireless Local Area Network (WLAN) has greatly increased in past years. Due to the large deployment of the WLAN, the immediate need of management plat­ forms has been recognized, which has a significant impact on the performance of a WLAN. Although there are various vendor-specific and proprietary solutions available in the market to cope with the management of wireless LAN, they have problems in interoperability and compatibility. To address this issues, IETF has come up with the interoperability standard of management of WLANs devices, Control And Provisioning of Wireless Access Points (CAPWAP) protocol, which is still in the draft phase.
    [Show full text]
  • Peergaurdian CLI $$ - Forum.Ipfire.Org 1/13/21, 9:03 PM
    [Feature Request] Peergaurdian CLI $$ - forum.ipfire.org 1/13/21, 9:03 PM forum.ipfire.org The old IPFire Forum Archive Search… ! " * Quick links # FAQ $ Login % Home ‹ Index ‹ English Area ‹ Development [Feature Request] Peergaurdian CLI $$ Post Reply & + , Search this topic… ! " 44 posts 1 2 3 ' [Feature Request] Peergaurdian CLI $$ / apoptosis . by apoptosis » March 2nd, 2014, 12:58 pm Posts: 5 Joined: March 2nd, 2014, 11:44 am So I just made a big mistake. I thought ipfire supported blocklists like Peergaurdian, Peerblook, Moblock, pfBlock, IPList. However, I miss read Guardian's url blocklists to be this feature. I ended up buying hardware, and installing ipfire only to find out I was wrong. Then I was like okay, I will just run Peergaurdian CLI like on arch linux: https://wiki.archlinux.org/index.php/PeerGuardian_Linux Only to discover that ipfire does use rpm or deb packaging and instead uses pakfire. Ok, so I will download and build myself so I downloaded the source at sourceforge: http://sourceforge.net/projects/peergua ... n%20Linux/ I want a command line only "slick" installation with ./configure --without-qt4 --disable-dbus Only to discover ipfire doesn't come with gcc, and you must build ipfire from scratch if you want to add a package like this. At this I don't have a linux system handy to do the ipfire build and make my own pakfire package, nor the knowhow to do a good pakfire package. I am willing to pay a bounty over paypal for any one to make a pgl-cli-2.2.4.pakfire package and make it available to everyone..
    [Show full text]