This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
start [2018/12/06 21:48] abeverley [Using iptables and PHP to create a captive portal] |
start [2018/12/06 21:48] abeverley |
||
---|---|---|---|
Line 19: | Line 19: | ||
===== Fair traffic shaping an ADSL line for a local network using Linux ===== | ===== Fair traffic shaping an ADSL line for a local network using Linux ===== | ||
- | * Traffic shaping a standard ADSL link in order to share it with a couple of hundred users is a common problem. There are dozens of bits of software and firewall scripts out there already to do this. This particular page details a method that I have used successfully for several years. It aims to be as simple as possible, is easily customised, and uses connlimit to identify P2P users. Although the latter is not 100% reliable, it seems to work pretty well and does not fall foul of any new/changed P2P software that happens to some of the other scripts. The page is written as more of a tutorial; if you would like to use this in practice, then I recommend you check out the scripts in the "captive portal from scratch" page below. [[Fair_traffic_shaping_an_ADSL_line_for_a_local_network_using_Linux|Fair traffic shaping an ADSL line for a local network using Linux]] | + | Traffic shaping a standard ADSL link in order to share it with a couple of hundred users is a common problem. There are dozens of bits of software and firewall scripts out there already to do this. This particular page details a method that I have used successfully for several years. It aims to be as simple as possible, is easily customised, and uses connlimit to identify P2P users. Although the latter is not 100% reliable, it seems to work pretty well and does not fall foul of any new/changed P2P software that happens to some of the other scripts. The page is written as more of a tutorial; if you would like to use this in practice, then I recommend you check out the scripts in the "captive portal from scratch" page below. [[Fair_traffic_shaping_an_ADSL_line_for_a_local_network_using_Linux|Fair traffic shaping an ADSL line for a local network using Linux]] |
===== Setting up a captive portal from scratch using Debian ===== | ===== Setting up a captive portal from scratch using Debian ===== | ||
- | * The link below gives the full details from start to finish of installing the Debian operating system, setting up a captive portal and shaping traffic fairly for dozens of users. [[Setting_up_a_captive_portal_from_scratch_using_Debian|Setting up a captive portal from scratch using Debian]] | + | The link below gives the full details from start to finish of installing the Debian operating system, setting up a captive portal and shaping traffic fairly for dozens of users. [[Setting_up_a_captive_portal_from_scratch_using_Debian|Setting up a captive portal from scratch using Debian]] |
===== PortalShaper - details of the scripts used in the installation above ===== | ===== PortalShaper - details of the scripts used in the installation above ===== | ||
Line 55: | Line 55: | ||
===== Setup SMTP authentication with Postfix running on Debian ===== | ===== Setup SMTP authentication with Postfix running on Debian ===== | ||
- | * The original idea of this page was a quick and dirty howto on how to setup SMTP authentication on Postfix. However, it turned out that there was no quick way to achieve what I wanted (encrypted passwords over an unencrypted link, using Courier IMAP as the password database). It also turned out that I was running a non-standard Postfix (it wasn't chrooted). Therefore, as SMTP AUTH and SASL have always been something of a black art to me, I have written a few things down that I have discovered, as well as a quick and dirty howto on setting up a basic SASL database. [[SMTP_authentication_and_Postfix|SMTP authentication and Postfix]] | + | The original idea of this page was a quick and dirty howto on how to setup SMTP authentication on Postfix. However, it turned out that there was no quick way to achieve what I wanted (encrypted passwords over an unencrypted link, using Courier IMAP as the password database). It also turned out that I was running a non-standard Postfix (it wasn't chrooted). Therefore, as SMTP AUTH and SASL have always been something of a black art to me, I have written a few things down that I have discovered, as well as a quick and dirty howto on setting up a basic SASL database. [[SMTP_authentication_and_Postfix|SMTP authentication and Postfix]] |
===== Setup clamav with Postfix on Debian Lenny in a chroot ===== | ===== Setup clamav with Postfix on Debian Lenny in a chroot ===== | ||
- | * Some quick steps showing something that's quite easy but not immediately obvious. [[Setup_clamav_with_Postfix_on_Debian_Lenny_in_a_chroot|Setup clamav with Postfix on Debian Lenny in a chroot]] | + | Some quick steps showing something that's quite easy but not immediately obvious. [[Setup_clamav_with_Postfix_on_Debian_Lenny_in_a_chroot|Setup clamav with Postfix on Debian Lenny in a chroot]] |