vpn

[bonkel]

Wer nutzt es?

was braucht man dafür? ich mein ausser das tun.ko modul

[santa]

Guck mal hier.
http://www.hdmedia-universe.com/board/showthread.php?p=11471

[KleinerSchelm]

in den neuen spark7162 image sollte tun.ko un die entsprechenden /dev angelegt sein.

deshalb brauch man mal einen der vpn nutzt

[Alex-2.5]

Vielen Dank!!! :o

Edit. Und funktioniert auch

[santa]

Nur jetzt dem bonkel noch verraten was ins image muss

[Alex-2.5]

Unter Plugins ist eine kurze beschreibung. Openvpn Plugin Seite 2 ganz unten.
Hier nochmals:

liblzo2.so.2 - nach /lib/
openvpn - nach /usr/bin/ (rechte 755)
openvpn.sh - wohin man will z.b. /etc/init.d/ (rechte 755)

neustarten (kann man auch zum erstmaligen starten hernehmen)

/etc/init.d/openvpn.sh restart

Dateien im Anhang.

Configs werden in /etc/openvpn gesucht. Also alles was .conf ist wird versucht zu starten.

[Alex-2.5]

in den neuen spark7162 image sollte tun.ko un die entsprechenden /dev angelegt sein.

deshalb brauch man mal einen der vpn nutzt

ich war mit der aussage das es geht wohl viel zu schnell :)
Ab welcher Build sollte dann das tun.ko drin sein? Oder besser gefragt, ist diese schon online oder kommt die noch?
In der "HDMU_1152_E2_spark7162_210_git_4676_nodebug_nolcd_ Diff3_ffm_Flash" ist es jedenfalls doch nicht. Hier war wohl doch mein altes tun.ko drin welches zwar fehler bringt aber dennoch geladen wurde.

[KleinerSchelm]

hast du noch eine bsp. config für leute die noch nie sowas gemacht haben. was so als basis rein soll ?

[Alex-2.5]

wenn man einen server hat mit dem man sich verbinden will müssen dort die zertifikate gebaut werden.
soll der receiver der server sein so muss dieser dann die zertifikate bauen.
bei mir ist eben ein kleiner thin client server. so kann ich mich damit in mein heimisches netzwerk verbinden ohne von irgendwelchen blockern (z.b. im büro) genervt zu werden.

aber um auch wirklich antwort zu geben :) :

server.conf sample:



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

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


client.conf sample:

##############################################
# 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 my-server-1 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 nobody

# 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 client.crt
key client.key

# Verify server certificate by checking
# that the certicate has the nsCertType
# field set to "server". 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 nsCertType
# field set to "server". The build-key-server
# script in the easy-rsa folder will do this.
;ns-cert-type 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 x

# 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

P.S. ich werde nach den nötigen dateien die als default nach /etc/openvpn/ sollten suchen, damit kann man dann zertifikate für clients erstellen.

[madie]

Hatten wir beide das nicht im AAF auch gebaut? Wie war das da gelöst? Weisst du das noch?

[Alex-2.5]

Genau madie, das waren wir beide.

Da war es im autostart. (usercmd.sh)
jedoch klappt das nur solange, wie kein neuer kernel das image einnimmt. denn dann müsste man die tun.ko tauschen im IPK.

[Alex-2.5]

So, nun hier noch was wie ich finde als default nach /etc/openvpn rein sollte wenns ein plugin wird.

damit kann man dann zertifikate erstellen. jedoch weis ich nicht ob openssl installiert ist im image, das ist meines wissens nach nötig.

[bonkel]

das heisst man braucht eine

client.conf
ca.crt
client.cri
client.key
? is das so richtig?

[bonkel]

wobei das mit der keyerstellung ja ohne openssl nich klappt...
geht das auch am pc dann ? muss ja... andere machens ja auch so , so wie ich das rauslese

[Alex-2.5]

ja genau. also wichtig ist das die eben passend am server und client liegen. sind ja sicherheitszertifikate.
geht natürlich am PC auch, bzw. VPN-Server.

wobei der name nicht unbedingt client.conf ist.
irgendwas.conf wird mit dem openvpn.sh gestartet. also wenn man meherere verbindungen hat, auch kein thema, die werden alle gestartet und sind dann als virtuelle netzwerkadapter (tun oder tap) zu finden mit ifconfig.

[bonkel]

gut dann reicht es doch so...


reicht doch dann wenn ich ein start stop ins hdmu center bring...und es automatisch startet :)

[Alex-2.5]

genau das reicht locker :)

und evtl noch eine ausgabe "ifconfig" wäre super in dem menü.
für dich eine kleinigkeit, bin ich mir sicher :)

also es wäre gut, ein autostart / start / stop / restart.
wobei start / stop und restart ja nur hinter das openvpn.sh gesetzt werden muss.
also z.b.
/etc/init.d/openvpn.sh start
/etc/init.d/openvpn.sh stop
/etc/init.d/openvpn.sh restart

das 'restart' oder auch das 'start' könnte man dann in den autostart setzten wenn das machbar ist.

und damit man nicht immer einen PC braucht wäre eine screen ausgabe von ifconfig eben super damit man sieht ob man verbunden ist oder nicht.

[bonkel]

autostart punkt fällt ganz weg...das soll automatisch gehen wenn man start macht, ist bei dlna server auch so..


was gibt denn ifconfig aus
wenn vpn an ist..kannst man beispiel posten..

[Alex-2.5]

Klar. also ifconfig gibt logischerweise eth0 und lo aus und dann eben noch tun bzw tap.

Hier ein beispiel mit mehreren geladenen .conf :



eth0 Link encap:Ethernet HWaddr 00:1C:B9:03:1A:97
inet addr:192.168.178.3 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8611 errors:0 dropped:0 overruns:0 frame:0
TX packets:5946 errors:1 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:1331256 (1.2 MiB) TX bytes:501855 (490.0 KiB)
Interrupt:133

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

tap0 Link encap:Ethernet HWaddr 5E:A4:2C:65:A5:42
inet addr:10.3.1.2 Bcast:10.3.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

tap1 Link encap:Ethernet HWaddr 25:AB:53:51:66:B2
inet addr:11.3.1.3 Bcast:11.3.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:216 (216.0 B) TX bytes:0 (0.0 B)

tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:19.4.0.34 P-t-P:19.4.0.33 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

[bonkel]

das heisst , wenn openvpn läuft sind tap/tun da , wenn nicht, nich?

[Alex-2.5]

genau.

das tun/tap wird nur gezeigt wenn auch eine verbindung zum server besteht.

[bonkel]

das ist gut ...dann kann ich das missbrauchen für ne anzeige obs läuft oder nicht :D

[Alex-2.5]

kann dann gerne das fertige testen ;)