From: "plugthebox.net /dev/null" <devnull@plugthebox.net>
To: lartc@vger.kernel.org
Subject: [LARTC] htb/iptables for ISP
Date: Wed, 25 Oct 2006 09:24:22 +0000 [thread overview]
Message-ID: <1161768263.19237.12.camel@localhost> (raw)
Hello,
I'm working on a customized Linux firewall/router for a small/medium ISP
(1200 users) we have almost 4 ranges of internal IPs and i want to limit
each IP to a certain speed.
The problem is that i'm storing all info about the user including IP and
bandwidth rates on a MySQL server, then dump all the htb/sfq lines on a
file (which takes 3 minutes) and then i run these files. This process
kills my machine for 3-4 minutes until dumping all htb/sqf/iptables into
files and running these files (remember that i almost have 1200 IPs, and
each IP has 6 HTB+SFQ line with 2 iptables)
Is there another method more efficient than re-running my files every
time i add/edit/del a user?
Sincerely,
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2006-10-25 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 9:24 plugthebox.net /dev/null [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-04 10:00 [LARTC] htb/iptables for ISP Peter Surda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1161768263.19237.12.camel@localhost \
--to=devnull@plugthebox.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox