Então, estou querendo adicionar meu PI de framboesa à minha VPN doméstica e fiz a mesma configuração dos meus outros clientes para o meu PI e ele se conecta, obtém um endereço IP da rede remota. O engraçado é que, a partir do PI após a conexão, ele não pode pingar o servidor VPN, que é 192.168.0.13 nem nada na rede remota (dispositivos domésticos), mas pode pingar meu gateway doméstico, que é 192.168 .0.1.
Coisas que eu já tentei:
tap0 com a métrica 100. OUTPUT chain em IPTABLES
.ovpn para corresponder exatamente à configuração na minha máquina de trabalho do Ubuntu. Eu não acho que nada esteja errado com a configuração do servidor, já que eu tenho uma máquina Windows e Ubuntu conectada agora e ambos podem fazer ping através da VPN de ambos os modos perfeitamente bem.
Rede de trabalho: 192.168.212.0/24
Rede remota / residencial / VPN: 192.168.0.0/24
PI Config
##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server. #
# #
# This configuration can be used by multiple #
# clients, however 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 are a client and that we
# will be pulling certain config file directives
# from the server.
client
# Use the same setting as you are using on
# the server.
# 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,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap
# Are we connecting to a TCP or
# UDP server? Use the same setting as
# on the server.
proto tcp
;proto udp
# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote home.com 1194
;remote my-server-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 server. Very useful
# on machines which are 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 nogroup
# Try to preserve some state across restarts.
persist-key
persist-tun
# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here. See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]
# Wireless networks often produce a lot
# of duplicate packets. Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings
# SSL/TLS parms.
# See the server config file for more
# description. It's best to use
# a separate .crt/.key file pair
# for each client. A single ca
# file can be used for all clients.
ca ca.crt
cert tunnelpi.crt
key tunnelpi.key
# Verify server certificate by checking that the
# certicate has the correct key usage set.
# 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 server certificates with the keyUsage set to
# digitalSignature, keyEncipherment
# and the extendedKeyUsage to
# serverAuth
# EasyRSA can do this for you.
remote-cert-tls server
# If a tls-auth key is used on the server
# then every client must also have the key.
tls-auth ta.key 1
# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
cipher AES-128-CBC
auth SHA256
key-direction 1
# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
comp-lzo
# Set log file verbosity.
verb 3
# Silence repeating messages
;mute 20
script-security 2
up /etc/openvpn/update-resolv-conf
down /etc/openvpn/update-resolv-conf
Rotas PI
default via 192.168.212.1 dev eth0
192.168.0.0/24 via 192.168.0.1 dev tap0 proto dhcp metric 150
192.168.0.0/24 dev tap0 proto kernel scope link src 192.168.0.177 metric 208
192.168.212.0/24 dev eth0 proto kernel scope link src 192.168.212.45 metric 100
Interfaces PI
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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 b8:27:eb:29:02:18 brd ff:ff:ff:ff:ff:ff
inet 192.168.212.45/24 brd 192.168.212.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::ba27:ebff:fe29:218/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether b8:27:eb:7c:57:4d brd ff:ff:ff:ff:ff:ff
8: tap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 100
link/ether 86:2b:bf:6d:32:f6 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.177/24 brd 192.168.0.255 scope global tap0
valid_lft forever preferred_lft forever
inet6 fe80::f6c1:d6f4:d369:5861/64 scope link
valid_lft forever preferred_lft forever
PI IPTABLES
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT icmp -- anywhere anywhere
Este é realmente bizarro e eu não tenho certeza se isso é apenas um problema de Raspbian ou estou faltando alguma coisa?
Obrigado pela ajuda