The OpenNET Project / Index page

[ новости /+++ | форум | wiki | теги | ]

форумы  помощь  поиск  регистрация  майллист  вход/выход  слежка  RSS
"Вопрос по Openvpn"
Вариант для распечатки  
Пред. тема | След. тема 
Форумы Открытые системы на сервере (VPN / FreeBSD)
Изначальное сообщение [ Отслеживать ]

"Вопрос по Openvpn"  +/
Сообщение от artemrts (??) on 15-Мрт-10, 16:30 
Имеется тестовая система, на которой я смоделировал такую схему:
- один сервер (FreeBSD) на котором поднят ВПН сервер
- два клиента (Windows XP)
Топология "звезда", т.е. задача обьединить все 3 машины, причем что бы две виндовые машины могли "видеть" друг друга.
  
Конфиг сервера:

# Which local IP address should OpenVPN
# listen on? (optional)
local 192.168.164.140

# 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 /usr/local/etc/openvpn/keys/ca.crt
cert /usr/local/etc/openvpn/keys/server.crt
key /usr/local/etc/openvpn/keys/server.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 /usr/local/etc/openvpn/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 172.16.1.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 172.16.1.1 255.255.255.0 172.16.1.10 172.16.1.20

# 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.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 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
# the TUN/TAP interface to the internet in
# order for this to work properly).
# CAVEAT: May break client's network config if
# client's local DHCP server packets get routed
# through the tunnel.  Solution: make sure
# client's local DHCP server is reachable via
# a more specific route than the default route
# of 0.0.0.0/0.0.0.0.
;push "redirect-gateway"

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses.  CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
;push "dhcp-option DNS 10.8.0.1"
;push "dhcp-option WINS 10.8.0.1"

# 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-server
tls-auth /usr/local/etc/openvpn/keys/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

---

  Клиенты коннектятся к серверу нормально. Пинг есть, но друг друга не пингуют.
  Подскажите как это исправить.

Высказать мнение | Ответить | Правка | Cообщить модератору

Оглавление

Сообщения по теме [Сортировка по времени | RSS]


1. "Вопрос по Openvpn"  +/
Сообщение от reader (ok) on 16-Мрт-10, 10:00 
gateway_enable="YES"

настроить firewall

Высказать мнение | Ответить | Правка | ^ | Наверх | Cообщить модератору

2. "Вопрос по Openvpn"  +/
Сообщение от artemrts (ok) on 16-Мрт-10, 15:59 
>gateway_enable="YES"
>
>настроить firewall

Та это я знаю. Фаервол вообще отключен, т.к. все пока крутится в виртуальной машине.

Еще есть какие догадки?

Высказать мнение | Ответить | Правка | ^ | Наверх | Cообщить модератору

3. "Вопрос по Openvpn"  +/
Сообщение от PJ (ok) on 16-Мрт-10, 17:40 
>>gateway_enable="YES"
>>
>>настроить firewall
>
>Та это я знаю. Фаервол вообще отключен, т.к. все пока крутится в
>виртуальной машине.
>
>Еще есть какие догадки?

таблицы маршрутизации показал бы со всех трёх


Высказать мнение | Ответить | Правка | ^ | Наверх | Cообщить модератору

4. "Вопрос по Openvpn"  +/
Сообщение от artemrts (??) on 16-Мрт-10, 21:50 
>>>gateway_enable="YES"
>>>
>>>настроить firewall
>>
>>Та это я знаю. Фаервол вообще отключен, т.к. все пока крутится в
>>виртуальной машине.
>>
>>Еще есть какие догадки?
>
>таблицы маршрутизации показал бы со всех трёх

Вот предоставляю таблицы маршрутизации.

Поясню.
192.168.164.2 - это адрес шлюза через который работает Интернет виртуальной сети VNWare.
192.168.164.140 - адрес машины на FreeBSD, она же сервер OpenVPN.
192.168.164.130 и 192.168.164.150 - адреса клиентов на ХР.

freebsd1# netstat -rn
Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
default            192.168.164.2      UGS         0        0    le0
127.0.0.1          link#3             UH          0        0    lo0
172.16.1.0/24      link#4             U           0        4   tap0
172.16.1.1         link#4             UHS         0        0    lo0
192.168.164.0/24   link#1             U           2      267    le0
192.168.164.140    link#1             UHS         0        0    lo0

Internet6:
Destination                       Gateway                       Flags      Netif Expire
::1                               ::1                           UH          lo0
fe80::%lo0/64                     link#3                        U           lo0
fe80::1%lo0                       link#3                        UHS         lo0
ff01:3::/32                       fe80::1%lo0                   U           lo0
ff02::%lo0/32                     fe80::1%lo0                   U           lo0

Вот вывод маршрутов первого клиента Win_XP1:

===========================================================================
滿߫¬ ¿¡ΓÑαΣÑ⌐ß«ó
0x1 ........................... MS TCP Loopback interface
0x2 ...00 ff 26 91 ee 1d ...... TAP-Win32 Adapter V8 - ╠ΦφΦ∩ε≡≥ ∩δαφΦ≡εΓ∙ΦΩα ∩αΩσ≥εΓ
0x3 ...00 0c 29 db 41 42 ...... VMware Accelerated AMD PCNet Adapter - ╠ΦφΦ∩ε≡≥ ∩δαφΦ≡εΓ∙ΦΩα ∩αΩσ≥εΓ
===========================================================================
===========================================================================
Активные маршруты:
Сетевой адрес           Маска сети      Адрес шлюза       Интерфейс  Метрика
          0.0.0.0          0.0.0.0    192.168.164.2  192.168.164.130      10
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1      1
       172.16.1.0    255.255.255.0      172.16.1.10     172.16.1.10      30
      172.16.1.10  255.255.255.255        127.0.0.1       127.0.0.1      30
   172.16.255.255  255.255.255.255      172.16.1.10     172.16.1.10      30
    192.168.164.0    255.255.255.0  192.168.164.130  192.168.164.130      10
  192.168.164.130  255.255.255.255        127.0.0.1       127.0.0.1      10
  192.168.164.255  255.255.255.255  192.168.164.130  192.168.164.130      10
        224.0.0.0        240.0.0.0      172.16.1.10     172.16.1.10      30
        224.0.0.0        240.0.0.0  192.168.164.130  192.168.164.130      10
  255.255.255.255  255.255.255.255      172.16.1.10     172.16.1.10      1
  255.255.255.255  255.255.255.255  192.168.164.130  192.168.164.130      1
Основной шлюз:       192.168.164.2
===========================================================================
Постоянные маршруты:
  Отсутствует


Вывод маршрутов второго клиента Win_XP2:

===========================================================================
‘ЇЁб®Є Ё­вҐа䥩ᮢ
0x1 ........................... MS TCP Loopback interface
0x2 ...00 ff 26 91 ee 1d ...... TAP-Win32 Adapter V8 - Минипорт планировщика пакетов
0x3 ...00 0c 29 12 4e ad ...... VMware Accelerated AMD PCNet Adapter - Минипорт планировщика пакетов
===========================================================================
===========================================================================
Активные маршруты:
Сетевой адрес           Маска сети      Адрес шлюза       Интерфейс  Метрика 
          0.0.0.0          0.0.0.0    192.168.164.2  192.168.164.150      10
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1      1
       172.16.1.0    255.255.255.0      172.16.1.11     172.16.1.11      30
      172.16.1.11  255.255.255.255        127.0.0.1       127.0.0.1      30
   172.16.255.255  255.255.255.255      172.16.1.11     172.16.1.11      30
    192.168.164.0    255.255.255.0  192.168.164.150  192.168.164.150      10
  192.168.164.150  255.255.255.255        127.0.0.1       127.0.0.1      10
  192.168.164.255  255.255.255.255  192.168.164.150  192.168.164.150      10
        224.0.0.0        240.0.0.0      172.16.1.11     172.16.1.11      30
        224.0.0.0        240.0.0.0  192.168.164.150  192.168.164.150      10
  255.255.255.255  255.255.255.255      172.16.1.11     172.16.1.11      1
  255.255.255.255  255.255.255.255  192.168.164.150  192.168.164.150      1
Основной шлюз:       192.168.164.2
===========================================================================
Постоянные маршруты:
  Отсутствует

Какие мысли?

Высказать мнение | Ответить | Правка | ^ | Наверх | Cообщить модератору

5. "Вопрос по Openvpn"  +/
Сообщение от PJ (ok) on 17-Мрт-10, 14:14 

>Какие мысли?

http://www.ru.kurlix.de/index.php?option=com_content&task=vi... - смотрели?

А использование tap-устройства принципиально в вашем случае?


Высказать мнение | Ответить | Правка | ^ | Наверх | Cообщить модератору

6. "Вопрос по Openvpn"  +/
Сообщение от artemrts (ok) on 17-Мрт-10, 17:06 
>
>>Какие мысли?
>
>http://www.ru.kurlix.de/index.php?option=com_content&task=vi... - смотрели?
>
>А использование tap-устройства принципиально в вашем случае?

Нет. Эту статью не смотрел. Я так понимаю маршруты не указаны. Сейчас буду ковырять.
А по поводу tap-устройства, желательно что бы по сетевому окружению юзеры ходили.

Высказать мнение | Ответить | Правка | ^ | Наверх | Cообщить модератору

Архив | Удалить

Рекомендовать для помещения в FAQ | Индекс форумов | Темы | Пред. тема | След. тема




Спонсоры:
Inferno Solutions
Hosting by Hoster.ru
Хостинг:

Закладки на сайте
Проследить за страницей
Created 1996-2020 by Maxim Chirkov
Добавить, Поддержать, Вебмастеру