Call for testers: fxp(4) WOL

[James Phillips]

Original From: Pyun YongHyeon <pyunyh at xxxxxxxxx>
date: Wed, 15 Oct 2008 09:37:45 +0900

Hello,

I was finally able to test the WOL on my machine, a pre-2000 Compaq Deskpro Running an Intel 82558 Pro/100 Ethernet NIC with WOL.
This card only supports "Magic Packets."

I had to enable APM instead of ACPI; following these instructions:
http://forums.freebsd.org/showthread.php?t=4619

(On my first try I made a show-stopping typo as well).

FreeBSD version: 
7.2-RELEASE-p2
GENERIC i386

Some selected boot messages:
apm0: <APM BIOS> on motherboard
apm0: found APM BIOS  v1.2, connected at v1.2
. . .
     fxp0 options = 2000 < VLAN_MTU, WOL_MAGIC>

# apm
APM version: 1.2
APM Management: Enabled
AC Line Status: on-line
Battery Status: unknown
Remaining battery life: unknown
Remaining battery time: unknown
Number of batteries: 0
Resume timer: disabled
Resume on ring indicator: disabled
APM Capabilities:
  global standby state
  global suspend state
  resume timer from standby
  resume timer from suspend
  RI resume from standby
  RI resume from suspend

# zzz
-> Screen flickered, did not respond to pings.
>From router:
[gate at Freesco] wakelan -h
Usage: wakelan [options] [mac] [broadcast] [port]
    -b addr    broadcast address
    -m mac     mac address of host
    -p port    UDP port to broadcast to
    -v[v]      version
[gate at Freesco] wakelan -b 192.168.26.255 -m 00:08:c7:bb:83:d8
-> Machine again responded to pings.

Ping results with the Power/Suspend Switch activated in the middle (no WOL this time):
james at test:~$ ping dusty
PING dusty.inet (192.168.26.69) 56(84) bytes of data.
64 bytes from dusty (192.168.26.69): icmp_seq=1 ttl=64 time=3.87 ms
64 bytes from dusty (192.168.26.69): icmp_seq=2 ttl=64 time=3.06 ms
64 bytes from dusty (192.168.26.69): icmp_seq=3 ttl=64 time=0.174 ms
64 bytes from dusty (192.168.26.69): icmp_seq=4 ttl=64 time=0.187 ms
64 bytes from dusty (192.168.26.69): icmp_seq=5 ttl=64 time=0.178 ms
64 bytes from dusty (192.168.26.69): icmp_seq=6 ttl=64 time=0.188 ms
64 bytes from dusty (192.168.26.69): icmp_seq=7 ttl=64 time=0.176 ms
64 bytes from dusty (192.168.26.69): icmp_seq=8 ttl=64 time=0.200 ms
64 bytes from dusty (192.168.26.69): icmp_seq=9 ttl=64 time=0.192 ms
64 bytes from dusty (192.168.26.69): icmp_seq=10 ttl=64 time=3.97 ms
64 bytes from dusty (192.168.26.69): icmp_seq=22 ttl=64 time=0.229 ms
64 bytes from dusty (192.168.26.69): icmp_seq=23 ttl=64 time=0.195 ms
64 bytes from dusty (192.168.26.69): icmp_seq=24 ttl=64 time=0.166 ms
64 bytes from dusty (192.168.26.69): icmp_seq=25 ttl=64 time=0.178 ms
64 bytes from dusty (192.168.26.69): icmp_seq=26 ttl=64 time=0.176 ms
64 bytes from dusty (192.168.26.69): icmp_seq=27 ttl=64 time=0.182 ms
64 bytes from dusty (192.168.26.69): icmp_seq=28 ttl=64 time=0.184 ms
64 bytes from dusty (192.168.26.69): icmp_seq=29 ttl=64 time=0.181 ms
64 bytes from dusty (192.168.26.69): icmp_seq=30 ttl=64 time=0.176 ms
64 bytes from dusty (192.168.26.69): icmp_seq=31 ttl=64 time=0.158 ms

--- dusty.inet ping statistics ---
31 packets transmitted, 20 received, 35% packet loss, time 29999ms
rtt min/avg/max/mdev = 0.158/0.701/3.970/1.242 ms

-> As expected.

I am working on getting my router to automatically wake up the server when a client machine wakes-up/connects to the network.

I have been feeling guilty leaving my server idling 24/7 even if it is barely used.

Regards,

James Phillips




      __________________________________________________________________
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now
http://ca.toolbar.yahoo.com.