Re: Creating Multiple Discard Interfaces

From: Brooks Davis (brooks_at_one-eyed-alien.net)
Date: 03/10/05

  • Next message: Charlie Schluting: "Re: tcpdump/bpf and seeing .1q tags" 
    Date: Wed, 9 Mar 2005 17:22:43 -0800
To: José María González <chema@cs.berkeley.edu>

    On Wed, Mar 09, 2005 at 04:18:25PM -0800, José María González wrote:
    > Hi,
    >
    > I'm trying to create several discard interfaces on 4.9-RELEASE, and I'm
    > having 2 problems. This is what I see (comments started by //):
    >
    > # ifconfig -a
    > de0: ...
    > lo0: ...
    > // these are my original interfaces
    >
    > # kldload if_disc
    >
    > # ifconfig -a
    > de0: ...
    > lo0: ...
    > ds0: flags=8008<LOOPBACK,MULTICAST> mtu 65532
    > // surprisingly enough, just loading the if_disc kernel module creates
    > // the ds0 interface for me. Well, I can live with that.
    >
    > # ifconfig ds0 create
    > ifconfig: SIOCIFCREATE: Invalid argument
    > # ifconfig disc0 create
    > ifconfig: SIOCIFCREATE: Invalid argument
    > // This makes sens, as the ds0 interface is already created
    >
    > # ifconfig ds1 create
    > ifconfig: SIOCIFCREATE: Invalid argument
    > # ifconfig disc1 create
    > ifconfig: SIOCIFCREATE: Invalid argument
    > // 1st problem: How do I create ds1, ds2, etc.?
    >
    >
    > // Now I want to get rid of the if_disc module
    > # ifconfig ds0 down
    > # ifconfig ds0 destroy
    > ifconfig: SIOCIFDESTROY: Invalid argument
    > #ifconfig disc0 destroy
    > ifconfig: interface disc0 does not exist
    > # kldunload -v -i 4
    > Unloading if_disc.ko, id=4
    > kldunload: can't unload file: Invalid argument
    > // 2nd problem: How do I get rid of the if_disc module?

    The discard module is not unloadable or clonable before 5.0. You need
    to upgrade to 5.3+ or statically compile in the discard device with an
    appropriate count.

    -- 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: Charlie Schluting: "Re: tcpdump/bpf and seeing .1q tags"