Mark Wright writes:
> sj# ngctl mkpeer lmc0: frame_relay rawdata downstream
> sj# ngctl mkpeer lmc0:rawdata lmi dlci0 auto0
> sj# ngctl mkpeer lmc0:rawdata rfc1490 dlci15 downstream
> ngctl: send msg: No such file or directory
>
> What does that mean? Should I be concerned that ifconfig -a doesn't reveal
> the lmc0? Or does it show up only after I do a 'ngctl interface'? It shows
> up in dmesg:
>
> lmc0: <Lan Media Coporation T1> port 0xf880-0xf8ff mem 0xffbefc00-0xffbefc7f
> irq 11 at device 16.0 on pci0
> lmc0: pass 2.2, serial 00:60:99:00:23:6d
> lmc0: driver is using old-style compatability shims
>
> I'm using the 20001210 snapshot, and the following changes were made to my
> kernel config:
>
> options NETGRAPH #enable netgraph networking
> options NETGRAPH_SOCKET #enable netgraph networking
> options NETGRAPH_FRAME_RELAY #enable frame relay
> options NETGRAPH_LMI #enable link management
> ...
> device lmc # LanMedia card
How about NETGRAPH_RFC1490?
Use "kldstat -v | grep ng_" to see if you have all the necessary
netgraph types (though it should load them automatically.. but then
maybe the KLD file can't be found).
-Archie
__________________________________________________________________________
Archie Cobbs * Packet Design * http://www.packetdesign.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
