Hi
"CLIENT" is part of the Microsoft server chat script, required to get a ppp
connection up and running to NT RAS. i.e. it's well above the IrCOMM level,
so fortunately they're not doing any proprietary extensions there ;-)
The following is the WinCE-equivalent script used in my Psion 5:
! Generic script for direct cable connections
! Suitable for NT RAS as supplied
start:
LOOP 3
{
SEND "CLIENT"+<0x0d>
WAIT 10
{
"SERVER" success
}
}
EXIT KErrTimeOut$
success:
EXIT
So basically, rather the hack pppd, all that is necessary is to use a simple
connect script to interface to this (assuming WinCE doesn't require anything
extra). e.g. something along the lines of:
> pppd ircomm0 115200 connect '/usr/sbin/chat "CLIENT" "SERVER"' ...
should do the trick. The (questionable?) benefit of this is that is makes
the linux machine look like an NT RAS server to any device configured to use
NT RAS (psion, palm, win95...?), not just WinCE devices.
Cheers
Joth
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jon Burford
> Sent: 10 December 1999 21:08
> To: [EMAIL PROTECTED]
> Subject: Re: [Linux-IrDA]WinCE and IrCOMM problems
>
>
> Yes, I have come accross this problem as well when trying to make an
> IrCOMM/PPP connection with a WinCE device. To get around it, you need to
> manually start the connection. Essentially you start by running
> a getty on
> /dev/ircomm, making a serial console connection to the linux box (from CE
> using "Make a connection as a Hayes Modem) and then when you get a login
> prompt on the WinCE side, fire off PPP on the linux box on the
> IrCOMM link.
> This page helped me start an IrCOMM/PPP connection between a
> Linux and WinCE
> device:
>
> http://www.the-gadgeteer.com/linux_ce.html
>
> Good luck and let me know if you have any questions! I am also very
> interested in making this automated but haven't had time to come
> back to the
> problem (our customers are all Palm users so I didn't much care). I was
> thinking that you might have to write a special WinCE app to make
> the thing
> not do the funky CLIENT crap, but I actually think this is part of MS-CHAP
> which is not supported by the Linux PPP SERVER (it is supported if you use
> pppd to connect TO a MS-CHAP server). So, even if you use the WinCE PPP
> API, you still probably can't disable MS-CHAP. The obviously better
> approach is to either hack or correctly add support for MS-CHAP
> in the Linux
> pppd. This wasn't supported as of a few weeks ago in Linux pppd, but the
> pppd guys knew about it and were thinking about adding it.
>
> Regards,
> Jon
>
> ----- Original Message -----
> From: Dag Brattli <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, December 10, 1999 12:37 PM
> Subject: [Linux-IrDA]WinCE and IrCOMM problems
>
>
> > Hi,
> >
> > IrCOMM for Linux now works with most devices except WinCE. When WinCE
> > connects to Linux, it doesn't ask for IrDA:IrCOMM:Parameters or send any
> > initial parameters (as IrCOMM sais you should do). All it says
> is "CLIENT"
> > a couple of times before it disconnects. This smells like proprietary
> > stuff, so I'm a bit clueless! Anybody that can give me some hints.
> >
> > PS. We really need to make irdadump follow speed changes!
> >
> > -- Dag
> >
> > --
> > / Dag Brattli | The Linux-IrDA Project
> /
> > // University of Tromsoe, Norway | Infrared communication for Linux
> //
> > /// http://www.cs.uit.no/~dagb | http://www.cs.uit.no/linux-irda/
> ///
> >
> > 20:28:13.355562 snrm:cmd ca=fe pf=1 c677866c < 00001401 new-ca=24 (32)
> > ff93011400006c8677c62401012682010183013f84010f850180860102080107
> > . . . . . . l . w . $ . . & . . . . . ? . . . . . . . . . . . .
> > 20:28:13.356383 ua:rsp ca=24 pf=1 c677866c > 00001401 (31)
> > 24736c8677c60114000001012682010183013f84017f8501ff860101080107
> > $ s l . w . . . . . . . & . . . . . ? . . . . . . . . . . . .
> > 20:28:13.533295 rr:cmd < ca=24 pf=1 nr=0 (2)
> > 2511
> > % .
> > 20:28:13.533556 rr:rsp > ca=24 pf=1 nr=0 (2)
> > 2411
> > $ .
> > 20:28:13.575205 i:cmd < ca=24 pf=1 nr=0 ns=0 LM slsap=03 dlsap=00
> CONN_CMD (6) 251080030100
> > % . . . . .
> > 20:28:13.575565 i:rsp > ca=24 pf=1 nr=1 ns=0 LM slsap=00 dlsap=03
> CONN_RSP (6) 243083008100
> > $ 0 . . . .
> > 20:28:13.613355 i:cmd < ca=24 pf=1 nr=1 ns=1 LM slsap=03 dlsap=00
> GET_VALUE_BY_CLASS: "IrDA:IrCOMM" "IrDA:TinyTP:LsapSel" (37)
> > 25320003840b497244413a4972434f4d4d13497244413a54696e7954503a4c73
> > % 2 . . . . I r D A : I r C O M M . I r D A : T i n y T P : L s
> > 20:28:13.614225 i:rsp > ca=24 pf=1 nr=2 ns=1 LM slsap=00 dlsap=03
> GET_VALUE_BY_CLASS: Success Integer: 1f (15)
> > 24520300840000012343010000001f
> > $ R . . . . . . # C . . . . .
> > 20:28:13.653318 i:cmd < ca=24 pf=1 nr=2 ns=2 LM slsap=03 dlsap=00 DISC
> (6)
> > 255480030201
> > % T . . . .
> > 20:28:13.653649 rr:rsp > ca=24 pf=1 nr=3 (2)
> > 2471
> > $ q
> > 20:28:13.693358 i:cmd < ca=24 pf=1 nr=2 ns=3 LM slsap=02 dlsap=1f
> CONN_CMD TTP credits=0(7)
> > 25569f02010004
> > % V . . . . .
> > 20:28:13.693726 i:rsp > ca=24 pf=1 nr=4 ns=2 LM slsap=1f dlsap=02
> CONN_RSP TTP credits=0(7)
> > 2494821f81000e
> > $ . . . . . .
> > 20:28:13.733274 rr:cmd < ca=24 pf=1 nr=3 (2)
> > 2571
> > % q
> > 20:28:13.733505 rr:rsp > ca=24 pf=1 nr=4 (2)
> > 2491
> > $ .
> > 20:28:13.773313 i:cmd < ca=24 pf=0 nr=3 ns=4 LM slsap=02 dlsap=1f TTP
> credits=0 (12)
> > 25681f020000434c49454e54
> > % h . . . . C L I E N T
> >
> > _______________________________________________
> > Linux-IrDA mailing list - [EMAIL PROTECTED]
> > http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
>
>
> _______________________________________________
> Linux-IrDA mailing list - [EMAIL PROTECTED]
> http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
>
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
