Use

For a baseline reference, I shared a directory with some large files on the Windows computer and transferred one of them via wireless. The transfer went from the computer's wireless card to my Linksys WRT54G, then to my Dell gigabit switch and into the gigabit Ethernet port of my desktop computer running Ubuntu. I used time and cp to transfer the file via a CIFS mount. It transferred a 142.3 MB (149199719 bytes) file in approximately one minute and 28 seconds. That's approximately 1655.71 KBps, or approximately 13.56 Mbps.

I conducted the same test using GameNet's powerline networking. I would have liked to have transferred the whole thing, but it was taking too long. After 17 minutes and 25.218 seconds, only 66.1 MB (69320704 bytes) had been transferred. That's 64.77 KBps, or 530.57 Kbps. It's adequate for gaming, but not for large file transfers.

I watched the status page during the transfer to see what kind of throughput each unit said I was getting. It never went above 30 Mbps for Tx or Rx.

I also did a ping test.

PING herbal.cadcx (192.168.1.141) 56(84) bytes of data.
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=1 ttl=128 time=165 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=2 ttl=128 time=17.3 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=3 ttl=128 time=4.56 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=4 ttl=128 time=8.38 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=5 ttl=128 time=22.0 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=6 ttl=128 time=24.7 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=7 ttl=128 time=21.9 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=8 ttl=128 time=10.2 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=9 ttl=128 time=28.8 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=10 ttl=128 time=16.8 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=11 ttl=128 time=1028 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=12 ttl=128 time=28.4 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=13 ttl=128 time=2.09 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=14 ttl=128 time=10.5 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=15 ttl=128 time=8.09 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=16 ttl=128 time=7.58 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=17 ttl=128 time=15.4 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=18 ttl=128 time=1.96 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=19 ttl=128 time=1.84 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=20 ttl=128 time=19.2 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=21 ttl=128 time=23.2 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=22 ttl=128 time=7.13 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=23 ttl=128 time=90.5 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=24 ttl=128 time=12.6 ms
64 bytes from herbal.cadcx (192.168.1.141): icmp_seq=25 ttl=128 time=29.1 ms

--- herbal.cadcx ping statistics ---
25 packets transmitted, 25 received, 0% packet loss, time 24072ms
rtt min/avg/max/mdev = 1.845/64.255/1028.283/199.607 ms, pipe 2

The average ping was 64.225 ms. That's adequate for Internet gaming, but it could be better. It's inadequate for LAN gaming.