I'm a bit lost at the moment with all these versions ... I got your git branch "devel", snapshot from 2008/08/12. As i've read it, it should be better to try "fakelb" and "serial" interface. kernel-af439cfe277c274905cf9be883a882b2889eb5e3.tar.gz I've cloned and compiled your git "user space tools" 2 weeks ago: 0.2-rc2 (if necessary i'll get a more recent snashots frome devels but tell me exacly which ones ? Notice i'd rather not get back to 0.1 that is as you say quite old hence far from current behaviour)
So here is what i want to do: # ./izattach /dev/ttyUSB0 OK seems to work, a [mwpan1] process (and corresponding interface according ifconfig -a) appears. As i did some small "printk" modifications in you kernel driver, i can see in /var/log/syslog that when the interface receive a valid "zb..." frame from my dongle it processes it and recognize a DATA_RECV_BLOCK (i verify main parts of my new firmware with your Python's tools). I will attach an other of our serial device to be able to make a coord on a mwpan1 and a device on a mwpan2 using yours tools, to avoid use of not supported part of 802.15.4 2003 specifications. So, questions are: 1) First, notice that "ifconfig mwpan1 up" give me: "SIOCSIFFLAGS: Operation not supported" ? And notice also that it does the same for "mwpan0" that is created at boot time ? 2) How to define the address (short or long) to an interface (mwpanX) (notice that 0.2-rc2 ther is no "izconfig" command) ? 3) How can set an interface working as a coordinator (izcoordinator syntax) ? 4) How can I set the other device associated to the firs one (iz assoc syntax ?) 5) How can "izchat" beetween these two serial interfaces ? Thank's for your precise answer (command to type for each questions) i'll tell you the result for each of them. Sincerely Dmitry Eremin-Solenikov a écrit : >> Consequently, what i would like to achieve, is to create the attachement >> "izattach" to my "WPC dongle", then use your tools "iz, izchat". But the >> Wiki "Howto" just talk about "fakelb" using. (Notice that fakelb >> currently does not work for me :O( Cf PS1 ...) So how can i find and >> use a newly attached serial device ? If it's possible, what should be >> the <iface> parameter for "iz" and "izchat" softwares ? >> > > As a side note: you may use > izconfig short PANID:DEVADDR to 'fake' devide association w/ a network > by making it use PANID DEVADDR as a short address. > > then izchat will be just happy in talking w/ some other network node > (if you care to check it just send what it gets from the console as a > network package to the other node and prints on the console > packages that it does receive from the node specified). I think there is > a short manpage for the izchat. > > Regarding iz: when you have network interface (either directly on old kernels, > or allocated via 'ip link add' on newer ones, you should use it. > > Hope this helps. > > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel