(ASCEND) freebsd, Linix and CBCP

[brian <b.ragunathan@ulcc.ac.uk>]

Our Linix/freebsd users are experiencing problems with Callback ,since 
upgrading to 6.1.7 on our max 4000's which support CBCP.

They have sent part of their logs,


>       ... is having a few problems at the moment. Trying the 4191030 
number
> today I get as far as logging into the Ascend then when it trys to bring 
up
> the IP layer I get:
>
> pppd[6738]: IPCP terminated at peer's request
> pppd[6738]: sent [IPCP TermAck id=0x2]
> pppd[6738]: rcvd [proto=0xc029] 05 01 00 04
> pppd[6738]: Unknown protocol (0xc029) received


another users log

Jun 25 22:58:21 Garfield pppd[2373]: local  IP address 128.86.250.22
Jun 25 22:58:21 Garfield pppd[2373]: remote IP address 128.86.254.5
Jun 25 22:58:21 Garfield pppd[2373]: IPCP terminated by peer
Jun 25 22:58:21 Garfield pppd[2373]: Unsupported protocol (0xc029) received
Jun 25 22:58:22 Garfield pppd[2373]: LCP terminated by peer
Jun 25 22:58:25 Garfield pppd[2373]: Connection terminated.
Jun 25 22:58:25 Garfield pppd[2373]: Connect time 0.1 minutes.
Jun 25 22:58:25 Garfield pppd[2373]: Sent 225 bytes, received 269 bytes.


The 0xc029 seems to be a Micro$oft CBCP protocol.  These users have radius 
as well as Max profiles.  I have been told that CBCP is now globally turned 
on by default.  They users want to use the straight Callback feature in the 
max.  Is there a way around this problem?

Is it the CBCP protocol that is causing callback to bomb out?

Brian

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>