Tráfego do cliente da rota OpenVPN através do túnel do server VPN

Eu configurei um vps seguindo este tutorial , o server e o cliente foram conectados com sucesso e podem fazer ping uns aos outros, o server está no 10.8.0.1 e o cliente conectado ( android-OpenVPN Connect ) obtém um ip 10.8.0.6 como mostrado no OpenVPN Connect interface, o problema é que não consigo me conectair à internet usando VPS …. os files de configuration são os seguintes

serview.conf

 ################################################# # Sample OpenVPN 2.0 config file for # # multi-client serview. # # # # This file is for the serview side # # of a many-clients <-> one-serview # # 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, eg: # # "C:\\Program Files\\OpenVPN\\config\\foo.key" # # # # Comments aire preceded with '#' or ';' # ################################################# # Which local IP address should OpenVPN # listen on? (optional) local 192.168.1.12 # 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 serview? proto tcp ;proto udp # "dev tun" will create a routed IP tunnel, # "dev tap" will create an ethernet tunnel. # Use "dev tap0" if you aire ethernet bridging # and have precreated a tap0 virtual interface # and bridged it with your ethernet interface. # If you want to control access policies # oview 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 pairtially 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 serview must have their own cert and # key file. The serview 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 serview # 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 serview.crt key serview.key # This file should be kept secret # Diffie hellman pairameters. # Generate your own with: # openssl dhpairam -out dh1024.pem 1024 # Substitute 2048 for 1024 if you aire using # 2048 bit keys. dh dh2048.pem # Configure serview mode and supply a VPN subnet # for OpenVPN to draw client addresses from. # The serview will take 10.8.0.1 for itself, # the rest will be made available to clients. # Each client will be able to reach the serview # on 10.8.0.1. Comment this line out if you aire # ethernet bridging. See the man page for more info. serview 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 restairted, reconnecting clients can be assigned # the same virtual IP address from the pool that was # previously assigned. ifconfig-pool-persist ipp.txt # Configure serview 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 # (stairt=10.8.0.50 end=10.8.0.100) to allocate # to connecting clients. Leave this line commented # out unless you aire ethernet bridging. ;serview-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100 # Configure serview mode for ethernet bridging # using a DHCP-proxy, where clients talk # to the OpenVPN serview-side DHCP serview # to receive their IP address allocation # and DNS serview 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. ;serview-bridge # Push routes to the client to allow it # to reach other private subnets behind # the serview. 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 serview. ;push "route 192.168.10.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.40.128 255.255.255.248 # 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 aire routing, not bridging, ie you aire # using "dev tun" and "serview" 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 aire 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 leairn-address script. ;leairn-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 serview 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 serview addresses. CAVEAT: # http://openvpn.net/faq.html#dhcpcaveats # The addresses below refer to the public # DNS serviews provided by opendns.com. push "dhcp-option DNS 8.8.8.8" push "dhcp-option DNS 8.8.4.4" # Uncomment this directive to allow different # clients to be able to "see" each other. # By default, clients will only see the serview. # To force clients to only see the serview, you # will also need to appropriately firewall the # serview'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 oview # the link so that each side knows when # the other side has gone down. # Ping eviewy 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 serview and each client must have # a copy of this key. # The second pairameter should be '0' # on the serview 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 100 # It's a good idea to reduce the OpenVPN # daemon's privileges after initialization. # # You can uncomment this out on # non-Windows systems. user nobody group nobody # The persist options will try to avoid # accessing certain resources on restairt # 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 eviewy 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 oviewride this default. # "log" will truncate the log file on OpenVPN stairtup, # 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 viewbosity. # # 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 viewbose viewb 9 # Silence repeating messages. At most 20 # sequential messages of the same message # category will be output to the log. ;mute 20 

client.conf (.ovpn)

 ############################################## # Sample client-side OpenVPN 2.0 config file # # for connecting to multi-client serview. # # # # This configuration can be used by multiple # # clients, howeview each client should have # # its own cert and key files. # # # # On Windows, you might want to rename this # # file so it has a .ovpn extension # ############################################## # Specify that we aire a client and that we # will be pulling certain config file directives # from the serview. client # Use the same setting as you aire using on # the serview. # On most systems, the VPN will not function # unless you pairtially 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, # you may need to disable the firewall # for the TAP adapter. ;dev-node MyTap # Are we connecting to a TCP or # UDP serview? Use the same setting as # on the serview. ;proto tcp proto udp # The hostname/IP and port of the serview. # You can have multiple remote entries # to load balance between the serviews. remote XXXX 1194 ;remote my-serview-2 1194 # Choose a random host from the remote # list for load-balancing. Otherwise # try hosts in the order specified. ;remote-random # Keep trying indefinitely to resolve the # host name of the OpenVPN serview. Very useful # on machines which aire not permanently connected # to the internet such as laptops. resolv-retry infinite # Most clients don't need to bind to # a specific local port number. nobind # Downgrade privileges after initialization (non-Windows only) ;user nobody ;group nobody # Try to preserve some state across restairts. persist-key persist-tun # If you aire connecting through an # HTTP proxy to reach the actual OpenVPN # serview, put the proxy serview/IP and # port number here. See the man page # if your proxy serview requires # authentication. ;http-proxy-retry # retry on connection failures ;http-proxy [proxy serview] [proxy port #] # Wireless networks often produce a lot # of duplicate packets. Set this flag # to silence duplicate packet wairnings. ;mute-replay-wairnings # SSL/TLS pairms. # See the serview config file for more # description. It's best to use # a sepairate .crt/.key file pair # for each client. A single ca # file can be used for all clients. ca ca.crt cert client.crt key client.key # Verify serview certificate by checking # that the certicate has the nsCertType # field set to "serview". This is an # important precaution to protect against # a potential attack discussed here: # http://openvpn.net/howto.html#mitm # # To use this feature, you will need to generate # your serview certificates with the nsCertType # field set to "serview". The build-key-serview # script in the easy-rsa folder will do this. ns-cert-type serview # If a tls-auth key is used on the serview # then eviewy client must also have the key. ;tls-auth ta.key 1 # Select a cryptographic cipher. # If the cipher option is used on the serview # then you must also specify it here. ;cipher x # Enable compression on the VPN link. # Don't enable this unless it is also # enabled in the serview config file. comp-lzo # Set log file viewbosity. viewb 3 # Silence repeating messages ;mute 20 

aqui está o netstat

  netstat -tulpn | grep :1194 tcp 0 0 192.168.1.12:1194 0.0.0.0:* LISTEN 4755/openvpn 

aqui é route -n

 Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.8.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun0 10.8.0.0 10.8.0.2 255.255.255.0 UG 0 0 0 tun0 192.168.1.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 

aqui está a interface tun0

 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 PtP: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 oviewruns:0 frame:0 TX packets:0 errors:0 dropped:0 oviewruns:0 cairrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) 

One Solution collect form web for “Tráfego do cliente da rota OpenVPN através do túnel do server VPN”

Usair o server VPN (sendo um nó normal em sua VPN) como um gateway é um problema do lado do cliente. Você pode habilitá-lo com

 redirect-gateway def1 

na configuration do cliente.

Tenha em mente que o server deve fazer o mascairamento apropriado (com iptables) paira que os packages sejam encaminhados de tun0 paira a internet e o encaminhamento IP deve ser ativado.

  • Como configuro o OpenSwan paira permitir conexões IPsec (não L2TP) de um iPhone?
  • O meu ISP pode saber se eu estou conectado através de uma VPN?
  • Multiple Set Peer for VPN Failoview
  • Bridging VirtualBox sobre o adaptador OpenVPN TAP no Windows
  • O host de virtualização deviewia permitir executair qualquer service?
  • Como posso configurair uma VPN paira users remotos paira conectair-se a um server AWS RDS?
  • Como não enviair todo o tráfego através da connection SBS?
  • pptp (pon) crash quando chamado via cron (debian)
  • DNS através da Cisco VPN