Can u attach ur Rules file..
thanks
pramod
___
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Dropping of packets on the receive side can be done bu IPTABLES..
thanks
pramod
Alexander Sirotkin wrote:
It appears that while Linux has plenty of traffic shaping mechanism on
transmit, there is nothing on receive side.
While generally it does make sense since transmit is more CPU
intensive
That sounds like an overly complicated way to do it. I would just
create a 512kbit class with subclasses for the internet traffic, and
route all MAN traffic into a 100mbit class. Should be some way to know
which ip's will go to the MAN. Creating a virtual interface makes little
sense here, si
Hi there...
I have an idea for you, just don't ask me how to implement it.
1. bring up some virtual interface, I'm almost sure linux has some way of
doing it. this interface should output data to your real interface.
2. try to route all MAN traffic trough this interface. you'll need to know the
ok i read everythong and now understand much more.. the problem is that my boss
told me to erase whole running server, because he wants to run tests on
hardware with windows... (i work with idiot).
he is so stubborn that he does not understand that this is qdisc issue.
my idea is :
On Thu, 14 Jul 2005 17:24:00 +0200 Peter Surda <[EMAIL PROTECTED]> wrote:
>If you don't want to adapt, once upon a time I wrote a management tool for an
>ISP with requirements similar to yours. Although I tuned it for performance and
>it seems to work well, as far as I know there are only a couple
It appears that while Linux has plenty of traffic shaping mechanism on
transmit, there is nothing on receive side.
While generally it does make sense since transmit is more CPU intensive
operation, after all receive also
consumes CPU cycles. It is clear that it's best to drop the packet as
soon
On Thu, 14 Jul 2005 10:14:37 -0300 Alvaro Motta <[EMAIL PROTECTED]> wrote:
>Hi folks.
Hi,
>This message may be a bit verbose and not as techie as the ones I've
>seen in this list, but describing the scenario will save a lot of
>messages.
>Problem: bbsm never performed as expected. It freezes, di
> Scenario:
>
> A building with 17 floors, each floor with 24 offices (totals 408
> offices) connected to the backbone through a border switch (1 vlan for
> each office). The offices can lease bandwidth of 64k, 128k, 256k,
> 512k, 1M and 2Mbps, according to their needs. We have 3 links to the
> in
Hi folks.
This message may be a bit verbose and not as techie as the ones I've
seen in this list, but describing the scenario will save a lot of
messages.
Scenario:
A building with 17 floors, each floor with 24 offices (totals 408
offices) connected to the backbone through a border switch (1 vla
10 matches
Mail list logo
