From: "Gunther Stammwitz" <gstammw@gmx.net>
To: lartc@vger.kernel.org
Subject: AW: Subject: [LARTC] Mini-ISP-like bandwidth limiter
Date: Sun, 27 Jan 2002 12:46:23 +0000 [thread overview]
Message-ID: <marc-lartc-101213557518447@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101212422305233@msgid-missing>
Hello Arindam,
it sound fine what you're doing :-)
Could you provide some example-scripts please ???
You have to understand that I'm a beginner in QOS.
Thanks and greetings from Germany,
Gunther
-----Ursprungliche Nachricht-----
Von: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]Im
Auftrag von Arindam Haldar
Gesendet: Sonntag, 27. Januar 2002 10:42
An: admin@banpol.com.pl; lartc@mailman.ds9a.nl
Betreff: Subject: [LARTC] Mini-ISP-like bandwidth limiter
hi stan,
Greeting from INDIA .... :-)
We do at our setup with multiple/combo network adapters !.. with
netfilter & lartc not only v do badwidth managment ip based but also a
little bit of la layer 4 switching, priortising usage of our servers !
i dont use GUI interface and am unaware of any but i guess there was
some discussion on netfilter mailing list a few days back for kde
netfilter admin or something like that !
how-to is ones best bet & ofcourse nice guys & gurus on this list makes
it outsanding !
> Message: 3
> From: "Stanis?aw Winiecki - Admin" <admin@banpol.com.pl>
> To: <lartc@mailman.ds9a.nl>
> Date: Fri, 25 Jan 2002 13:29:13 +0100
> Subject: [LARTC] Mini-ISP-like bandwidth limiter
>
> Hi everyone,
>
> Greetings from Poland :)
> I want to be able to allocate portions of the internet link bandwidth to
> several homes in an apartment house. We pay together for internet access
and
> have a Linux router/gateway.
> Now we want to expand a little, i.e. buy a bit more bandwidth and achieve
> the following:
> - A possibility to assign a public IP address to a household (some people
> want to have their own servers at home)
> - Split the bandwidth to a requested level, so that some people could get
> more, some less, and pay their appropriate share in the overall link cost.
>
> It looks to me as a small ISP-like problem :) Of course we run this
network
> privately, so we can't afford a professional bandwidth limiting software
or
> hardware solution.
>
> To be honest I'm not a Linux guru [yet ;)], so learning about LARTC,
> experimenting and maintaining it will take some time. In the meantime I
was
> wondering, whether someone has experience with such a setup, with multiple
> network adapters and hopefully some administration aids (a web-based
> interface would be a dream).
>
> Anyone can help?...
>
> Best regards
> Stan
--
Arindam Haldar
Systems & Network
Digital 2 Virtual ISP Pvt Ltd.
Vadodara, Gujarat INDIA
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2002-01-27 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-27 9:53 Subject: [LARTC] Mini-ISP-like bandwidth limiter Arindam Haldar
2002-01-27 12:46 ` Gunther Stammwitz [this message]
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=marc-lartc-101213557518447@msgid-missing \
--to=gstammw@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.