From: "William L. Thomson Jr." <wlt@obsidian-studios.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Load-banancing. two ip's from one isp - solution
Date: Wed, 29 Mar 2006 19:47:25 +0000 [thread overview]
Message-ID: <1143661646.7359.4.camel@wlt.obsidian-studios.com> (raw)
In-Reply-To: <20060328013941.CB4311B58DB@poczta.interia.pl>
On Wed, 2006-03-29 at 21:32 +0200, Szymon Mroofka wrote:
>
> I'll patch when I'll upgrading kernel or if there will be such need maby very
> soon. For now I'm tired of compiling and instaling new kernel it takes too
> long on my old and slow box ;).
Yeah been there and done that. So long as you do not run into issues.
The patches should cause no harm being in place. If anything could help
out in some scenarios.
>
> Yes... no nat needed.
That was just part of how Julians patches fixed things to work? But if
it's not needed or does not apply in your case. Then great.
>
> My box is only used as a desktop so I don't need to care about any errors,
> this will not couse any problem like in big networks or companys where people
> need to have access to the internet all the time.
Yeah I was load balancing two SDSL lines for my servers. So it was
critical I resolved any bugs, or minor issues. As it could work fine for
a while, till a cache got flushed or etc. Then all hell would break
lose.
> I thing I've done it by in my script:
> ip route append prohibit default table wew metric 1 proto static
> ip route append prohibit default table zew metric 1 proto static
Just a safety net in case the default cant be reached. Ideally it was
routed already per the preceding rule. If that does not happy, safety
net. So you do not have to wait for a time out or etc.
> I'm using iptables to mark packets for htb so it should be easy to add few new
> rules and use it in routing... I hope it will be.... but I'm afraid that
> becouse of I can't use PRERUTING chain (only local packets OUTPUT chain)
> there may be some problems with it.... I'll check it soon.
Ah shaping and etc. On my list, just don't want to go limiting a service
unnecessarily. One of these days :) Then again I said that years ago and
it never happened :)
--
Sincerely,
William L. Thomson Jr.
Obsidian-Studios, Inc.
http://www.obsidian-studios.com
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-03-29 19:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 1:39 [LARTC] Load-banancing. two ip's from one isp sAwAr
2006-03-28 3:26 ` William L. Thomson Jr.
2006-03-28 9:27 ` sAwAr
2006-03-28 14:16 ` William L. Thomson Jr.
2006-03-28 14:59 ` Kirk Reiser
2006-03-28 15:10 ` William L. Thomson Jr.
2006-03-28 15:53 ` William L. Thomson Jr.
2006-03-28 16:58 ` sAwAr
2006-03-28 17:06 ` William L. Thomson Jr.
2006-03-28 17:55 ` sAwAr
2006-03-28 18:56 ` William L. Thomson Jr.
2006-03-28 19:37 ` sAwAr
2006-03-29 1:11 ` sAwAr
2006-03-29 4:08 ` William L. Thomson Jr.
2006-03-29 17:12 ` [LARTC] Load-banancing. two ip's from one isp - solution sAwAr
2006-03-29 18:18 ` William L. Thomson Jr.
2006-03-29 19:32 ` Szymon Mroofka
2006-03-29 19:47 ` William L. Thomson Jr. [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=1143661646.7359.4.camel@wlt.obsidian-studios.com \
--to=wlt@obsidian-studios.com \
--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.