* [LARTC] flow classification
@ 2003-11-10 15:54 Ciprian Niculescu
2003-11-10 23:59 ` Damion de Soto
2003-11-11 11:09 ` Ciprian Niculescu
0 siblings, 2 replies; 3+ messages in thread
From: Ciprian Niculescu @ 2003-11-10 15:54 UTC (permalink / raw)
To: lartc
hello,
i have 2 links to the ISP of 128kbit each, and i want to balance the
trafic between them, but not staticly (local ip1-5 throw isp1, and the
rest to isp2). I though at a ingress clasification, then routing by the
mark, and at the exit nat (yes i must do nat :(((, but the clasification
must be flow based, and i dont know how to do it.
C
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [LARTC] flow classification
2003-11-10 15:54 [LARTC] flow classification Ciprian Niculescu
@ 2003-11-10 23:59 ` Damion de Soto
2003-11-11 11:09 ` Ciprian Niculescu
1 sibling, 0 replies; 3+ messages in thread
From: Damion de Soto @ 2003-11-10 23:59 UTC (permalink / raw)
To: lartc
> i have 2 links to the ISP of 128kbit each, and i want to balance the
> trafic between them, but not staticly (local ip1-5 throw isp1, and the
> rest to isp2). I though at a ingress clasification, then routing by the
> mark, and at the exit nat (yes i must do nat :(((, but the clasification
> must be flow based, and i dont know how to do it.
If certain IPs are always going through the same link, then you don't really want
load balancing at all.
Don't you just want routing rules that say local ip1-5 always go through one gateway
(isp1), and the default route is isp2 for everyone else?
Or did I misunderstand?
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Damion de Soto - Software Engineer email: damion@snapgear.com
SnapGear --- ph: +61 7 3435 2809
| Custom Embedded Solutions fax: +61 7 3891 3630
| and Security Appliances web: http://www.snapgear.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--- Free Embedded Linux Distro at http://www.snapgear.org ---
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [LARTC] flow classification
2003-11-10 15:54 [LARTC] flow classification Ciprian Niculescu
2003-11-10 23:59 ` Damion de Soto
@ 2003-11-11 11:09 ` Ciprian Niculescu
1 sibling, 0 replies; 3+ messages in thread
From: Ciprian Niculescu @ 2003-11-11 11:09 UTC (permalink / raw)
To: lartc
On Tue, 11 Nov 2003 09:59:18 +1000, "Damion de Soto"
<damion@snapgear.com> said:
> > i have 2 links to the ISP of 128kbit each, and i want to balance the
> > trafic between them, but not staticly (local ip1-5 throw isp1, and the
> > rest to isp2). I though at a ingress clasification, then routing by the
> > mark, and at the exit nat (yes i must do nat :(((, but the clasification
> > must be flow based, and i dont know how to do it.
>
> If certain IPs are always going through the same link, then you don't
> really want
> load balancing at all.
> Don't you just want routing rules that say local ip1-5 always go through
> one gateway
> (isp1), and the default route is isp2 for everyone else?
>
> Or did I misunderstand?
yes, you did, the 2 links are "practicaly" at the same isp, and i will
gain nothing if i do shortest_path routing
C
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-11-11 11:09 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-11-10 15:54 [LARTC] flow classification Ciprian Niculescu
2003-11-10 23:59 ` Damion de Soto
2003-11-11 11:09 ` Ciprian Niculescu
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.