> 
> I am actualy trying to establish the communication between a cisco router
> and my Free BSD machine.
> 
> +-------+                     +---------------+
> | cisco |serial interface     | FreeBSD 4.1   |
> | 3600  +-----------------------+             |
> |     |               RISCom  |               |
> +-------+             card    +---------------+
>       x.x.x.145       x.x.x.146
> 
> I beleive that the router is correclty configured but NOT the FreeBSD
> machine.
> 
> This is what dmesg | grep sr1 shows:
> --------
> sr1: Adapter 0, port 1.
> sr1 XXX: driver didn't set ifq_maxlen
> sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01.
> ...
> sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01.
> sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01.

There is 2 things you should make sure of.

1. If it is an ISA card that you are getting the interrupts. You can check
this with vmstat -i and make sure they do arrive. Some motherboards need
configuration in the BIOS to make isa interrupts work.

2. That the cisco is providing a clock. The sr driver configure the card
to expect a clock and it won't work without it.

> sr1: Down event, taking interface down.
> ...
> sr1: Down event, taking interface down.
> sr1: Down event, taking interface down.
> sr1: lcp illegal conf-req in state initial
> ...
> sr1: lcp illegal conf-req in state initial
> sr1: lcp illegal conf-req in state initial

This is a bug in the state machine of sppp. I have fixed it in -current,
but haven't merged it into stable yet.

> --------
> 
> This is the ifconfig:
> -------
> sr1: flags=8451<UP,POINTOPOINT,RUNNING,OACTIVE,MULTICAST> mtu 1500
>         inet6 fe80::2d0:b7ff:fe09:3333%sr1 --> :: prefixlen 64
> scopeid 0x2 
>         inet x.x.x.146 --> x.x.x.145 netmask 0xfffffffc 
> ------

You can also enable the debug flag in ifconfig, then you will see the
ppp packets, that should also help debuging the problem.

John
-- 
John Hay -- [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message

Reply via email to