Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Mar 2001 07:42:39 +0100
From:      Udo Erdelhoff <ue@nathan.ruhr.de>
To:        freebsd-net <freebsd-net@freebsd.org>
Cc:        Murray Taylor <mtaylor@bytecraft.com.au>, "'freebsd-hackers@freebsd.org'" <freebsd-hackers@freebsd.org>
Subject:   Re: Netgraph error message
Message-ID:  <20010316074239.R83336@nathan.ruhr.de>
In-Reply-To: <710709BB8B02D311942E00606744181054429B@MELEXC01>; from mtaylor@bytecraft.com.au on Fri, Mar 16, 2001 at 11:39:10AM %2B1100
References:  <710709BB8B02D311942E00606744181054429B@MELEXC01>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 16, 2001 at 11:39:10AM +1100, Murray Taylor wrote:
> I get the following messages when I fire up ngctl
> 
> module_register: module netgraph already exists
> linker_file_sysinit: "netgraph.ko" failed to register 17
> 
> I am using 4.3-BETA as at 13/mar
> and have options NETGRAPH in my kernel config
> 
> I am using the ngctl command to configure a frame relay system

I assume that you are also using the netgraph nodes for frame relay.  In
that case, the error messages are probably mostly harmless. I've had
similar messages when I tried to use mpd-netgraph on a box that had
options NETGRAPH/NETGRAPH_ETHER/NETGRAPH_SOCKET/NETGRAPH_PPPOE in
the kernel config.

As far as I understand it, you have to use an all-or-nothing approach when
it comes to netgraph. If you do not include any netgraph modules in your
kernel, the system will load your modules and everything is fine.  If you
include all neccessary modules into the kernel, things will work as well.
Things start to go downhill if some of the modules have been included in
the kernel and some others have to be loaded. The system gets the
information that the module NETGRAPH_FOO depends on NETGRAPH. The system
ignores that netgraph.ko is already present in the kernel and will try to
load the module. It's no big surprise that the operation fails.

I managed to work around the problem by loading the additional modules
manually (kldload ng_foo;kldload ng_bar;...). The correct fix is to include
all neccessary modules in your kernel. Use a second shell while you are
running ngctl and run kldstat.  If you see any netgraph modules in the
output, add them to your kernel config.

NOTE: This was on a 4.1-stable system, things may have changed since then.

/s/Udo
-- 
"I don't want to run a company. I'm not good at managing people.
You have a problem with the guy in the next cubicle?
I don't care. Shoot him or something."
-- Marc Andreesen, founder of Netscape, Rolling Stone, May 97

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010316074239.R83336>