Eduardo Espejo wrote: > These users can't connect with them ISP's because OAM request from users are > not replied, users from Euskaltel ( adding PACKETDEBUG (buf->base, > buf->filled_cells * 53) in xdslusb.c, xdslusb is a modiffication of > speedtch.c ) recieve this and ISP close the connection: > > xdslusb.c: udsl_process_receive: processing buf 0xc69378d8 > xdslusb.c: 000 : 00 80 02 3a d2 18 01 00 1d 62 5c ff ff ff ff ff > xdslusb.c: 016 : ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > xdslusb.c: 032 : ff ff ff 6a 6a 6a 6a 6a 6a 6a 6a 6a 6a 6a 6a 6a > xdslusb.c: 048 : 6a 6a 6a 00 bb
Decoding that gives: GFC=0 VPI=8 VCI=35 PTI=5 Result: We have just received an End-to-End F5 OAM Cell. As we are the endpoint we should respond to it. F5 is Virtual Channel Connection (VCC) so both the VPI and VCI are taken into account and will match the VPI/VCI of the circuit carrying the user data. End-to-End (PTI=5), Segment (PTI=4) F4 is Virtual Path Connection (VPC) so VPI is taken into account, and the VCI is used to determin if it is End-to-End (VCI=4) or Segment (VCI=3) pti number below is wrong if it is supposed to apply to the above cell dump. > xdslusb.c: udsl_extract_cells: vpi 8, vci 35, pti 1 > xdslusb.c: udsl_extract_cells: bogus pdu_length 27264 (sarb->len: 48, vcc: > 0xc6928e00)! > > All the drivers, with OAM loopback support , that I've seen have this > support in its module.. just look this modification of speedtch.c for works > with a 3COM modem > > http://wierdthings.webcindario.com/cxacru.c > > Well, Josep Comas is the admin too for the project for Zyxel 630-11 driver, > he promissed put this support in xdslusb.c just like cxacru.c (so many > months ago), but since many driver use speedtch.c like a template I think > this feature must be in the base.. > > If it is not necessary put this feature in the module, how can this users do > a OAM ping ?? > > Regards > When I use the "speedtch" kernel module. It links to the "atm" module. In my view, OAM support should be included in the "atm" module, then it will automatically work for all low level usb DSL modems, i.e. put the OAM handling code in one place, instead of duplicate it all over the place. As it does not appear to be in the "atm" module, then someone should add it. We should NOT respond to any OAM cells unless we know how to handle ATM. The "speedtch" should not need to know much, if any about ATM, and just pass the data to the "atm" module to handle. BUT, as the current "speedtch" seems to be lumping AAL5 cells into single AAL5 frames before sending them on (probably for performance reasons) we might have to add OAM support into the "speedtch" module. Cheers James Liste de diffusion modem ALCATEL SpeedTouch USB Pour se d�sinscrire : mailto:[EMAIL PROTECTED]
