JackOfAll wrote: > There may be something to this that requires further investigation. > ISTR, that someone posted about a similar problem before. (Might have > been Erland. My memory is a bit fuzzy. But we never got to the bottom of > it.) Something to do with the router was allocating the same IP to the > ethernet interface and the wireless, then he couldn't get back into it > and did a re-image. It may be to do with the router you use and its dhcp > implementation. My router allocates by MAC address, which will of course > be different for ethernet and Wi-Fi so they would never get the same IP. > I wonder if the device is sending "wandboard" as the clientId for both > interfaces and some routers allocate IP using that rather than MAC, so > both interfaces would get the same address........ Just thinking out > loud. Might need to put a unique clientId in both ifcfg files.....
DHCP always works with MAC addresses; that is how this protocol is built. The only way that the two interfaces would get the same IP address is that the Wandboard would request it with the same MAC address for both interfaces. During the tests I have been doing this is not the case and the Wandboard requests IP addresses with the correct MAC addresses. If someone has this issue again they should try to flush their ARP cache of the computer they're trying to connect to the Wandboard with. You can also have a look at what your computer has in cache (arp -a) and delete the entry for the Wandboard (arp -d IP address). ------------------------------------------------------------------------ Pascal Hibon's Profile: http://forums.slimdevices.com/member.php?userid=7969 View this thread: http://forums.slimdevices.com/showthread.php?t=98544 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
