All of lore.kernel.org
 help / color / mirror / Atom feed
From: "M.F. PSIkappa" <psi@platon.atlantis.sk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: Iproute2 in FreebSD
Date: Thu, 04 Oct 2001 16:38:33 +0000	[thread overview]
Message-ID: <marc-lartc-100221354103755@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100219996108715@msgid-missing>

Hello,
you don't need IPROUTE2 on FreeBSD, you can use ipfw. Ipfw has less bugs
and more documentation as IPROUTE2 but ipfw has less features than
IPROUT2+iptables. 
With ipfw you can make:
- multirouting
- firewalling
- traffic shaping
Everything with 1 tool and 1 syntax.
But!
Traffic shaping with ipfw is very poor better is ALTQ but best is linux tc
(without bugs ;)
Multirouting with ipfw has other philosophy there is no multiple tables...

PSIkappa
psi@atlantis.sk

On Thu, 4 Oct 2001, bert hubert wrote:

> On Wed, Oct 03, 2001 at 08:16:47PM +0330, Mohsen Nourany wrote:
> > Hello
> > How can I Install IPROUTE2 in FreeBSD?
> > and in your opinion, is LINUX better or FREEBSD , for multirouting ?
> 
> Even my BSD friends tell me Linux is currently better with iproute2 &
> iptables.
> 
> -- 
> http://www.PowerDNS.com          Versatile DNS Software & Services
> Trilab                                 The Technology People
> Netherlabs BV / Rent-a-Nerd.nl           - Nerd Available -
> 'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet


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

      reply	other threads:[~2001-10-04 16:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-04 12:52 [LARTC] Re: Iproute2 in FreebSD bert hubert
2001-10-04 16:38 ` M.F. PSIkappa [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=marc-lartc-100221354103755@msgid-missing \
    --to=psi@platon.atlantis.sk \
    --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.