Hi All We figured out the solution to our Tmote Connect problem.
Pressing the reset button at the back of the Tmote Connect(NSLU2) for 30 seconds resets the network settings to default. This detail is found in a page deep down in LinkSys' NSLU2 help site. ( I am not sure if this method has any side-effects. As our Tmote Connect was a brand new one, we could afford to do it. It did not erase the Moteiv software though.) Having done that, we were able to get the device on IP address 192.168.1.77 . After resetting the IP address to default, we followed the procedure given in Moteiv's guide to change the IP address. Surprisingly, the LKGxxyyzz label on the device was wrong and did not contain part of the actual MAC address, as outlined in Moteiv's Tmote Connect User Guide. We had to figure out the real MAC address using a network probing tool. Regards, Harish On 4/11/07, Urs Hunkeler <[EMAIL PROTECTED]> wrote:
Hi, Just some random idea (I don't have a TMote Connect, so this is all guessing): maybe the TMote Connect only sends broadcasts to obtain an IP address from a DHCP server. It wouldn't make sense to include an IP address in these broadcasts as those packets are not IP packets. So the TMote Connect could still have assumed the IP address 192.168.1.77. You could try to reach the TMote Connect by just assuming that it has the IP address 192.168.1.77. If you try a ping, the device should at least answer the ARP request. Cheers, Urs harish prabhu schrieb: > Hi, > > We have recently purchased a TMOTE CONNECT. However we are unable to get it > working. > > Our Environment setup is : > > 1) OS – Windows XP > > 2) No DHCP Server on the network > > > Also we noticed that the MAC address (as formulated according to the user > manual) and the actual MAC address (found by using an IP sniffer) are > different. Also we find that, though the IP sniffer is able to display the > MAC address of this device, the device does not seem to be getting an IP > address at all. The manual mentions that in the absence of a DHCP server > the > device will try to claim an IP address of 192.168.1.77, if there is no > conflict. We have checked that there is no conflict at this address, yet > the > device is not able to obtain an IP address. All packets that come out of > the > device are broadcast packets. > > Has anyone faced a similar problem ? > Can someone please help us get this device running? > > Regards > Harish Prabhu
_______________________________________________ Tinyos-help mailing list [EMAIL PROTECTED] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
