Am 03.03.2011 um 22:09 schrieb Brandeburg, Jesse: > On Thu, 3 Mar 2011, Mathias Krause wrote: > >> Hello e1000e developers, >> >> I have a problem getting a specific wake-on-lan combination getting to >> work on my onboard 82574L PCIe adapter. I would like to wake the system >> from S3 by either an ARP request or an unicast packet send to the system, >> e.g. an ICMP packet. What I'm seeing is that wake-on-unicast works, but >> wake-on-arp does not, albeit the adapter is configured to do so: > > Sorry to hear wake on arp is not working, I'm hoping Carolyn can take a > look or our lab can reproduce. > > Wake on arp may not be the best wake behavior however because most systems > receive an arp at least every two minutes from the switch port they are > plugged into. Other machines on your network will also arp for your > machine if they recently contacted it.
It should of course only wake the system if the NIC receives an ARP request for one of its configured IP addresses. But I'll monitor my network to see if this might be a problem or not. >> Reading the specification (document number 317694-020, section 5.5.3.1), >> the adapter should wake on ARP request because it wakes up on unicast >> packets directed to the configured IPv4 address. The document states that >> the ARP method and the unicast method are using the same table for IP >> addresses matching (IP4AT), so if it works for the unicast case it should >> work for the ARP case also, shouldn't it? > > I'm not sure that anything programs the IP4AT register, as I don't see it > being used in our drivers. I imagine that is relevant. :-) But then, how does the current wake on unicast method work? It does need to tell the card the addresses to look for, too. Can you give me some pointers to functions in the e1000e source? I've found the places where setting a specific wake method via ethtool toggles the bits in the WUFC register. But it's only enabling/disabling the support for that wakeup event which, in fact, doesn't satisfies the requirements for wake on ARP. I assume the wake on unicast method is using the MAC address of the interface as a filter? > I think the > problem is the interface to ethtool should provide a way to program the IP > address to the NIC when enabling wake on arp. That would be great but how about automatically falling back to the first four configured addresses until ethtool supports specifying the addresses to use for wakeup? Regards, Mathias ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
