On 01/19/07 12:45, Manish Kathuria wrote:
My experience has been mixed. The patch worked very well in many cases
but in some it worked only if the first hop gateway was down and not
any of the subsequent hops. So as you mentioned its happening since it
can ping the switch / modem, it thinks the l
You should propably try:
tc qdisc add dev eth0 root handle 1: htb default 20
and not 30 cause your default class is 20 no?
On 1/20/07, Simone84bo <[EMAIL PROTECTED]> wrote:
Hi to all
I am studying HTB on LARTC how to. I realize a simple configuration on
router:
tc qdisc add dev eth0 root handle
Hi to all
I am studying HTB on LARTC how to. I realize a simple configuration on
router:
tc qdisc add dev eth0 root handle 1: htb default 30
tc class add dev eth0 parent 1: classid 1:1 htb rate 3mbit burst 15k
tc class add dev eth0 parent 1:1 classid 1:10 htb rate 2mbit burst 15k
tc class add dev e
On 1/19/07, Tom Lobato <[EMAIL PROTECTED]> wrote:
Hello all!
I applied http://www.ssi.bg/~ja/routes-2.6.8-10.diff patch to kernel
2.6.8.1 and it works fine, or almost fine. It does the load balancing
well, but when one link is dropped it continues to try it.
At the end of http://www.ssi.bg
On Fri, 19 Jan 2007 12:37:54 -0300, Luciano Ruete wrote
> Equalize is a patch for 2.4, it never get's mainline, and there is
> no 2.6 version AFAIK.The iproute option is there, but without the
> patch does nothing.
Interesting. I used vanilla 2.4 and didn't need equalize patch.
Are you sure equali
On Friday 19 January 2007 08:13, hhoxha wrote:
> Hi
> Everybody in the list
>
> I have a situation like this
>
> --(IP1)
> linux |eth0.40-- |
> router || |
> box| (IP2)|--|Client Router ( Destiantion Net DNET)
>
>|eth0.41
Thanks Marco.
Very useful your reply.
Roberto
2007/1/18, Marco Aurelio <[EMAIL PROTECTED]>:
This is not possible because ipp2p does not match every p2p packet but only
some essential signaling packets. By filtering these packets, the p2p client
cannot estabilish connections to transfer data,
Hi
Everybody in the list
I have a situation like this
--(IP1)
linux |eth0.40-- |
router | | |
box| (IP2)|--|Client Router ( Destiantion Net DNET)
|eth0.41-- | |/27 subnet
--
I just
POSTROUTING chain of which table?
NAT should not affect things, as long as - as you say - both directions
are going through the box.
It sounds like you are "not sure" if it's working.
Use connmark target too to save the mark in the conntrack and look in
/proc/net/ip_conntrack
Also use iptables -vn
Cheers Andy,
That clarifies;-)
Regards,
-nik
Andy Furniss wrote:
Nikolay Kichukov wrote:
Hello Andy,
How do one create such a filter to catch arp/other link layer traffic?
Can
you give us one such example?
A quick test on ingress
#tc qdisc add dev eth0 ingress
Classify all ip traffic
#t
10 matches
Mail list logo