Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 18 Jul 2000 17:44:37 +0400
From:      "Vladimir N. Kovalev" <smith@scn.ru>
To:        freebsd-net@freebsd.org
Subject:   TAU-PCI-E1 and NETGRAPH Frame Relay
Message-ID:  <39745F45.D441D899@scn.ru>

next in thread | raw e-mail | index | archive | help
Hello !
During a one week ago I'm trying to install syncronous E1 card from Cronyx
Engineering (www.cronyx.ru) Tau-PCI-E1 into my FreeBSD 4.0-STABLE server and
connect it to IPTL Radwiz System via Frame Relay. . But without success.

First of all, I install Tau drivers v 3.33 according the instruction and put
into kernell config file some parameters for NETGRAPH and this card. Looks like
options         NETGRAPH
options         NETGRAPH_CRONYX         # Netgraph mode
options         NETGRAPH_FRAME_RELAY
options         NETGRAPH_LMI
.....
# Cronyx-Tau-PCI adapter(s).
device          cp0

After recompile kernel and reboot system I saw, that Unix detect this card
/kernel: cp0: <Cronyx-Tau-PCI serial adapter>  mem
0xe4000000-0xe400ffff,0xe4010000-0xe40107ff  irq 9 at device 11.0 on pci0
/kernel: cp0: Tau-PCI-E1, clock 16 MHz
Fine.

Then, I set some parameters for card like syncronization, time slots and CRC.
sconfig cp0 syn=rcv crc4=on use16=on ts=1-31
And execute following command for the NETGRAPH
# create a frame_relay type node and attach it to the sync port.
ngctl mkpeer cp0: frame_relay rawdata downstream
# Attach the dlci output of the (de)multiplexor to a new
# Link management protocol node.
ngctl mkpeer cp0:rawdata lmi dlci0 auto0
# Attach the DLCI(channel) the Telco has assigned you to
# a node to hadle whatever protocol encapsulation your peer
# is using. In this case rfc1490 encapsulation.
ngctl mkpeer cp0:rawdata rfc1490 dlci100 downstream
# Attach the ip (inet) protocol output of the protocol mux to the ip (inet)
# input of a netgraph "interface" node (ifconfig should show it as "ng0").
#if interface ng0 needs to be created use a mkpeer command.. e.g.
ngctl mkpeer cp0:rawdata.dlci100 iface inet inet
# Then use ifconfig on interface ng0 as usual
ifconfig ng0 10.0.4.2 10.0.4.1 netmask 255.255.255.252

As result of this manipulation all signals on Tau turn on.
/var/log > sconfig -i
cp0 idle cfg=A 1984000 syn=rcv higain=off use16=on crc4=off loop=off ts=1-31
/var/log > sconfig -m
Channel LE      DTR     DSR     RTS     CTS     CD
cp0        On      On        On        On       On       On

Unfortunetly, I have no replay on ping to 10.0.4.1 yet.
But in /var/log/messages I find such strings
Jul 18 09:35:48 tau /kernel: nglmi: unexpected message type(0x0)
Jul 18 09:35:49 tau /kernel: nglmi: error at location 3
Jul 18 09:35:49 tau /kernel: nglmi: packet data: 03 08 00>75 95 01 01 00 03 02
0b 00
Jul 18 09:35:49 tau /kernel: nglmi: no response from exchange
Jul 18 09:35:59 tau /kernel: nglmi: unexpected message type(0x0)
Jul 18 09:35:59 tau /kernel: nglmi: error at location 3
Jul 18 09:35:59 tau /kernel: nglmi: packet data: 03 08 00>75 95 01 01 00 03 02
0c 00

Anybody know that does this message mean ?
Or there I make mistake ?

Thanks in advance.

Best regards
Vladimir N. Kovalev





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?39745F45.D441D899>