Re: Feature requests / inquiries.

From: Brooks Davis (brooks_at_one-eyed-alien.net)
Date: 08/29/05

  • Next message: Max Laier: "Re: Feature requests / inquiries."
    Date: Mon, 29 Aug 2005 10:50:29 -0700
    To: Bart Van Kerckhove <bart@it-ss.be>
    
    
    

    On Mon, Aug 29, 2005 at 05:56:25PM +0200, Bart Van Kerckhove wrote:
    > Dear Sirs / Fellow Freebsd Freaks,
    >
    > I've been using FreeBSD for a while now as a routing/firewalling platform,
    > but recent developments in our network infrastructure confront me with some
    > lack of features in the IPstack.
    > In a nutshell, i'm looking for support for (in order of importance to me) :
    > (r)STP, ECMP, and LACP.
    >
    > For STP, i have found a patch that contained a port from netbsd code of
    > if_bridge ; but i'm way too insecure about running this on a production
    > system.
    > For ECMP, the only thing i found out was that there used to be a patchset
    > that did something like it, but went defunct after 4.8.
    > LACP: no idea at all, sorry :)
    >
    > As these are features we'll be using some time soon now, i can say we _need_
    > them. I have even seriously considered moving to NetBSD; the lack of NIC
    > polling support for the intel chipsets i'm using is holding me back at the
    > moment.
    > I do not want to move over to linux, for various reasons.
    > So I figured perhaps some of the freebsd community is also interested in
    > these features, and I might as well sponsor (part of?) its development.
    > Are there any persons interested in developing these features, or do they
    > already exist and am I just plain ignorant (forgive me if that is the case).
    > Please note that i'm not interested in the netgraph approach, as that's
    > (imho) just a hack around it, and it's not functioning with for example
    > gnu/zebra et all.
    >
    > I am looking for short- and long-term solutions, anything that's developed
    > trough sponsoring i'd be happy to contribute to the main tree.
    > As this would be the first time we actually ask for a specific feature in
    > any OSS software, I could be way off the scale with the figures i had in
    > mind. This would be about 200 to 400 euro per feature, the more important
    > ones like STP and ECMP are totally open to discussion.
    >
    > Any takers? Any enlightenment? Thanks for helping out in advance ;)

    if_bridge has been imported into FreeBSD 6.0 and I believe will be
    merged to 5.x before 5.5.

    I can't speak for ECMP.

    LACP is supported by ng_fec. The fact that you don't like it is a
    seperate issue. FWIW, ng_fec only uses netgraph for configuration.
    It's not really a netgraph node. I'd personally like to see OpenBSD's
    if_trunk imported and LACP added, but I certainly don't have time.

    -- Brooks

    -- 
    Any statement of the form "X is the one, true Y" is FALSE.
    PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4
    
    



  • Next message: Max Laier: "Re: Feature requests / inquiries."

    Relevant Pages

    • Re: Feature requests / inquiries.
      ... > Dear Sirs / Fellow Freebsd Freaks, ... > STP, ECMP, and LACP. ... > these features, and I might as well sponsor its development. ... ng_fec only uses netgraph for configuration. ...
      (freebsd-hackers)
    • Feature requests / inquiries.
      ... I've been using FreeBSD for a while now as a routing/firewalling platform, ... For ECMP, the only thing i found out was that there used to be a patchset ... As these are features we'll be using some time soon now, ... trough sponsoring i'd be happy to contribute to the main tree. ...
      (freebsd-hackers)
    • Feature requests / inquiries.
      ... I've been using FreeBSD for a while now as a routing/firewalling platform, ... For ECMP, the only thing i found out was that there used to be a patchset ... As these are features we'll be using some time soon now, ... trough sponsoring i'd be happy to contribute to the main tree. ...
      (freebsd-net)
    • Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3
      ... This whole discussion is really interesting as it clearly showcases two common trends in computing (rapid development vs stability) On the one side we got people who are more interested in development than stabilization of the existing code base. ... They really do not care about "new features", but they do care about maximum stability of the existing code, security, and nonstop business continuity even in the face of natural disasters. ... There are definitely points of conflict along these lines, but much of the time the reason that people use FreeBSD is precisely because there *is* agreement on these points. ... If FreeBSD developers only hung around to do adventurous new feature development, we wouldn't have -STABLE branches, errata/security branches, freebsd-update, and so on. ...
      (freebsd-stable)
    • Re[2]: FreeBSD and i386 VM hardware
      ... the Intel microprocessors provide some very elaborate features ... MD>:for management of virtual memory, I/O operations, and security, allowing total ... How much of this is used by FreeBSD? ... MD> use most of the major MMU/VM features of the processor. ...
      (FreeBSD-Security)