Hi,
Sorry for not reponding to the earlier question of:
> After receiving Obex stuff on your Palm, when you
> can't do your PPP connection, if you try to send
> Obex stuff from Palm to Linux, what does happen ?
> This is important to know if the bug is IrTTP or
> IrComm.
Obex connections work fine even after the PPP fails.
Again, sorry for not including the behavior alongside
the log. Have put in my 2 cents worth for what happens
at the various stages in the log.
> > Apr 11 16:42:38 rl62 modprobe: can't locate module
> > irda-dongle-1
The above message is generated when I start the PPPd
deamon. The irda dongle I am using is the esi dongle.
I have yet to understand why this message is
generated.
> > Apr 11 16:43:09 rl62 pppd[492]: LCP: timeout
> sending Config-Requests
> No IrDA link or bug in the IrDA stack. Maybe a
> normal PPP disconnect. To check further.
The above message is generated once I start the PPP
demaon and if there is no PPP connection initiated for
some time, about 30 seconds. Earlier it used to stop
the PPP deamon after this message, but now I have it
on with the persist option and hence it does not stop
listening for PPP connections after this message.
> Apr 11 16:50:37 rl62 kernel: IrLAP, no
> activity on link!
> Apr 11 16:50:37 rl62 kernel: Assertion
> failed! hashbin->hb_current !=
> NULL,irqueue.c,hashbin_get_next,line=502
>
> No IrDA link. The Palm is quite brutal when it
> disconnect, that may be the reason.
> Ugly. Something is wrong. Do you managed to get
> Obex through
> at this point ?
Yes Obex did go through after this. This is what I
wanted clarified, what does the assertion mean.
> > Apr 11 17:02:36 rl62 irattach: Starting device
> irda0
> > Apr 11 17:02:36 rl62 irattach: executing: 'echo
> rl62 >
> > /proc/sys/net/irda/devname'
>
> Ok, we restart the stack.
That is right, I did an irattach after killing the
running irattach process. This is because after a PPP
connection, the IrComm device persists in the
discovery buffer for some time and I wanted to get rid
of that. Is there any other way to clear the discovery
buffer??
> > Apr 11 17:02:50 rl62 kernel: IrLAP, no activity on
> > link!
> I guess the end of the first Obex push.
> > Apr 11 17:02:50 rl62 kernel: Assertion failed!
> > hashbin->hb_current !=
> > NULL,irqueue.c,hashbin_get_next,line=502
> Don't like it.
Yes, there were quite a lot of Obex connections done
in this period. Again, what does the assertion mean??
> > Apr 11 17:08:58 rl62 kernel: ppp_tty_ioctl: set
> xmit
> > asyncmap 0
> Ok, we start PPP.
This is where the Palm initiated a PPP connection.
> > Apr 11 17:09:00 rl62 pppd[492]: IPCP terminated by
> > peer
> > Apr 11 17:09:01 rl62 pppd[492]: LCP terminated by
> peer
>
> The Palm doesn't like us and tell us to go away.
> That's probably a misconfiguration at the PPP level,
> because we managed to establish a basic LCP link (so
> IrDA and IrComm are ok).
> This one fail, but that's not the fault of
> IrDA.
In fact, this one did not fail, it did establish a PPP
connection and the Palm did disconnect properly.
> > Apr 11 17:09:06 rl62 kernel: IrDA: Registered
> device irda0
> > Apr 11 17:09:06 rl62 pppd[899]: pppd 2.3.11
> started by root, uid 0
> We restart IrDA.
>
> > Apr 11 17:09:07 rl62 irattach: Starting device
> irda0
> > Apr 11 17:09:07 rl62 irattach: executing: 'echo
> rl62 > /proc/sys/net/irda/devname'
> We restart IrDA.
> > Apr 11 17:09:26 rl62 kernel: IrLAP, no activity on
> > link!
> > Apr 11 17:09:36 rl62 pppd[899]: LCP: timeout
> sending Config-Requests
>
> No IrDA link ? Or maybe the PPP on the Palm
> disconnect brutal. Or maybe a bug in IrDA.
> What happened to this PPP connection ?
>
> <Probably bunch of Obex>
Again, this is a restart of irattach and a new PPP
deamon start. The restart of IR is to get rid of the
IrComm device in the discovery buffer. The PPPd
restart is to starting listening for PPP connections
again after the disconnect earlier. The LCP timeout is
the message by the PPP deamon after 30 seconds of no
activity on PPP.
> > Apr 11 17:59:58 rl62 kernel: ppp_tty_ioctl: set
> xmit asyncmap 0
> Hum... We seem to reuse the old instance of
> PPP, not create a new one. Why the old one is not
> dead yet ? It should have timeout by now. There is
> something weird in your PPP config.
What makes you say that, cause at this time, if you
look at the previous messages in the log, it is
successfull PPP connect and disconnect, a new
IrRestart and a new PPP deamon start, as you can see
from the messages below.
> > Apr 11 18:00:00 rl62 pppd[899]: IPCP terminated by
> > peer
> > Apr 11 18:00:01 rl62 pppd[899]: LCP terminated by
> peer
>
> Palm tell us to go away. Could you try with a fresh
> new instance of pppd instead of reusing the old one
?
> Use the timeout option of pppd.
This is in fact generated by the Palm disconnecting.
We are starting a new instance of ppp every time. As I
mentioned before the PPP deamon is started by the
following script:
===================
while x=1
do
/usr/sbin/pppd /dev/ircomm0 57600 local crtscts
nodetach noauth 10.0.1.1:10.0.1.2 passive ms-dns
10.0.0.1
sleep 1
kill -9 `/sbin/pidof irattach`
/usr/sbin/irattach /dev/ttySir -d esi
done
===================
Thanks again for all the help.
Nita.
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
