*The following example is done in the [[w:Debian|Debian]] GNU/Linux distribution.

+

*In [[w:Debian|Debian]] using the [[w:Unstable (Debian)|Unstable]] or [[w:Testing (Debian)|Testing]] branch the aoetools<ref>[http://aoetools.sourceforge.net/ Sourceforge: ATA Over Ethernet Tools]</ref> package <ref>[http://packages.debian.org/unstable/admin/aoetools Debian Package: aoetools] - tools to assist in using ATA over Ethernet</ref> can be installed using [[w:Aptitude (program)|aptitude]].

−

+

−

Install the aoetools<ref>[http://aoetools.sourceforge.net/ Sourceforge: ATA Over Ethernet Tools]</ref> package <ref>[http://packages.debian.org/unstable/admin/aoetools Debian Package: aoetools] - tools to assist in using ATA over Ethernet</ref> using aptitude. You will need to have [[w:Unstable (Debian)|Unstable (Debian)]] or [[w:Testing (Debian)|Testing (Debian)]] branch enabled.

Advantages

AoE avoids the usual high-level TCP/IP or UDP protocols; it's a base-level protocol itself. (For the technically-minded, it is an OSI level 2 protocol.) This gives the advantage of higher speed transfers, as the protocol doesn't have to build upon existing structures. In comparison, iSCSI runs over TCP/IP.[4]

It apparently uses less CPU time than the similar iSCSI protocol. For the technically minded, the AoE specification[5][6] is 8 pages compared with iSCSI's[7] 257 pages.

AoE is not routable over LANs and is intended for SANs only, which can provide greatly increased security.

Disadvantages

Each partition on the server computer can only be used by one client at a time; AoE is not intended to be a replacement for NFS or similar protocols which run on top of filesystems. It is designed to work at a much lower level.

As the protocol is non-routable, the servers cannot be separated by routers.

Uses

ATA Over Ethernet is therefore useful for creating cheap SANs, but it is not intended for the average user. It is very definitely not useful for sharing files easily: NFS or Samba is much better for this.

WARNING!

There is a possibility that you could brick your NAS with these instructions. Please make sure that you read the entire page carefully. This was a proof of concept exercise that someone on the IRC proposed. I bricked my LS the first time I played with this and had to reflash

Installation

The Linkstation is used as a server running vblade. A separate computer is a client running aoetools. This version of vblade runs in userspace, however there are versions that run in kernelspace.[8][9]

Server (vblade)

FreeLink

Use aptitude to install the vblade componant of AoE[10]. You will need to have the unstable branch added.

The first number (1) is the shelf number, the second (2) the slot number, change these numbers to your liking. The eth0 part tells vblade what interface to use, it will only be available to that interface on that direct connection. It can't go through routers and it can't be redirected. The last argument is the device name to share, this could be /dev/sda1 or some other device.

vblade 1 2 eth0 /dev/sda1

Or instead to have it run on startup and stay up since Vblade may not take well to being forked. Adding it to /etc/inittab as a command that would respawn itself should "daemonize" vblade[11]. If someone has a better solution please put it in here, it may be possible to add it to init.d