Ok, there seems to be some conflicting info on what to send the CE devices when they send CLIENT. Some say send SERVER, some send CLIENT\cSERVER. But leaving that at one side for a moment ... I've been tracing the IR traffic and I got the bit where the Jornada sends CLIENT but not the bit where the PC sends SERVER back. Should this bit be visable?? I enclose the relevant irdadump -x trace and the ppp options file I am using. I am using stock kernel 2.4.2ac28. Cheers, Ian. Trace (irdadump -x): 11:55:00.484228 i:cmd < ca=90 pf=1 nr=0 ns=0 LM slsap=03 dlsap=00 CONN_CMD (6) 911080030100 . . . . . . 11:55:00.484315 i:rsp > ca=90 pf=1 nr=1 ns=0 LM slsap=00 dlsap=03 CONN_RSP (6) 903083008100 . 0 . . . . 11:55:00.504236 i:cmd < ca=90 pf=1 nr=1 ns=1 LM slsap=03 dlsap=00 GET_VALUE_BY_CLASS: "IrDA:IrCOMM" "IrDA:TinyTP:LsapSel" (37) 91320003840b497244413a4972434f4d4d13497244413a54696e7954503a4c73 . 2 . . . . I r D A : I r C O M M . I r D A : T i n y T P : L s 11:55:00.504297 i:rsp > ca=90 pf=1 nr=2 ns=1 LM slsap=00 dlsap=03 GET_VALUE_BY_CLASS: Success Integer: 23 (15) 905203008400000123430100000023 . R . . . . . . # C . . . . # 11:55:00.524233 i:cmd < ca=90 pf=1 nr=2 ns=2 LM slsap=03 dlsap=00 DISC (6) 915480030201 . T . . . . 11:55:00.524300 rr:rsp > ca=90 pf=1 nr=3 (2) 9071 . q 11:55:00.544231 i:cmd < ca=90 pf=1 nr=2 ns=3 LM slsap=02 dlsap=23 CONN_CMD TTP credits=0(7) 9156a302010004 . V . . . . . 11:55:00.544325 i:rsp > ca=90 pf=1 nr=4 ns=2 LM slsap=23 dlsap=02 CONN_RSP TTP credits=0(7) 9094822381000e . . . # . . . 11:55:00.564230 rr:cmd < ca=90 pf=1 nr=3 (2) 9171 . q 11:55:00.564258 rr:rsp > ca=90 pf=1 nr=4 (2) 9091 . . 11:55:00.584230 i:cmd < ca=90 pf=1 nr=3 ns=4 LM slsap=02 dlsap=23 TTP credits=0 (12) 917823020000434c49454e54 . x # . . . C L I E N T 11:55:00.584320 rr:rsp > ca=90 pf=1 nr=5 (2) 90b1 . . 11:55:00.614238 rr:cmd < ca=90 pf=1 nr=3 (2) 9171 . q 11:55:00.614277 i:rsp > ca=90 pf=1 nr=5 ns=3 LM slsap=23 dlsap=02 TTP credits=1 (23) 90b602230111220010040000258011010312010020010c . . . # . . " . . . . . % . . . . . . . . . [shouldn't this bit have included SERVER ?] 11:55:00.664232 rr:cmd < ca=90 pf=1 nr=4 (2) 9191 . . 11:55:00.664268 rr:rsp > ca=90 pf=1 nr=5 (2) 90b1 . . [last 2 repeated x 10] 11:55:00.874307 i:rsp > ca=90 pf=1 nr=5 ns=4 LM slsap=23 dlsap=02 TTP credits=0 (9) 90b80223000320010c . . . # . . . . 11:55:00.894230 rr:cmd < ca=90 pf=1 nr=5 (2) 91b1 . . 11:55:00.894263 rr:rsp > ca=90 pf=1 nr=5 (2) 90b1 . . [last 2 repeated for ever] PPP options file: /dev/irnine 115200 crtscts noauth passive local 192.168.1.1:192.168.1.100 ms-dns 192.168.0.1 debug connect "/usr/sbin/chat -v CLIENT SERVER" Dag Brattli wrote: > Yes, you need to add a few things to your connect script. > Something like (don't remember exactly): > connect "chat CLIENT CLIENTSERVER" > > On Fri, 30 Mar 2001 12:39:27 +0100, Ian Barry wrote: > > I've managed to [snipped] --- Ian Barry, Appliance Studio Ltd. _______________________________________________ Linux-IrDA mailing list - [EMAIL PROTECTED] http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
