All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Routing/forwarding/shaping problems in v2.2.x (Long -
Date: Thu, 20 Mar 2003 12:59:30 +0000	[thread overview]
Message-ID: <marc-lartc-104816525504119@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104816249501359@msgid-missing>


	Hello,

On Thu, 20 Mar 2003, Gordan Bobic wrote:

> The setup:
>
> "Home brewed" v2.2.24 (will patch to v2.2.25 later today) with the DS8 patch
> applied. Currently downloading the DS9/rbtree/htb3 patches to be applied
> later (obviously, unpatching the old DS8 first), and see if at least some of
> my problems go away.

	Yes, DS-8 has many problems including security ones.
The only problem is that I still didn't upgraded the patches to
2.2.25, may be in the next days I'll find time to do so.

> Multiple cable/DSL lines with multiple default routes and equal cost
> multipath.

	I strongly recommend the route patches in such case:

http://www.ssi.bg/~ja/#routes-2.2
http://www.ssi.bg/~ja/routes-2.2.20-7.diff

> When applying ingres shaping (policing filter) all executes fine without
> reporting any errors, but
>
> tc -s -d qdisc show dev eth1
> and
> tc -s -d filter show dev eth1

	DS9 has fixes for the ingress stats

> Can anyone hazard a guess as to why this is not doing what it should be? Is
> this a know bug in DS8 and DS9 will fix it? I will try it anyway, just to
> make sure, but some encouraging news would be nice. :-)

	Yes, yes, I'll add it to the changelog

> 2) ipmasqadm portfw unstable/unreliable
>
> I have tried to use this approach to forward ports from the firewall to an
> internal server. It works OK initially, but within minutes, things start
> going wrong. Some connections get through on one interface but not the other.
> Later, connections from the same host will work on a different interface, but
> not the one it worked on initially.

	Such problems should be solved from the "routes" patches,
they will keep each traffic through its ISP.

	Read nano.txt from http://www.ssi.bg/~ja/#routes
It is for 2.4 but the concept and the routing rules are same.

> TIA.
>
> Gordan

Regards

--
Julian Anastasov <ja@ssi.bg>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2003-03-20 12:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 12:09 [LARTC] Routing/forwarding/shaping problems in v2.2.x (Long - sorry) Gordan Bobic
2003-03-20 12:59 ` Julian Anastasov [this message]
2003-03-20 13:38 ` Gordan Bobic
2003-03-20 23:25 ` [LARTC] Routing/forwarding/shaping problems in v2.2.x (Long - Julian Anastasov

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-104816525504119@msgid-missing \
    --to=ja@ssi.bg \
    --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.