Quick and Easy File Transfer with netrw
Fast Transport

© Lead Image © Tomas Anderson, 123RF.com
Even without elaborate infrastructure, you can still push your data across the network with netrw.
If you're looking for a quick and easy tool for transferring files, netrw [1] offers an elegant solution. According to the project website, the purpose of netrw is to "simplify and speed up file transfers to hosts without an FTP server." Netrw is also useful for scenarios where the user transferring the file does not have an account on the target machine.
The netrw project consists of two programs, netread
and netwrite
. As the names imply, netwrite
writes the file from the sending machine and netread
reads it on the target. The advantage of this ad hoc solution, compared with solutions in which the daemon listens constantly, is the brief existence of the open channel. This design reduces the likelihood of an attacker accidentally stumbling across the open port.
Netrw gives you the ability to transfer any kind of electronic data. Of course, it's always better to use netrw on a protected network, and you are advised not to use it in an insecure setting. If you do, however, you'll want to protect your privacy by encrypting the payload.
Basic Functions
In the simplest case, start by initializing the reception of data with netread
. You only specify the port number and redirect stdout to a file (Listing 1, line 1). The transfer itself is launched in the same style (line 2).
Listing 1
Configuring Data Reception
01 $ netread <port> > <outputfile> 02 $ netwrite <IP address> <port> < <file>
Figure 1 shows the transfer sequence. The two programs have common options; the most important ones are described in Table 1.

Table 1
Options for netread and netwrite
Parameter | Explanation |
---|---|
udp |
Uses UDP instead of TCP |
-f <Host> |
Establishes a connection on the read side |
-C <Algorithm> |
Uses specified algorithm (sha1, md5, rmd160, none) |
-o <File> |
Specifies the file |
-h <Value> |
Outputs the progress of all <Value>s (KB) |
-H <Value> |
Outputs the progress of all <Value>s (MB) |
-b |
Specifies speed in bps (instead of Bps) |
-q |
Suppresses screen output |
-v |
Outputs detailed messages |
-vv |
Outputs very detailed messages |
You can either redirect the payload directly from a file or you can use the -i <file>
option in netwrite
. On the target system, use the output redirection (>
) or the -o <file>
option for saving the data.
Progress
The progress indicator proves especially useful for transferring large volumes of data; it lets you check to see whether bytes are actually still flowing across the network. You can choose between a display in kilobytes (-h
) or megabytes (-H
). The option requires you to define the volume of data that triggers a hash mark being written to screen. This can mean that your screen either fills up or shows very little information (Figure 2).

In a shell script (Listing 2) [2], you could use stat
[3] to determine the size of the file and then define a useful integer value for the progress bar. Note that one line is made up of 50 hash marks. Accordingly, you might not see any output for very small volumes of data.
Listing 2
Determining File Size
01 #! /bin/sh 02 if [ -z $1 ]; then 03 echo "File name missing - CANCEL!" 04 exit 05 elif [ -z $2 ]; then 06 echo "Remote computer/target port missing - CANCEL!" 07 exit 08 elif [ -z $3 ]; then 09 echo "Remote computer/target port missing - CANCEL!" 10 exit 11 fi 12 13 volume=$(stat -c %s $1) 14 diamonds=$(echo $volume/1014/50 | bc) 15 netwrite -h $diamonds $2 $3 < $1
The receiving side does not know the file size in advance. You can either ask for this value before the transfer is initiated or use a value of 1000
; experience has shown that -H
produces reasonable output.
Figure 3 shows the flow of the script. For clarity, positional parameters are used in place of input templates. You could extend this script accordingly with the capabilities of Zenity [4] or cdialog [5].

Firewall Mode
Firewall mode lets you set up a connection in the reverse direction. You can pass in either the IP address or a hostname using the -f
option. The following workflow has proved useful in practical terms: Call netwrite
with the -f
option, then start netread
also with -f
. This means that you are using firewall mode on both systems, but the startup sequence is the other way around.
In Figure 4, you can see the steps required for the sender (light background in the terminal) and the receiver (dark background). The computers are addressed by their hostnames (ze5
and ZE6
). After the call to netwrite
, you will see a message that the program is listening on the specified port. The other messages are displayed after calling netread
on the target system.

Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Direct Download
Read full article as PDF:
Price $2.95
News
-
Red Hat Enterprise Linux 7.5 Released
The latest release is focused on hybrid cloud.
-
Microsoft Releases a Linux-Based OS
The company is building a new IoT environment powered by Linux.
-
Solomon Hykes Leaves Docker
In a surprise move, Solomon Hykes, the creator of Docker has left the company.
-
Red Hat Celebrates 25th Anniversary with a New Code Portal
The company announces a GitHub page with links to source code for all its projects
-
Gnome 3.28 Released
The latest GNOME rolls out with better contact management and new features for handling virtual machines.
-
Install Firefox in a Snap on Linux
Mozilla has picked the Snap package system to deliver its application to Linux users.
-
OpenStack Queens Released
The new release comes with new features for mission critical workloads.
-
Kali Linux Comes to Windows
The Kali Linux developers even managed to run full blown XFCE desktop via WSL.
-
Ubuntu to Start Collecting Some Data with Ubuntu 18.04
It will be an ‘opt-out’ feature.
-
CNCF Illuminates Serverless Vision
The Cloud Native Computing Foundation announces a paper describing their model for a serverless ecosystem.