Hi Dag,
Here is more info on my troubles with irdaping...
First, a few comments on discovery. When discovery is enabled
only one one side, the machine being discovered has reliably the name
of the other in /proc/net/irda/discovery, whereas the machine making
the discovery has the name of the other in /proc/net/irda/discovery
only from time to time. When both side are doing discovery, the name
of the other machine appear in /proc/net/irda/discovery most of the
time but it is not totally reliable.
Inspection with irdadump shows that some discovery frame get
lost. More details on demand. I don't know what is impacted by that...
Back to irdaping. Here is the irdadump :
-------------------------------------------------------
18:22:34.012170 xid:cmd ffffffff < e3b5c0c1 S=6 s=0 (14)
18:22:34.102164 xid:cmd ffffffff < e3b5c0c1 S=6 s=1 (14)
18:22:34.192164 xid:cmd ffffffff < e3b5c0c1 S=6 s=2 (14)
18:22:34.282163 xid:cmd ffffffff < e3b5c0c1 S=6 s=3 (14)
18:22:34.372163 xid:cmd ffffffff < e3b5c0c1 S=6 s=4 (14)
18:22:34.462232 xid:cmd ffffffff < e3b5c0c1 S=6 s=5 (14)
18:22:34.462345 xid:rsp ce4d5d1f > e3b5c0c1 S=6 s=5 weblab3 hint=0400 [ Computer ]
(23)
18:22:34.562174 xid:cmd ffffffff < e3b5c0c1 S=6 s=* tourrilhes-j-3 hint=8404 [
Computer IrCOMM ] (31)
18:22:52.012198 xid:cmd ffffffff < e3b5c0c1 S=6 s=0 (14)
18:22:52.102185 xid:cmd ffffffff < e3b5c0c1 S=6 s=1 (14)
18:22:52.192179 xid:cmd ffffffff < e3b5c0c1 S=6 s=2 (14)
18:22:52.282179 xid:cmd ffffffff < e3b5c0c1 S=6 s=3 (14)
18:22:52.372175 xid:cmd ffffffff < e3b5c0c1 S=6 s=4 (14)
18:22:52.462274 xid:cmd ffffffff < e3b5c0c1 S=6 s=5 (14)
18:22:52.462387 xid:rsp ce4d5d1f > e3b5c0c1 S=6 s=5 weblab3 hint=0400 [ Computer ]
(23)
18:22:52.522334 test:cmd ca=0xfe pf=1 ce4d5d1f > e3b5c0c1 (32)
18:22:53.522250 test:cmd ca=0xfe pf=1 ce4d5d1f > e3b5c0c1 (32)
18:22:53.772761 test:rsp ca=0xfe pf=0 e3b5c0c1 < ce4d5d1f (32)
18:22:54.522253 test:cmd ca=0xfe pf=1 ce4d5d1f > e3b5c0c1 (32)
18:22:54.772615 test:rsp ca=0xfe pf=0 e3b5c0c1 < ce4d5d1f (32)
18:22:55.012197 xid:cmd ffffffff < e3b5c0c1 S=6 s=0 (14)
18:22:55.102178 xid:cmd ffffffff < e3b5c0c1 S=6 s=1 (14)
18:22:55.192178 xid:cmd ffffffff < e3b5c0c1 S=6 s=2 (14)
18:22:55.282178 xid:cmd ffffffff < e3b5c0c1 S=6 s=3 (14)
18:22:55.372178 xid:cmd ffffffff < e3b5c0c1 S=6 s=4 (14)
18:22:55.462259 xid:cmd ffffffff < e3b5c0c1 S=6 s=5 (14)
18:22:55.462372 xid:rsp ce4d5d1f > e3b5c0c1 S=6 s=5 weblab3 hint=0400 [ Computer ]
(23)
18:22:55.522269 test:cmd ca=0xfe pf=1 ce4d5d1f > e3b5c0c1 (32)
18:22:56.522246 test:cmd ca=0xfe pf=1 ce4d5d1f > e3b5c0c1 (32)
18:22:56.772621 test:rsp ca=0xfe pf=0 e3b5c0c1 < ce4d5d1f (32)
18:22:57.522258 test:cmd ca=0xfe pf=1 ce4d5d1f > e3b5c0c1 (32)
18:22:57.772623 test:rsp ca=0xfe pf=0 e3b5c0c1 < ce4d5d1f (32)
18:22:58.012195 xid:cmd ffffffff < e3b5c0c1 S=6 s=0 (14)
18:22:58.102183 xid:cmd ffffffff < e3b5c0c1 S=6 s=1 (14)
18:22:58.192178 xid:cmd ffffffff < e3b5c0c1 S=6 s=2 (14)
18:22:58.282178 xid:cmd ffffffff < e3b5c0c1 S=6 s=3 (14)
18:22:58.372181 xid:cmd ffffffff < e3b5c0c1 S=6 s=4 (14)
18:22:58.462261 xid:cmd ffffffff < e3b5c0c1 S=6 s=5 (14)
18:22:58.462373 xid:rsp ce4d5d1f > e3b5c0c1 S=6 s=5 weblab3 hint=0400 [ Computer ]
(23)
18:22:58.522269 test:cmd ca=0xfe pf=1 ce4d5d1f > e3b5c0c1 (32)
18:22:59.522256 test:cmd ca=0xfe pf=1 ce4d5d1f > e3b5c0c1 (32)
18:22:59.772623 test:rsp ca=0xfe pf=0 e3b5c0c1 < ce4d5d1f (32)
18:23:00.522256 test:cmd ca=0xfe pf=1 ce4d5d1f > e3b5c0c1 (32)
18:23:00.772622 test:rsp ca=0xfe pf=0 e3b5c0c1 < ce4d5d1f (32)
-------------------------------------------------------
As you can see, a few discovery frames got lost on the way. Bah...
Now, a copy of dmesg with debug to 3 (not the same run) :
-------------------------------------------------------
irlmp_discovery_confirm()
irlmp_notify_client()
discovery->daddr = 0x7847cd36
async_wrap_skb(), wrong magic in skb!
irlmp_discovery_confirm()
irlmp_notify_client()
discovery->daddr = 0x7847cd36
async_wrap_skb(), wrong magic in skb!
irlap_recv_test_frame()
irlap_state_ndm() not implemented!
async_wrap_skb(), wrong magic in skb!
irlap_recv_test_frame()
irlap_state_ndm() not implemented!
async_wrap_skb(), wrong magic in skb!
irlmp_discovery_confirm()
irlmp_notify_client()
discovery->daddr = 0x7847cd36
async_wrap_skb(), wrong magic in skb!
irlap_recv_test_frame()
irlap_state_ndm() not implemented!
-------------------------------------------------------
In fact, maybe the "not implemented" is relevant there...
So, irdaping just sits there without telling me anything about
the packet it receives. When I press ^C, it tells me "X packet dropped
by filter".
I tried irdaping when IrComm is connected, but apparently with
the same results.
Have fun...
Jean
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
