mike wrote:
> prg wrote:
> > Personally, I don't like running the Linux stack as a bridge --
just
> > can't get over the willies of having the nics in promisc mode.
Just a
> > personal foible and not recommended as advice.
>
> Why you say that? i've seen many linux bridges running without
troubles
> for years.
As I said, just my personal feeling, not advice to anyone else. A nic
running full time in promiscuous mode is just too juicy a target for
someone sniffing packets.
> > Then I have the good fortune of having a few extra Ciscos around at
> > work to cope in the short run and $ to provide a long term
solution.
>
> Heh, i don't have money to afford a Cisco just for my interests.
My attitude is "easy" to live with since someone else is paying for the
switches;-)
> > I think you should be able to get what you need. Easy as flipping
a
> > light switch? Doubt it.
>
> Naww, i don't want a plug'n'play thing that does all for me.
> I want only examples to make my own script, but before that i wanted
to
> be sure that tc worked ok on a bridge.
It's been some time -- 2.4.14 kernel? -- since I played with the
bridging code, but it worked OK then. So far as I know, it still
works, but scripts and iptables rules may have to be brought up to date
for 2.6+ kernels. Should not be anything difficult or non-obvious.
IIRC, some of the "shaping" queues (IM?) never worked with bridge + tc
and one or two other approaches need a slight modification, I think.
The script should get you far down the road to success -- maybe a tweak
or two.
have fun

prg
email above disabled