Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying OpenVPN 2 Cookbook
  • Table Of Contents Toc
  • Feedback & Rating feedback
OpenVPN 2 Cookbook

OpenVPN 2 Cookbook

4.1 (12)
close
close
OpenVPN 2 Cookbook

OpenVPN 2 Cookbook

4.1 (12)

Overview of this book

Table of Contents (19 chapters)
close
close
OpenVPN 2 Cookbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1
Index

Plaintext tunnel


In the very first recipe, we created a tunnel in which the data traffic was not encrypted. To create a completely plain text tunnel, we also disable the HMAC authentication. This can be useful when debugging a bad connection, as all traffic over the tunnel can now easily be monitored. In this recipe, we will look at how to do this. This type of tunnel is also useful when doing performance measurements, as it is the least CPU-intensive tunnel that can be established.

Getting ready

Install OpenVPN 2.0 or higher on two computers. Make sure the computers are connected over a network. For this recipe, the server computer was running CentOS 5 Linux and OpenVPN 2.1.1 and the client was running Fedora 13 Linux and OpenVPN 2.1.1.

As we are not using any encryption, no secret keys are needed.

How to do it...

  1. Launch the server (listening)-side OpenVPN process:

       [root@server]# openvpn \
                --ifconfig 10.200.0.1 10.200.0.2 \
                --dev tun -–auth none
    
  2. Then launch the client-side OpenVPN process:

       [root@client]# openvpn \
                --ifconfig 10.200.0.2 10.200.0.1 \
                --dev tun –-auth none\
                --remote openvpnserver.example.com
    
  3. The connection is established with two warning messages in the output:

    … ******* WARNING *******: null cipher specified, no encryption will be used

    … ******* WARNING *******: null MAC specified, no authentication will be used

How it works...

With this setup, absolutely no encryption is performed. All the traffic that is sent over the tunnel is encapsulated in an OpenVPN packet and then sent "as-is".

There's more...

To actually view the traffic, we can use tcpdump:

  • Set up the connection as outlined.

  • Start tcpdump and listen on the network interface, not the tunnel interface itself:

    [root]@client]# tcpdump -w -I eth0 -s 0 host openvpnserver \
               | strings
    
  • Now, send some text across the tunnel, using something like nc (Netcat). First, launch nc on the server side:

     [server]$ nc -l 31000
    
  • On the client side, launch nc in client mode and type the words hello and goodbye.

     [client]$ nc 10.200.0.1 3100
             hello
             goodbye
    
  • In the tcpdump window, you should now see:

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
OpenVPN 2 Cookbook
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon