Gigabit Linux Routers

I have posted thos off-list, for the list:
http://www.lannerinc.com/DM/FW-7550_DM.pdf
pros: cheap, cf-disk support, low power (~50W)

cf-disk support is pretty easy to add to lots of things. With the advent
of 4GB compact flash modules and CF-to-IDE adapters, it is not too hard
to avoid rotating media...

OS:
Freebsd:
pros: very stable, quagge runs very well, fastforwarding support,

quagga OSPF needs a patch on FreeBSD 7, else it will decimate your OSPF
environment.

   simple traffic shaping, interrupt less polling supported

Several different traffic shaping strategies are available, and I think
all of them go far beyond "simple".

cons: only 1 route for each network, vrrp failover is not easy to
   implement with quagga and ospf, no multipath routing

carp seems easy to implement, even with quagga and ospf. At least, it's
set up on a lab setup here and everything appears to work as expected.

... JG

Dear Joe,

Several different traffic shaping strategies are available, and I think
all of them go far beyond "simple".

ipfw 100 add pipe 1 all from 192.168.0.0/24 to any xmit vlan1
ipfw pipe 1 config bw 95Mbit/s queue 200Kbytes

thats simple.

cons: only 1 route for each network, vrrp failover is not easy to
   implement with quagga and ospf, no multipath routing

carp seems easy to implement, even with quagga and ospf. At least, it's
set up on a lab setup here and everything appears to work as expected.

example setup:

A----(ospf)---B
\ /
  \ /
   \ /
    \ /
     \ /
      lan1

A and B share 1 virtual ip for lan1 (192.168.0.1/24).
problems:
*) only 1 ip-net supported (no aliases)
*) carp is i bound, carp-dev line openbsd is in development
   (not shure if already stable)
*) if carp switch over:
   t=0: A is master, has route 192.168.0.1/24
        B has route 192.168.0.1/24 via ospf
   t=1: A goes down, route disappear (need linkstate in ospf)
   t=2: B carp takes over 192.168.0.1/24
     B can not add 192.168.0.1/24 route as it is still
     known via ospf
   t=3: B gets update to remove route 192.168.0.1/24 via ospf
   t=4: 192.168.0.1/24 route has disappeared, failover broken.

with ucarp, some special scripts and source code changed I was able
to handle this situation, but not with carp and ospf (at least at
freebsd 6.3)

Kind regards,
   Ingo Flaschberger