Date: Thu, 31 Mar 2005 01:52:06 +0400 From: Roman Kurakin <rik@cronyx.ru> To: John Mok <jmok@attglobal.net> Cc: Julian Elischer <julian@elischer.org> Subject: Re: HOWTO connect MCI using Netgraph + Frame Relay with Digi SYNC/570i Message-ID: <424B1F86.2040407@cronyx.ru> In-Reply-To: <42497803.40904@attglobal.net> References: <42344AF7.6070701@attglobal.net> <423C72A1.7060000@cronyx.ru> <4240497D.5030304@attglobal.net> <42404B15.5040605@elischer.org> <424835C0.9070603@attglobal.net> <42485836.6030203@elischer.org> <424898E3.8080007@attglobal.net> <4248A5BB.3040508@elischer.org> <42497803.40904@attglobal.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, John Mok: > Dear Julian, > > I have re-compiled the kernel with NETGRAPH_ETHER and NETGRAPH_IFACE. > I failed to create the lmi node :- > > #ngctl mkpeer sync_ar0: frame_relay rawdata downstream > #ngctl name sync_ar0:rawdata fr-mux > #ngctl mkpeer fr-mux: lmi dlci0 ansi Why 'ansi'? It should be 'annexD'. annexD means ANSI T1.617 AnnexD (1994) In fact, I dont know if anyone support version of year 1991 now. rik > > ngctl: send msg: Invalid arguments > > Command "ngctl types" returns :- > > There are 7 total types: > Type name Number of living nodes > --------- ---------------------- > socket 1 > frame_relay 1 > ether 3 > rfc1490 0 > lmi 0 > iface 0 > sync_ar 2 > > Command "ngctl show fr-mux:" returns :- > > Name: fr-mux Type: frame_relay ID: 00000007 Num hooks: 1 > Local hook Peer name Peer type Peer ID Peer > hook ---------- --------- --------- ------- > --------- downstream sync_ar0 sync_ar > 00000001 rawdata > > Except the brief description on manpage, please help to advise where I > could find the detailed documentation (e.g. user guides or admin > guides etc.) about what node types and hooks are available in netgraph. > > Thank you very much. > > John Mok > > > Julian Elischer wrote: > >> >> >> John Mok wrote: >> >>> >>> The command "ngctl types" shows :- >>> >>> There are 5 total types: >>> Type name Number of living nodes >>> --------- ---------------------- >>> socket 1 >>> rfc1490 0 >>> lmi 0 >>> frame_relay 0 >>> sync_ar 2 >>> >>> What other modules are needed? How to add them, whether load them >>> dynamically or compiled into kernel? >>> >>> Thanks a lot. >> >> >> >> >> kldload ng_iface at least >> >> it should be loaded automatically if you add the line shown below.. >> >> >>> >>> John Mok >>> >>> >>> Julian Elischer wrote: >>> >>>> what does >>>> "ngctl types" >>>> say? >>>> >>>> looks like you don't have all the right modules loaded.. >>>> >>>> >>>> John Mok wrote: >>>> >>>>> >>>>> After issuing the following commands :- >>>>> >>>>> #ngctl mkpeer sync_ar0: frame_relay rawdata downstream >>>> >>>> >>>> >> >> ngctl name sync_ar0:rawdata fr-mux >> >> replace the next line with.. >> #ngctl mkpeer fr-mux: lmi dlci0 ansi >> >> and add: >> ngctl name fr-mux:dlci0 lmi >> >>>>> #ngctl mkpeer sync_ar0:rawdata rfc1490 dlci16 rfc1490 >>>> >>>> >>>> >> this could be replaved by: >> ngctl mkpeer fr-mux: rfc1490 dlci16 downstream >> >> >>>>> #ngctl mkpeer sync_ar0:rawdata dlci16 rl0 inet inet >>>> >>>> >>>> >> this line is totally confused.. >> >> should be: >> ngctl name fr-mux:dlci16 protomux >> ngctl mkpeer protomux: iface inet inet >> >> now you can add the ip addresses.. >> >> sorry I didn't read it better several days ago.. >> >> >>>>> >>>>> #ifconfig ng0 1.2.3.4 5.6.7.8 >>>>> ifconfig: interface ng0 does not exist >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> are you SURE none of these returned an error? >>>> >>>>> >>>>> The command ifconfig shows :- >>>>> >>>>> rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 >>>>> options=8<VLAN_MTU> >>>>> inet6 fe80::207:40ff:fe09:f09%rl0 prefixlen 64 scopeid 0x1 >>>>> inet 192.168.255.254 netmask 0xffffff00 broadcast 192.168.255.255 >>>>> ether 00:07:40:09:0f:09 >>>>> media: Ethernet autoselect (none) >>>>> status: no carrier >>>>> xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 >>>>> options=9<RXCSUM,VLAN_MTU> >>>>> inet6 fe80::201:3ff:fec1:9c58%xl0 prefixlen 64 scopeid 0x2 >>>>> ether 00:01:03:c1:9c:58 >>>>> media: Ethernet autoselect (100baseTX <full-duplex>) >>>>> status: active >>>>> xl1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 >>>>> options=9<RXCSUM,VLAN_MTU> >>>>> inet6 fe80::201:3ff:fe34:61af%xl1 prefixlen 64 scopeid 0x3 >>>>> inet 192.168.16.254 netmask 0xffffff00 broadcast 192.168.16.255 >>>>> ether 00:01:03:34:61:af >>>>> media: Ethernet autoselect (100baseTX <full-duplex>) >>>>> status: active >>>>> plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500 >>>>> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 >>>>> inet6 ::1 prefixlen 128 >>>>> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 >>>>> inet 127.0.0.1 netmask 0xff000000 >>>>> >>>>> and the command "ngctl list" shows :- >>>>> >>>>> There are 4 total nodes: >>>>> Name: ngctl811 Type: socket ID: 00000011 Num >>>>> hooks: 0 >>>>> Name: <unnamed> Type: frame_relay ID: 00000004 Num >>>>> hooks: 1 >>>>> Name: sync_ar1 Type: sync_ar ID: 00000002 Num >>>>> hooks: 0 >>>>> Name: sync_ar0 Type: sync_ar ID: 00000001 Num >>>>> hooks: 1 >>>>> >>>>> Would it be the problem that I test it with cable disconnected >>>>> from the modem (i.e.CSU/DSU)? >>>>> >>>>> Thanks a lot. >>>>> >>>>> John Mok >>>>> >>>>> >>>>> Julian Elischer wrote: >>>>> >>>>>> did the last command do anything? >>>>>> >>>>>> please show the output of: >>>>>> ifconfig >>>>>> ngctl list >>>>>> >>>>>> >>>> >> > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?424B1F86.2040407>