9 More Discussions You Might Find Interesting
1. IP Networking
Hi.
Can you please help me with a routing problem?
There are 2 networks:
192.168.10.0/24 (eth0)
192.168.11.0/24 (eth0:1)
The default gateway is 192.168.10.1
iPv4 routing is already enabled and working.
With vpnc I've built up an VPN connection and can access my home network... (0 Replies)
Discussion started by: tschmi
0 Replies
2. Cybersecurity
Hey everyone. I have a problem, but it may be my lack of understanding that is the cause. Ok so I attend a technical school, and needless to say there's a lot of wannabe hackers, pranksters and what not.
So from my laptop I'd like to connect to the wireless AP's around campus, but security is a... (1 Reply)
Discussion started by: Lost in Cyberia
1 Replies
3. IP Networking
I have a Cisco 1841 router configured as Easy VPN Server. Here is the configuration of the router:
Cisco# Cisco#show running-config Building configuration... Current configura - Pastebin.com
I have a Centos 5.7 server with installed Cisco VPN client for Linux. The client successfully... (0 Replies)
Discussion started by: rcbandit
0 Replies
4. IP Networking
I was given my pcf file to login to work from home and wanted to use OpenVPN instead of the Cisco VPN client software. Can I use this pcf file with OpenVPN? I attempted to use vpnc:
http://wiki.centos.org/HowTos/vpnc
but it just times out
?? (2 Replies)
Discussion started by: metallica1973
2 Replies
5. SCO
I would like to know if anyone has a way to PRINT TO a printer attached to a Windows 7 PC, from SCO, while logged in via a VPN connection.
I am able to attach to a Samba share on the SCO server for files while attached to the VPN, so I know my Samba is workling - but my print jobs return:
... (2 Replies)
Discussion started by: tbb999
2 Replies
6. Solaris
Hi everyone,
I am hoping anyone of you could help me in this weird problem we have in 1 of our Solaris 10 servers. Lately, we have been having some ftp problems in this server. Though it can ping any server within the network, it seems that it can only ftp to a select few. For most servers, the... (4 Replies)
Discussion started by: labdakos
4 Replies
7. IP Networking
Hello,
I have question about VPN connection thats,
I have two networks
1-Office Network
2-Home Network
both are connected to internet
i have in Office network PPTP VPN Server with real or static ip and on the home network all clients working with local ip
Now ,
I need to connect to... (3 Replies)
Discussion started by: LinuxCommandos
3 Replies
8. Linux
Trying to connect to my companies VPN with vpnc but I keep getting an error that the target failed to respond. I run wireshark and see that my host sends out a few ISAKMP packets but gets no response and gives up.
Any ideas what can cause this to happen? Is there someway that UDP traffic could... (0 Replies)
Discussion started by: osulinux
0 Replies
9. Shell Programming and Scripting
Hi All:
I need a script that can be timed to run every half hour to an hour to run a traceroute through a VPN to test that a connection is still up from a Win XP system. Which would be the best, C++ or Perl and what are some good resources to look at.
(If anyone has a script to do this... (1 Reply)
Discussion started by: maxhewitt
1 Replies
GVPE.OSDEP(5) GNU Virtual Private Ethernet GVPE.OSDEP(5)
NAME
gvpe.osdep - os dependent information
DESCRIPTION
This file tries to capture OS-dependent configuration or build issues, quirks and platform limitations, as known.
TUN vs. TAP interface
Most operating systems nowadays support something called a tunnel-device, which makes it possible to divert IPv4 (and often other
protocols, too) into a user space daemon like gvpe. This is being referred to as a TUN-device.
This is fine for point-to-point tunnels, but for a virtual ethernet, an additional ethernet header is needed. This functionality (called a
TAP device here) is only provided by a subset of the configurations.
On platforms only supporting a TUN-device, gvpe will invoke it's magical ethernet emulation package, which currently only handles ARP
requests for the IPv4 protocol (but more could be added, bu the tincd network drivers might need to be modified for this to work). This
means that on those platforms, only IPv4 will be supported.
Also, since there is no way (currently) to tell gvpe which IP subnets are found on a specific host, you will either need to hardwire the
MAC address for TUN-style hosts on all networks (and avoid ARP altogether, which is possible), or you need to send a packet from these
hosts into the vpn network to tell gvpe the local interface address.
Interface Initialisation
Unless otherwise notes, the network interface will be initialized with the expected MAC address and correct MTU value. With most interface
drivers, this is done by running /sbin/ifconfig, so make sure that this command exists.
Interface Types
native/linux
TAP-device; already part of the kernel (only 2.4+ supported, but see tincd/linux). This is the configuration tested best, as gvpe is being
developed on this platform.
ifname should be set to the name of the network device.
To hardwire ARP addresses, use iproute2 (arp can do it, too):
MAC=fe:fd:80:00:00:$(printf "%02x" $NODEID)
ip neighbour add 10.11.12.13 lladdr $MAC nud permanent dev $IFNAME
tincd/linux
TAP-device; already part of the kernel (2.2 only). See native/linux for more info.
ifname should be set to the path of a tap device, e.g. /dev/tap0. The interface will be named accordingly.
native/cygwin
TAP-device; The TAP device to be used must either be the CIPE driver (http://cipe-win32.sourceforge.net/), or (highly recommended) the
newer TAP-Win32 driver bundled with openvpn (http://openvpn.sf.net/). Just download and run the openvpn installer. The only option you need
to select is the TAP driver.
ifname should be set to the name of the device, found in the registry at (no kidding :):
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlNetwork{4D36E972-E325-11CE-BFC1-08002BE10318}<adapterid>ConnectionName
The MAC address is dynamically being patched into packets and ARP-requests, so only IPv4 works with ARP on this platform.
tincd/bsd
TAP-device, maybe; migth work for many bsd variants.
This driver is a newer version of the tincd/*bsd drivers. It might provide a TAP device, or might not work at all. You might try this
interface type first, and, if it doesn't work, try one of the OS-specific drivers.
tincd/freebsd
TAP-device; part of the kernel (since 4.x, maybe earlier).
ifname should be set to the path of a tap device, e.g. /dev/tap0. The interface will be named accordingly.
These commands might be helpful examples:
ifconfig $IFNAME 10.0.0.$NODEID
route add -net 10.0.0.0 -netmask 255.255.255.0 -interface $IFNAME 10.0.0.$NODEID
tincd/netbsd
TUN-device; The interface is a point-to-point device. To initialize it, you currently need to configure it as a point-to-point device,
giving it an address on your vpn (the exact address doesn't matter), like this:
ifconfig $IFNAME mtu $MTU up
ifconfig $IFNAME 10.11.12.13 10.55.66.77
route add -net 10.0.0.0 10.55.66.77 255.0.0.0
ping -c1 10.55.66.77 # ping once to tell gvpe your gw ip
The ping is required to tell the ARP emulator inside GVPE the local IP address.
ifname should be set to the path of a tun device, e.g. /dev/tun0. The interface will be named accordingly.
tincd/openbsd
TUN-device; already part of the kernel. See tincd/netbsd for more information.
native/darwin
TAP-device;
The necessary kernel extension can be found here:
http://www-user.rhrk.uni-kl.de/~nissler/tuntap/
There are two drivers, the one to use is the "tap" driver. It driver must be loaded before use, read the docs on how to install it as a
startup item.
ifname should be set to the path of a tap device, e.g. /dev/tap0. The interface will be named accordingly.
These commands might be helpful examples:
ifconfig $IFNAME 10.0.0.$NODEID
route add -net 10.0.0.0 -interface $IFNAME 255.255.255.0
tincd/darwin
TUN-device; See tincd/netbsd for more information. native/darwin is preferable.
The necessary kernel extension can be found here:
http://chrisp.de/en/projects/tunnel.html
ifname should be set to the path of a tun device, e.g. /dev/tun0. The interface will be named accordingly.
The driver must be loaded before use:
kmodload tunnel
tincd/solaris
TUN-device; already part of the kernel(?), or available here:
http://vtun.sourceforge.net/tun/
Some precompiled tun drivers might be available here:
http://www.monkey.org/~dugsong/fragroute/
The interface MAC and MTU are NOT set up for you. Please try it out and send me an ifconfig command invocation that does that.
See tincd/netbsd for more information.
Completely untested so far.
tincd/mingw
TAP-device; see native/cygwin for more information.
The setup is likely to be similar to native/cygwin.
Completely untested so far.
tincd/raw_socket
TAP-device; purpose unknown and untested, probably binds itself on an existing ethernet device (given by ifname). It must be down prior to
running the command, and GVPE will try to set it's MAC address and MTU to the "correct" values.
Completely untested so far.
tincd/uml_socket
TAP-device; purpose unknown and untested, probably creates a UNIX datagram socket (path given by ifname) and reads and writes raw packets,
so might be useful in other than UML contexts.
No network interface is created, and the MAC and MTU must be set as appropriate on the other side of the socket. GVPE will exit if the MAC
address doesn't match what it expects.
Completely untested so far.
tincd/cygwin
Known to be broken, use native/cygwin instead.
SEE ALSO
gvpe(5).
AUTHOR
Marc Lehmann <gvpe@schmorp.de>
2.2 2008-09-01 GVPE.OSDEP(5)