Openvpn conecta mas nao navega

1. Openvpn conecta mas nao navega

dj tornados
djtornados

(usa Fedora)

Enviado em 06/06/2012 - 22:16h

salve a todos da comunidade
eu criei uma vpn com openvpn no fedora para 3 socios ter acesso de fora
a vpn conecta pinga o server mas nao navega uma obs. no windows da como rede nao identificada em propriedades so aprece ip da vpn e dns

segue configuração do server vpn:

#################################################
# 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 keys/ca.crt
cert keys/matriz.crt
key keys/matriz.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 keys/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.1.0 255.255.255.0"
#ush "default-gateway 10.8.0.1"
#push "route 192.168.1.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 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 208.67.222.222"
push "dhcp-option DNS 208.67.220.220"

# 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 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 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



obs este sever esta com firewall + squid segue iptables



# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*nat
:OUTPUT ACCEPT [0:0]
:PREROUTING ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
-A POSTROUTING -o eth1 -j MASQUERADE
# Forward HTTP connections to Squid proxy
-A PREROUTING -p tcp -m tcp -i p5p1 --dport 80 -j REDIRECT --to-ports 3128
COMMIT
*filter
:FORWARD ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -p tcp -m tcp --dport 10000:10010 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 30000:30010 -j ACCEPT
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p udp -i eth1 --dport 1194 -j ACCEPT
-A INPUT -i tun+ -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 9101 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 9102 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 9103 --state NEW -j ACCEPT
-A INPUT -p udp -m state -m udp --dport 10080 --state NEW -j ACCEPT
-A INPUT -p udp -m udp -m state --dport 631 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 9102 --state NEW -j ACCEPT
-A INPUT -p udp -m state -m udp --dport 137 --state NEW -j ACCEPT
-A INPUT -p udp -m state -m udp --dport 138 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 25 --state NEW -j ACCEPT
-A INPUT -p tcp -m tcp -m state --dport 53 --state NEW -j ACCEPT
-A INPUT -p udp -m state -m udp --dport 53 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 21 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 16509 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 16514 --state NEW -j ACCEPT
-A INPUT -p tcp -m tcp -m state --dport 993 --state NEW -j ACCEPT
-A INPUT -p ah -j ACCEPT
-A INPUT -p esp -j ACCEPT
-A INPUT -p udp -m state -m udp --dport 500 --state NEW -j ACCEPT
-A INPUT -p udp -m state -m udp -d 224.0.0.251 --dport 5353 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 2049 --state NEW -j ACCEPT
-A INPUT -p udp -m state -m udp --dport 1194 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 995 --state NEW -j ACCEPT
-A INPUT -p udp -m state -m udp --dport 1812 --state NEW -j ACCEPT
-A INPUT -p udp -m state -m udp --dport 1813 --state NEW -j ACCEPT
-A INPUT -p udp -m state -m udp --dport 5404 --state NEW -j ACCEPT
-A INPUT -p udp -m state -m udp --dport 5405 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 11111 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 21064 --state NEW -j ACCEPT
-A INPUT -p udp -m state -m udp --dport 137 --state NEW -j ACCEPT
-A INPUT -p udp -m state -m udp --dport 138 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 139 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 445 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 631 --state NEW -j ACCEPT
-A INPUT -p udp -m state -m udp --dport 631 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 22 --state NEW -j ACCEPT
-A INPUT -p udp -m state -m udp --dport 69 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 80 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 443 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 10000 --state NEW -j ACCEPT
-A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
-A FORWARD -p icmp -j ACCEPT
-A FORWARD -i lo -j ACCEPT
-A FORWARD -o eth1 -j ACCEPT
-A FORWARD -i tun+ -j ACCEPT
-A FORWARD -i p5p1 -o tun+ -j ACCEPT
-A FORWARD -m state -i eth1 -o tun+ --state ESTABLISHED,RELATED -j ACCEPT
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
-A INPUT -p tcp -m tcp -m state --dport 3128 --state NEW -j ACCEPT
-A INPUT -p udp -m udp -m state --dport 53 --state NEW -j ACCEPT
-A INPUT -p udp -m udp -m state --dport 1701 --state NEW -j ACCEPT
-A INPUT -p tcp -m tcp -m state --dport 1701 --state NEW -j ACCEPT
-A INPUT -p tcp -m tcp -m state --dport 1723 --state NEW -j ACCEPT
-A INPUT -p udp -m udp -m state --dport 1723 --state NEW -j ACCEPT
-A INPUT -p udp -m udp -m state --dport 1433 --state NEW -j ACCEPT
-A INPUT -p tcp -m tcp -m state --dport 1433 --state NEW -j ACCEPT
-A INPUT -p tcp -m tcp -m state --dport 3306 --state NEW -j ACCEPT
-A INPUT -p udp -m udp -m state --dport 3306 --state NEW -j ACCEPT
-A INPUT -p udp -m udp -m state --dport 5432 --state NEW -j ACCEPT
-A INPUT -p tcp -m tcp -m state --dport 5432 --state NEW -j ACCEPT
-A INPUT -p tcp -m tcp -m state --dport 8008 --state NEW -j ACCEPT
-A INPUT -p udp -m udp -m state --dport 8008 --state NEW -j ACCEPT
-A INPUT -p udp -m udp -m state --dport 23 --state NEW -j ACCEPT
-A INPUT -p tcp -m tcp -m state --dport 23 --state NEW -j ACCEPT
-A INPUT -p tcp -m tcp -m state --dport 8080 --state NEW -j ACCEPT
-A INPUT -p udp -m udp -m state --dport 8080 --state NEW -j ACCEPT
-A INPUT -p udp -m udp -m state --dport 22 --state NEW -j ACCEPT
-A INPUT -p tcp -m tcp -m state --dport 22 --state NEW -j ACCEPT
-A INPUT -p tcp -m tcp --dport 5000:5200 -j ACCEPT
-A INPUT -p tcp -m tcp -m state --dport 1194 --state NEW -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
COMMIT
# Generated by webmin
*mangle
:FORWARD ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:PREROUTING ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
COMMIT
# Completed


estou ficando doido e nao acho onde estou errando se puderem me ajudar desde ja agradeço a todos


  


2. Re: Openvpn conecta mas nao navega

Cristiano Gomes
cristianovicosa

(usa Debian)

Enviado em 07/06/2012 - 00:04h

Ola!
Explica direito seus objetivos. Está vpn vai servir para acesso a internet ou apenas para acesso ao servidor da empresa?


3. Re: Openvpn conecta mas nao navega

dj tornados
djtornados

(usa Fedora)

Enviado em 07/06/2012 - 12:39h

bom dia este sever hoje é trabalhao como proxysquid, frirewall , e dados oque os socios querem é acessar seus arquivos banco de dados etc quando estiverem fora da empresa.


4. Re: Openvpn conecta mas nao navega

Cristiano Gomes
cristianovicosa

(usa Debian)

Enviado em 07/06/2012 - 13:26h

Certo parcceiro. Preciso de mais detalhes, tipo, eles vão acessar o servidor via ssh, outro computador da rede via vnc ou TS. Coloque o maximo de detalhes que você puder pra podermos colocar uma resposta boa pra você.


5. Re: Openvpn conecta mas nao navega

dj tornados
djtornados

(usa Fedora)

Enviado em 07/06/2012 - 13:43h

Bem eles apenas querem ter acesso aos arquivos e banco de dados determinado pelo adm, eles nao vao ter acesso a mais pela vpn obs no clinte windows eu instalei o openvpn gui e coloquei os arquivos de configuracao rodei a vpn no cliente windows ele conecta sem problema mas da como rede nao identificada ai nem mapiando unidade o windows consegue acesso mas seu deer um ping no ip do sever pela vpn ele respode


6. Re: Openvpn conecta mas nao navega

Cristiano Gomes
cristianovicosa

(usa Debian)

Enviado em 07/06/2012 - 15:29h

Boa tarde!
Estes arquivos estão no servidor da vpn?
Eles são acessador pelo samba ou outro serviço?
O banco de dados, o que é? Mysql, mdb oracle ? Como vão acesa-lo? por um software?

Não consegui analizar seu firewall, por que trabalho um pouco diferente, mas pelo que você disse, sua vpn está ok, falta apenas um meio de acesso a estes arquivos ou falta liberar alguma porta no firewall. Não se esqueça que a interface de sua VPN no servidor é tun0 ou tun1 e assi por diante e não eth.., por tanto você deve tratar assin no firewall.

Qualquer coisa, posta ai.



7. Re: Openvpn conecta mas nao navega

dj tornados
djtornados

(usa Fedora)

Enviado em 07/06/2012 - 15:45h

ate agora oque foi me passado é pelo samba, postsql e maysql que estao no mesmo servidor
quanto ao firewall pode ter algo errado pois estou criando tudo isto na cara e a coragem e estudo na escola google se estiver errado fica avontade para falar ou ate mesmo criticar, criticas construtivas é sempre bem vinda.



8. Re: Openvpn conecta mas nao navega

Cristiano Gomes
cristianovicosa

(usa Debian)

Enviado em 07/06/2012 - 16:58h

Boa tarde parceiro.
Com relação o firewall, aconselho pesquizar aqui no volume, tem muito conteudo.

Com relação a acessar arquivos pelo samba, se o link de internet das duas pontas não forem bons, você terá sérios problemas de desempenho. Para esta tarefa voce deve usar Rdesktop, se os arquivos dos ditos sócios forem arquivos tipo de word, excel, corel e outro dependetes do windows, ai você precisa montar um servidor windows de terminal e redirecionar no seu firewall. Neste caso talvez nem precise de VPN.

Tenho vários clientes usando estas estruturas e posso afirmar que cada caso é um caso.Você precisa conhecer bem os objetivos e projetar.

Estamos aqui para ajudar. Fique a vontade para perguntar.


9. Re: Openvpn conecta mas nao navega

dj tornados
djtornados

(usa Fedora)

Enviado em 07/06/2012 - 17:25h

ok me explica para que serve openvpn pois oque vi ate agora é para poder interligar redes como se uma só inclusive a maior parte dos arquivos que estao dando exemplos de compartilhamento linux windos com openvpn


10. Re: Openvpn conecta mas nao navega

Cristiano Gomes
cristianovicosa

(usa Debian)

Enviado em 07/06/2012 - 20:11h

Olá!
Serve para varios fins, vou te dar um exemplo:

Temos em uma ponta uma matriz:

Servidor debian, conectado com a internet, servindo de firewall, proxy e outros.
Estações de trabalho com windows xp
Uma impressora matricial ligada a uma estação de trabalho.

Temos na outra ponta uma filial:

Modem de ADSL roteado.
Estaçoes de trabalho windows xp.
Uma impressora laser ligada a uma estação de trabalho.

Então configuramos o servidor da matriz para ser um servidor de VPN, alem de suas outras funções.

E m seguida configuramos os clientes de VPN nas estações da filial para conectar no servidor da matriz.

Dai criamos algumas rotas e as maquinas da matriz poderam entrar na rede das maquinas da filial pegar arquivos(se as internets forem fracas, fica um pouco lento). Podemos também da matriz imprimir na filia e da filial na matriz.


11. Re: Openvpn conecta mas nao navega

dj tornados
djtornados

(usa Fedora)

Enviado em 07/06/2012 - 20:34h

ok e oque eu toquerendo é que quem tiver na rua com seu not consiga estar na rede como se estivese presente na empresa pegar e colocar arquivo imprimir etc.
obs. a principio a ideia é que eles possam conectar de cada ai todos os links sao de 10 megas.


12. Re: Openvpn conecta mas nao navega

Cristiano Gomes
cristianovicosa

(usa Debian)

Enviado em 07/06/2012 - 21:12h

Bom agora sabemos o que você quer

Tem material aquino Volume.

Olhe este artigo.
http://www.vivaolinux.com.br/artigo/OpenVPN-Instalacao-e-configuracao?pagina=1






Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts