openVPN как точка доступа

[DZ333817]

Здравствуйте,
Помогите разобраться,
Есть прямой ip дома на роутере, в его локалке поставил сервер на Ubuntu (ip - 192.168.1.5) и поднял openvpn (ну и порт пробросил). но сейчас openvpn создает еще одну подсеть (10.8.0.x). может ли openvpn работать в режиме точки доступа, не создавая своей подсети, а отдавать их роутеру ? Чтоб те кто подключались к vpn получали ip от роутера (типа 192.168.1.x) и оказывались в моей локалке ?
спасибо =)

[fisher74]

А прямой IP это как?

Код: [Выделить]

server-bridge 192.168.1.5 255.255.255.0 192.168.1.64 192.168.168.127

Пользователь решил продолжить мысль 01 Ноября 2015, 19:22:42:ну и не забываем про

Код: [Выделить]

sudo apt-get install bridge-utils

[DZ333817]

Здравствуйте,
Ну, прямой - это я так реальный/постоянный обозвал

а можно вопрос про строчку
server-bridge 192.168.1.5 255.255.255.0 192.168.1.64 192.168.168.127
последний ip точно 192.168.168.127 , а не 192.168.1.127


первое - это ip сервера в локалке роутера
второе - маска (в данном случае все возможные 192.168.1.xxx)
третий - откуда начинать ?
четвертый -

Он же по идее ничего раздавать не должнен (раздавать же должен будет роутер). или я не прав ?
спасибо

[fisher74]

Да, с последним параметром промахнулся, извините.

1 - да
2 - да
3 - первый адрес выделенный для VPN
4 - последний адрес выделенный VPN

всё он должен раздавать, в DHCP-сервере локалки эти адреса нужно исключать из пула.

[DZ333817]

Спасибо
при первой попытке запуска в логах openvpn вылезло:
Options error: --server-bridge directive only makes sense with --dev tap
Use --help for more information.
как я понял,  для режима bribge, надо использовать  dev tap, а не dev tun, поменял.

включил  в /etc/sysctl.conf  net.ipv4.ip_forward = 1 

сейчас соединение устанавливается, инета и локалки не видно, логи пустые, но при попытке ping ya.ru, пакеты не ходят, но вижу  (213.180.193.3) 56(84) bytes of data.  Значит, DNS-ки он уже видит

Я настраивал по этой статье (https://rusadmin.biz/rukovodstva/openvpn-na-debian/). Тут все про режим dev tun, который теперь не использую. Заранее извиняюсь за глупые вопросы...

надо ли добавлять что-то в iptables по аналогии со статьей автора, мне надо добавить что-то типа
iptables -A FORWARD -i eth0 -o tun0 tap -m state --state ESTABLISHED,RELATED -j ACCEPT ?

сервер пока поставил на 192.168.1.50, порт 8989, вот весь конфиг

Код: [Выделить]

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

# 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 server.crt
key 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 dh2048.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 192.168.1.50 255.255.255.0 192.168.1.73 192.168.1.83

# 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.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
# 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-256-CBC   # AES
;cipher DES-EDE3-CBC  # Triple-DES
auth SHA512

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

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

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


[fisher74]

по аналогии со статьей автора, мне надо добавить что-то типа

Это зависит от текущей политики безопасности шлюза, но вектор мыслей верный (только интерфейс не ограничивается лишь буквенной аббревиатурой)

вот весь конфиг

Конфиг не смотрел

[DZ333817]

значит, думаю, надо так ?
iptables -A FORWARD -i eth0 -o tap0 -m state --state ESTABLISHED,RELATED -j ACCEPT

[fisher74]

зависит от текущей политики безопасности шлюза

[DZ333817]

Ну, это для дома, не думаю, что мой сервер кому-то сильно интересен. VPN сделал по ключам, с tls, но без пароля.

Еще вот вопрос мучает, если есть ip-tv приставка, завязанная на определенного провайдера, который у меня дома, то будет ли она работать, например у другого человека, если его роутер подключить по VPN к моему ? =)))

[fisher74]

ДАже "для дома" существует политика безопасности, даже если Вы про неё ничего не знаете.

А по IP-TV - это зависит от технологии услуги.

[DZ333817]

А вы не могли бы в двух словах описать, чем плоха данная строчка?  я только недавно в этой среде... а чтоб не было желания решить все по простому, снес винду на ноуте, и осваиваю Ubuntu теперь и на ноуте =)))

вам спасибо большое за подсказки =)

[fisher74]

Где я сказал, что она плоха? Её отношение к "тёмным" или "светлым" можно определить только по месту приложения.

Я к тому что нельзя рассматривать состоятельность одного правила netfilter, не зная всего их списка и структуры сети (хотя бы основных моментов: интерфейсы, маршруты).

[DZ333817]

прописал эту строчку, но все равно, сеть устанавлмвается, но локальной сети и инета нет =(
Пользователь решил продолжить мысль 03 Ноября 2015, 14:23:50:Ну хоть логи писаться стали
Так, для справки, по логу... у себя в host назвал свой сервер h.dz для  192.168.1.50 (чтоб постоянно ip руками не вбивать), а 83.149.9.113 - ip-шки мегафона (использую тел. для раздачи инета, чтоб тестировать удаленное подключение).

Код: [Выделить]

Tue Nov  3 14:08:08 2015 OpenVPN 2.3.2 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [eurephia] [MH] [IPv6] built on Dec  1 2014
Tue Nov  3 14:08:08 2015 NOTE: when bridging your LAN adapter with the TAP adapter, note that the new bridge adapter will often take on its own IP address that is different from what the LAN adapter was previously set to
Tue Nov  3 14:08:08 2015 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.
Tue Nov  3 14:08:08 2015 Diffie-Hellman initialized with 2048 bit key
Tue Nov  3 14:08:08 2015 Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Tue Nov  3 14:08:08 2015 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Tue Nov  3 14:08:08 2015 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Tue Nov  3 14:08:08 2015 Socket Buffers: R=[212992->131072] S=[212992->131072]
Tue Nov  3 14:08:08 2015 TUN/TAP device tap0 opened
Tue Nov  3 14:08:08 2015 TUN/TAP TX queue length set to 100
Tue Nov  3 14:08:08 2015 GID set to nogroup
Tue Nov  3 14:08:08 2015 UID set to nobody
Tue Nov  3 14:08:08 2015 UDPv4 link local (bound): [undef]
Tue Nov  3 14:08:08 2015 UDPv4 link remote: [undef]
Tue Nov  3 14:08:08 2015 MULTI: multi_init called, r=256 v=256
Tue Nov  3 14:08:08 2015 IFCONFIG POOL: base=192.168.1.73 size=11, ipv6=0
Tue Nov  3 14:08:08 2015 Initialization Sequence Completed
Tue Nov  3 14:11:55 2015 83.149.9.113:16395 TLS: Initial packet from [AF_INET]83.149.9.113:16395, sid=2c09e8b1 745ae727
Tue Nov  3 14:11:56 2015 83.149.9.113:16395 VERIFY OK: depth=1, C=US, ST=CA, L=SanFrancisco, O=Fort-Funston, OU=MyOrganizationalUnit, CN=Fort-Funston CA, name=EasyRSA, emailAddress=me@myhost.mydomain
Tue Nov  3 14:11:56 2015 83.149.9.113:16395 VERIFY OK: depth=0, C=US, ST=CA, L=SanFrancisco, O=Fort-Funston, OU=MyOrganizationalUnit, CN=h.dz, name=EasyRSA, emailAddress=me@myhost.mydomain
Tue Nov  3 14:11:56 2015 83.149.9.113:16395 WARNING: 'dev-type' is used inconsistently, local='dev-type tap', remote='dev-type tun'
Tue Nov  3 14:11:56 2015 83.149.9.113:16395 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1634', remote='link-mtu 1602'
Tue Nov  3 14:11:56 2015 83.149.9.113:16395 WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1532', remote='tun-mtu 1500'
Tue Nov  3 14:11:56 2015 83.149.9.113:16395 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Tue Nov  3 14:11:56 2015 83.149.9.113:16395 Data Channel Encrypt: Using 512 bit message hash 'SHA512' for HMAC authentication
Tue Nov  3 14:11:56 2015 83.149.9.113:16395 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Tue Nov  3 14:11:56 2015 83.149.9.113:16395 Data Channel Decrypt: Using 512 bit message hash 'SHA512' for HMAC authentication
Tue Nov  3 14:11:56 2015 83.149.9.113:16395 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA
Tue Nov  3 14:11:56 2015 83.149.9.113:16395 [h.dz] Peer Connection Initiated with [AF_INET]83.149.9.113:16395
Tue Nov  3 14:11:56 2015 h.dz/83.149.9.113:16395 MULTI_sva: pool returned IPv4=192.168.1.73, IPv6=(Not enabled)
Tue Nov  3 14:11:59 2015 h.dz/83.149.9.113:16395 PUSH: Received control message: 'PUSH_REQUEST'
Tue Nov  3 14:11:59 2015 h.dz/83.149.9.113:16395 send_push_reply(): safe_cap=940
Tue Nov  3 14:11:59 2015 h.dz/83.149.9.113:16395 SENT CONTROL [h.dz]: 'PUSH_REPLY,route-gateway 192.168.1.50,ping 10,ping-restart 120,ifconfig 192.168.1.73 255.255.255.0' (status=1)
Tue Nov  3 14:12:00 2015 h.dz/83.149.9.113:16395 MULTI: Learn: 40:00:40:11:1b:95 -> h.dz/83.149.9.113:16395
Tue Nov  3 14:12:00 2015 h.dz/83.149.9.113:16395 MULTI: Learn: 40:00:40:06:f3:06 -> h.dz/83.149.9.113:16395
Tue Nov  3 14:12:00 2015 h.dz/83.149.9.113:16395 MULTI: Learn: 40:00:40:06:f3:05 -> h.dz/83.149.9.113:16395
Tue Nov  3 14:12:00 2015 h.dz/83.149.9.113:16395 MULTI: Learn: 40:00:40:11:44:2f -> h.dz/83.149.9.113:16395
Tue Nov  3 14:12:00 2015 h.dz/83.149.9.113:16395 MULTI: Learn: 40:00:40:11:58:70 -> h.dz/83.149.9.113:16395
Tue Nov  3 14:12:00 2015 h.dz/83.149.9.113:16395 MULTI: Learn: 40:00:40:06:f3:04 -> h.dz/83.149.9.113:16395
Tue Nov  3 14:12:00 2015 h.dz/83.149.9.113:16395 MULTI: Learn: 40:00:40:11:b6:be -> h.dz/83.149.9.113:16395
Tue Nov  3 14:12:01 2015 h.dz/83.149.9.113:16395 MULTI: Learn: 40:00:40:11:f9:90 -> h.dz/83.149.9.113:16395
Tue Nov  3 14:12:01 2015 h.dz/83.149.9.113:16395 MULTI: Learn: 40:00:40:06:f2:b9 -> h.dz/83.149.9.113:16395
Tue Nov  3 14:12:01 2015 h.dz/83.149.9.113:16395 MULTI: Learn: 40:00:40:11:4d:0d -> h.dz/83.149.9.113:16395
Tue Nov  3 14:12:01 2015 h.dz/83.149.9.113:16395 MULTI: Learn: 40:00:40:11:9f:34 -> h.dz/83.149.9.113:16395
Tue Nov  3 14:12:01 2015 h.dz/83.149.9.113:16395 MULTI: Learn: 40:00:40:11:23:c8 -> h.dz/83.149.9.113:16395
Tue Nov  3 14:12:01 2015 h.dz/83.149.9.113:16395 MULTI: Learn: 40:00:40:11:68:57 -> h.dz/83.149.9.113:16395
Tue Nov  3 14:12:02 2015 h.dz/83.149.9.113:16395 MULTI: Learn: 40:00:40:11:f6:e9 -> h.dz/83.149.9.113:16395
Tue Nov  3 14:12:02 2015 h.dz/83.149.9.113:16395 MULTI: Learn: 40:00:40:11:1a:90 -> h.dz/83.149.9.113:16395
и так далее... =(

[fisher74]

нельзя рассматривать состоятельность одного правила netfilter, не зная всего их списка и структуры сети (хотя бы основных моментов: интерфейсы, маршруты).

Код: [Выделить]

ip a; ip r
nslookup ya.ru
nslookup ya.ru 8.8.8.8c сервера и клиентов

с сервера так же sudo iptables-save

[DZ333817]

С сервера

Код: [Выделить]

root@dz-srv:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 1c:6f:65:20:c6:b7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.50/24 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fdaf:f068:b220:0:d8ef:928f:6887:da98/64 scope global temporary dynamic
       valid_lft 583316sec preferred_lft 64316sec
    inet6 fdaf:f068:b220:0:8c8:6381:495b:62bf/64 scope global temporary deprecated dynamic
       valid_lft 497519sec preferred_lft 0sec
    inet6 fdaf:f068:b220:0:d914:2d19:49b8:5a60/64 scope global temporary deprecated dynamic
       valid_lft 411721sec preferred_lft 0sec
    inet6 fdaf:f068:b220:0:1e6f:65ff:fe20:c6b7/64 scope global dynamic
       valid_lft 4294944768sec preferred_lft 4294944768sec
    inet6 fe80::1e6f:65ff:fe20:c6b7/64 scope link
       valid_lft forever preferred_lft forever
6: tap0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 100
    link/ether ce:49:e9:99:e6:f4 brd ff:ff:ff:ff:ff:ff

root@dz-srv:~# ip r
default via 192.168.1.1 dev eth0  proto static
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.50  metric 1

root@dz-srv:~# nslookup ya.ru
Server:         127.0.1.1
Address:        127.0.1.1#53

Non-authoritative answer:
Name:   ya.ru
Address: 213.180.193.3
Name:   ya.ru
Address: 93.158.134.3
Name:   ya.ru
Address: 213.180.204.3

root@dz-srv:~# nslookup ya.ru 8.8.8.8
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   ya.ru
Address: 213.180.193.3
Name:   ya.ru
Address: 213.180.204.3
Name:   ya.ru
Address: 93.158.134.3


root@dz-srv:~# iptables-save
# Generated by iptables-save v1.4.21 on Tue Nov  3 21:06:54 2015
*filter
:INPUT ACCEPT [19824804:1774540951]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [10931802:2504017733]
-A FORWARD -i eth0 -o tap0 -m state --state RELATED,ESTABLISHED -j ACCEPT
COMMIT
# Completed on Tue Nov  3 21:06:54 2015





С клиента

Код: [Выделить]

dz@dz-nb:~ > ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether ac:22:0b:07:21:c0 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:15:00:b9:88:1d brd ff:ff:ff:ff:ff:ff
    inet 192.168.43.19/24 brd 192.168.43.255 scope global wlan0
       valid_lft forever preferred_lft forever
    inet6 fe80::215:ff:feb9:881d/64 scope link
       valid_lft forever preferred_lft forever
4: tun0@NONE: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 100
    link/none
    inet 192.168.1.73/24 brd 192.168.1.255 scope global tun0
       valid_lft forever preferred_lft forever
dz@dz-nb:~ > ip r
default dev tun0  proto static
192.168.1.0/24 dev tun0  proto kernel  scope link  src 192.168.1.73
192.168.43.0/24 dev wlan0  proto kernel  scope link  src 192.168.43.19  metric 9
213.141.141.xxx (мой ip-роутера, я закрою, на всякий случай) via 192.168.43.1 dev wlan0  proto static

dz@dz-nb:~ > nslookup ya.ru
Server:         127.0.1.1
Address:        127.0.1.1#53

Non-authoritative answer:
Name:   ya.ru
Address: 213.180.193.3
Name:   ya.ru
Address: 93.158.134.3
Name:   ya.ru
Address: 213.180.204.3

                         
dz@dz-nb:~ > nslookup ya.ru 8.8.8.8
;; connection timed out; no servers could be reached