Bonjour,
 
Je suis entrain de configurer un serveur OpenVPN sous une debian,
 
Pour cela j'ai suivis ce tuto : http://www.coagul.org/article.php3?id_article=422
 
Cependant, dès que je lance le service, je perd tout les accès réseaux, d'autant plus que le VPN ne fonctionne pas, le client arrive à se connecter, mais ne ping personne.
 
Avez-vous des idées ou solutions    
 
 

logs? fichiers de config? Merci

Voici le fichier server.conf
 
#################################################
# Sample OpenVPN 2.0 config file for            #
# multi-client server.                          #
#                                               #
# This file is for the server side              #
# of a many-clients <-> one-server              #
# OpenVPN configuration.                        #
#                                               #
# OpenVPN also supports                         #
# single-machine <-> single-machine             #
# configurations (See the Examples page         #
# on the web site for more info).               #
#                                               #
# This config should work on Windows            #
# or Linux/BSD systems.  Remember on            #
# Windows to quote pathnames and use            #
# double backslashes, e.g.:                     #
# "C:\\Program Files\\OpenVPN\\config\\foo.key" #
#                                               #
# Comments are preceded with '#' or ';'         #
#################################################
 
# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d
 
# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one.  You will need to
# open up this port on your firewall.
port 1194
 
# TCP or UDP server?
;proto tcp
proto udp
 
# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun
 
# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one.  On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap
 
# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key).  Each client
# and the server must have their own cert and
# key file.  The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys.  Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca ca.crt
cert SRVOpenVPN.crt
key SRVOpenVPN.key  # This file should be kept secret
 
# Diffie hellman parameters.
# Generate your own with:
#   openssl dhparam -out dh1024.pem 1024
# Substitute 2048 for 1024 if you are using
# 2048 bit keys.  
dh dh1024.pem
 
# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
server 10.8.0.0 255.255.255.0
 
# Maintain a record of client <-> virtual IP address
# associations in this file.  If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist ipp.txt
 
# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface.  Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0.  Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients.  Leave this line commented
# out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100
 
# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses.  You must first use
# your OS's bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge
 
# Push routes to the client to allow it
# to reach other private subnets behind
# the server.  Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
push "route 192.168.0.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"
 
# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).
 
# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
client-config-dir ccd
route 192.168.0.0 255.255.255.0
# Then create a file ccd/Thelonious with this line:
#   iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN.  This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.
 
# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
#   ifconfig-push 10.9.0.1 10.9.0.2
 
# Suppose that you want to enable different
# firewall access policies for different groups
# of clients.  There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
#     group, and firewall the TUN/TAP interface
#     for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
#     modify the firewall in response to access
#     from different clients.  See man
#     page for more info on learn-address script.
;learn-address ./script
 
# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
;push "redirect-gateway def1 bypass-dhcp"
 
# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses.  CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
push "dhcp-option DNS 192.168.0.5"
push "dhcp-option DOMAIN Home.local"
 
# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
client-to-client
 
# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names.  This is recommended
# only for testing purposes.  For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn
 
# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120
 
# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
#   openvpn --genkey --secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be '0'
# on the server and '1' on the clients.
;tls-auth ta.key 0 # This file is secret
 
# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
;cipher BF-CBC        # Blowfish (default)
;cipher AES-128-CBC   # AES
;cipher DES-EDE3-CBC  # Triple-DES
 
# Enable compression on the VPN link.
# If you enable it here, you must also
# enable it in the client config file.
comp-lzo
 
# The maximum number of concurrently connected
# clients we want to allow.
;max-clients  
 
# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.
user openvpn
group openvpn
 
# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun
 
# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status openvpn-status.log
 
# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it.  Use one
# or the other (but not both).
;log         openvpn.log
;log-append  openvpn.log
 
# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3
 
# Silence repeating messages.  At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20

J'ai pas l'impression d'avoir bien activer les logs

iptabes ou autres qui bloquerait? si non je regarde t'as config se soir.

Le serveur est vraiment tout neuf, rien d'installer qui pourrait bloquer,
 
A moin qu'IPtables soit installer nativement ?
 
(Je debute sous ce système)

Quand tu dis "ne ping personne" tu as tenté de pinger quoi ?
As-tu fait des règles de routage ? Si oui lesquelles ?
Car de base OpenVPN sert à monter un tunnel, pas à nater.
 
tes logs ne sont pas activés puisqu'ils y a un ; devant
 
 
 
;log         openvpn.log
;log-append  openvpn.log  
 
D'ailleurs conseil, donne le chemin complet genre /var/log/openvpn/openvpn.log par exemple.
 
Si tu souhaites accèder à internet depuis ton client VPN tu devrais peut-etre push le DNS de ton FAI ou OpenDNS là-dedans
 
push "dhcp-option DNS 192.168.0.5"  
 
Et aussi, si tu fais un ifconfig ou un ipconfig /all cela te donne quoi coté client ?
 
Quand tu dis "dès que je lance le service" c'est coté client ou coté serveur ?

t'arrive a faire un ping sur 10.8.0.1?

Merci pour l'attention que vous portez a ce topic,
 
Je pense que Walk_Man a touché le point sensible :
 
Il n'y a pas de règle de routage de fait coté serveur, uniquement :
 
"route 192.168.0.0 255.255.255.0" dans le fichier de conf openvpn.
 
Est-ce obligatoire de mettre push le DNS de mon FAI etant donné que le serveur 192.168.0.5 est un serveur DNS qui gère ça ?
 
Coté client j'obtiens une IP en 10.8.0.6 je crois
Mais je ne ping pas depuis le client la 10.8.0.1
 
Le problème en plus de cela c'est qu'immediatement après que je le lance le service openvpn coté serveur je perd toute connexions, je ne ping donc ni la 10.8.0.1 ni la 192.168.0.6
 
Merci à vous !!

 
Pour le push DNS, ca depends l'interet de tes clients. Tu peux push les deux
 
lorsque tu fais un "openvpn start" tu perds le local depuis ton serveur ?!

Exactement toutes les interfaces ne ping plus le reseau local, et les clients ne le ping plus non plus

Pourrais-tu nous montrer un ifconfig avant d'avoir monté l'openvpn et après l'avoir monté ? Car que depuis le client tu ne ping pas grand chose ca se peut .. A voir la conf coté client aussi. Mais c'est super étonnant qu'en montant ton interface tunX foute toutes tes autres interfaces en vrac.
 
Voilà le genre de conf que j'ai mis en prod plusieurs fois sur du FreeBSD 6 et 7 pour te donner une idée
 

J'éssai de faire ça ce soir, je ne risque pas me couper l'accès à distance ^^
 
Coté client il n'y a qu'une route eventuellement a rajouter ?
 
Ta config ressemble de près a la mienne, a quelque detail près, ont ils leur importance ?
 
Pour l'histoire du nat il n'y a rien a revoir de ce coté la ?

 
Avant de songer au NAT, il faut déjà comprendre pourquoi tu perds le réseau.

Exacte, je communique le resultat de ifconfig ce soir

Jun  7 20:36:28 VPNSERVER10 ovpn-server[2928]: event_wait : Interrupted system call (code=4)
Jun  7 20:36:28 VPNSERVER10 ovpn-server[2928]: TCP/UDP: Closing socket
Jun  7 20:36:28 VPNSERVER10 ovpn-server[2928]: /sbin/route del -net 10.8.0.0 netmask 255.255.255.0
Jun  7 20:36:28 VPNSERVER10 ovpn-server[2928]: Closing TUN/TAP interface
Jun  7 20:36:28 VPNSERVER10 ovpn-server[2928]: /sbin/ifconfig tun0 0.0.0.0
Jun  7 20:36:28 VPNSERVER10 ovpn-server[2928]: SIGTERM[hard,] received, process exiting
Jun  7 20:36:29 VPNSERVER10 ovpn-server[3020]: OpenVPN 2.1_rc11 i486-pc-linux-gnu [SSL] [LZO2] [EPOLL] [PKCS11] built on Sep 18 2008
Jun  7 20:36:29 VPNSERVER10 ovpn-server[3020]: NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x.  Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.
Jun  7 20:36:29 VPNSERVER10 ovpn-server[3020]: Cannot open dh1024.pem for DH parameters: error:02001002:system library:fopen:No such file or directory: error:2006D080:BIO routines:BIO_new_file:no such file
Jun  7 20:36:29 VPNSERVER10 ovpn-server[3020]: Exiting
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3046]: OpenVPN 2.1_rc11 i486-pc-linux-gnu [SSL] [LZO2] [EPOLL] [PKCS11] built on Sep 18 2008
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3046]: NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x.  Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3046]: Diffie-Hellman initialized with 1024 bit key
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3046]: WARNING: file 'VPNSERVER10.key' is group or others accessible
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3046]: /usr/bin/openssl-vulnkey -q -b 1024 -m <modulus omitted>
Jun  7 20:37:23 VPNSERVER10 kernel: [ 9441.448614] tun0: Disabled Privacy Extensions
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3046]: TLS-Auth MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ]
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3046]: ROUTE default_gateway=192.168.0.1
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3046]: TUN/TAP device tun0 opened
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3046]: TUN/TAP TX queue length set to 100
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3046]: /sbin/ifconfig tun0 10.8.0.1 pointopoint 10.8.0.2 mtu 1500
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3046]: /sbin/route add -net 10.8.0.0 netmask 255.255.255.0 gw 10.8.0.2
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3046]: Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3053]: Socket Buffers: R=[111616->131072] S=[111616->131072]
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3053]: UDPv4 link local (bound): [undef]:1194
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3053]: UDPv4 link remote: [undef]
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3053]: MULTI: multi_init called, r=256 v=256
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3053]: IFCONFIG POOL: base=10.8.0.4 size=62
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3053]: IFCONFIG POOL LIST
Jun  7 20:37:23 VPNSERVER10 ovpn-server[3053]: Initialization Sequence Completed
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: MULTI: multi_create_instance called
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: 192.168.0.11:60410 Re-using SSL/TLS context
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: 192.168.0.11:60410 LZO compression initialized
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: 192.168.0.11:60410 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ]
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: 192.168.0.11:60410 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: 192.168.0.11:60410 Local Options hash (VER=V4): '530fdded'
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: 192.168.0.11:60410 Expected Remote Options hash (VER=V4): '41690919'
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: 192.168.0.11:60410 TLS: Initial packet from 192.168.0.11:60410, sid=070be60e e605f3d3
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: 192.168.0.11:60410 VERIFY OK: depth=1, /C=FR/ST=IDF/L=GLR/O=HOME/CN=VPNSERVER10/emailAddress=clement.paulet@free.fr
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: 192.168.0.11:60410 VERIFY OK: depth=0, /C=FR/ST=IDF/L=GLR/O=HOME/CN=clement/emailAddress=clement.paulet@free.fr
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: 192.168.0.11:60410 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: 192.168.0.11:60410 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: 192.168.0.11:60410 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: 192.168.0.11:60410 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: 192.168.0.11:60410 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: 192.168.0.11:60410 [clement] Peer Connection Initiated with 192.168.0.11:60410
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: clement/192.168.0.11:60410 MULTI: Learn: 10.8.0.6 -> clement/192.168.0.11:60410
Jun  7 20:38:26 VPNSERVER10 ovpn-server[3053]: clement/192.168.0.11:60410 MULTI: primary virtual IP for clement/192.168.0.11:60410: 10.8.0.6
Jun  7 20:38:28 VPNSERVER10 ovpn-server[3053]: clement/192.168.0.11:60410 PUSH: Received control message: 'PUSH_REQUEST'
Jun  7 20:38:28 VPNSERVER10 ovpn-server[3053]: clement/192.168.0.11:60410 SENT CONTROL [clement]: 'PUSH_REPLY,route 192.168.0.0 255.255.255.0,dhcp-option DNS 192.168.0.5,dhcp-option DOMAIN Home.Local,route 10.8.0.0 255.255.255.0,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5' (status=1)

if config après :
 
 
VPNSERVER10usr/share/doc/openvpn/examples/easy-rsa/2.0# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:15:5d:00:05:11
          inet addr:192.168.0.30  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::215:5dff:fe00:511/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19173 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13703 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:16745035 (15.9 MiB)  TX bytes:1589675 (1.5 MiB)
          Interrupt:9 Base address:0xec00
 
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1232 (1.2 KiB)  TX bytes:1232 (1.2 KiB)
 
tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:10.8.0.1  P-t-P:10.8.0.2  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 B)  TX bytes:588 (588.0 B)
 
ifconfig avant :
VPNSERVER10usr/share/doc/openvpn/examples/easy-rsa/2.0# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:15:5d:00:05:11
          inet addr:192.168.0.30  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::215:5dff:fe00:511/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19207 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13744 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:16748464 (15.9 MiB)  TX bytes:1595215 (1.5 MiB)
          Interrupt:9 Base address:0xec00
 
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1232 (1.2 KiB)  TX bytes:1232 (1.2 KiB)
 
tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:10.8.0.1  P-t-P:10.8.0.2  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 B)  TX bytes:588 (588.0 B)