Hi Joe We tried your suggestion but the problem persists and the device is unable to get any IP address. We tried pinging 192.168.1.77 and used a sniffer as well. The sniffer declares 192.168.1.77 to be an unknown IP address.
Regards, Harish On 4/11/07, Joe Polastre <[EMAIL PROTECTED]> wrote:
Have you put the Tmote Connect on a local network where your computer is on the same subnet (192.168.1.*) as the Tmote Connect device? Sometimes the best way to do this is directly connecting Tmote Connect to your computer through a cross-over cable and setting your computer's IP to 192.168.1.2, gateway of 192.168.1.1, and invalid DNS addresses. -Joe On 4/10/07, harish prabhu <[EMAIL PROTECTED]> wrote: > > > 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 > Tinyos-help@Millennium.Berkeley.EDU > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >
_______________________________________________ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
