From owner-freebsd-net Sat Mar 17 23:37:50 2001 Delivered-To: freebsd-net@freebsd.org Received: from online.tmx.com.au (online.tmx.com.au [192.150.129.1]) by hub.freebsd.org (Postfix) with ESMTP id 6CC6537B723 for ; Sat, 17 Mar 2001 23:37:45 -0800 (PST) (envelope-from mtaylor@bytecraft.com.au) Received: from melexc01.bytecraft.com.au ([203.9.250.249]) by online.tmx.com.au (8.9.3/8.8.8) with ESMTP id SAA08504 for Sun, 18 Mar 2001 18:37:35 +1100 (EST) Received: by MELEXC01 with Internet Mail Service (5.5.2448.0) id ; Sun, 18 Mar 2001 18:39:09 +1100 Message-ID: <710709BB8B02D311942E00606744181054429C@MELEXC01> From: Murray Taylor To: "'freebsd-net'" Subject: RE: Netgraph error message Date: Sun, 18 Mar 2001 18:38:11 +1100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org No it hasn't changed in 4.3-BETA ... I have added options NETGRAPH_FRAME_RELAY options NETGRAPH_LMI options NETGRAPH_SOCKET options NETGRAPH_RFC1490 options NETGRAPH_IFACE to my config and all is silent ... cheers mjt > -----Original Message----- > From: Udo Erdelhoff [SMTP:ue@nathan.ruhr.de] > Sent: Friday, 16 March 2001 17:43 > To: freebsd-net > Cc: Murray Taylor; 'freebsd-hackers@freebsd.org' > Subject: Re: Netgraph error message > > 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