Thanks for the quick response. The journalctl tool is certainly powerful and useful. I'll have to spend some time learning its tricks. Here is the output:
I can see it is timing out but can't see why this is happening all of a sudden.
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)
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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT DEBIAN
shorewall6-tunnels
SHOREWALL6-TUNNELS(5) [FIXME: manual] SHOREWALL6-TUNNELS(5)NAME
tunnels - Shorewall6 VPN definition file
SYNOPSIS
/etc/shorewall6/tunnels
DESCRIPTION
The tunnels file is used to define rules for encapsulated (usually encrypted) traffic to pass between the Shorewall6 system and a remote
gateway. Traffic flowing through the tunnel is handled using the normal zone/policy/rule mechanism. See
http://www.shorewall.net/VPNBasics.html for details.
The columns in the file are as follows (where the column name is followed by a different name in parentheses, the different name is used in
the alternate specification syntax).
TYPE -
{ipsec[:{noah|ah}]|ipsecnat|gre|l2tp|pptpclient|pptpserver|{openvpn|openvpnclient|openvpnserver}[:{tcp|udp}][:port]|generic:protocol[:port]}
Types are as follows:
ipsec - IPv6 IPSEC
ipsecnat - IPv6 IPSEC with NAT Traversal (UDP port 4500 encapsulation)
gre - Generalized Routing Encapsulation (Protocol 47)
l2tp - Layer 2 Tunneling Protocol (UDP port 1701)
openvpn - OpenVPN in point-to-point mode
openvpnclient - OpenVPN client runs on the firewall
openvpnserver - OpenVPN server runs on the firewall
generic - Other tunnel type
If the type is ipsec, it may be followed by :ah to indicate that the Authentication Headers protocol (51) is used by the tunnel (the
default is :noah which means that protocol 51 is not used). NAT traversal is only supported with ESP (protocol 50) so ipsecnat tunnels
don't allow the ah option (ipsecnat:noah may be specified but is redundant).
If type is openvpn, openvpnclient or openvpnserver it may optionally be followed by ":" and tcp or udp to specify the protocol to be
used. If not specified, udp is assumed. Note: At this writing, OpenVPN does not support IPv6.
If type is openvpn, openvpnclient or openvpnserver it may optionally be followed by ":" and the port number used by the tunnel. if no
":" and port number are included, then the default port of 1194 will be used. . Where both the protocol and port are specified, the
protocol must be given first (e.g., openvpn:tcp:4444).
If type is generic, it must be followed by ":" and a protocol name (from /etc/protocols) or a protocol number. If the protocol is tcp
or udp (6 or 17), then it may optionally be followed by ":" and a port number.
ZONE - zone
The zone of the physical interface through which tunnel traffic passes. This is normally your internet zone.
GATEWAY(S) (gateway or gateways) - address-or-range [ , ... ]
The IP address of the remote tunnel gateway. If the remote gateway has no fixed address (Road Warrior) then specify the gateway as
::/0. May be specified as a network address and if your kernel and ip6tables include iprange match support then IP address ranges are
also allowed.
Beginning with Shorewall 4.5.3, a list of addresses or ranges may be given. Exclusion (shorewall6-exclusion[1] (5) ) is not supported.
GATEWAY ZONE(S) (gateway_zone or gateway_zones) - [zone[,zone]...]
Optional. If the gateway system specified in the third column is a standalone host then this column should contain a comma-separated
list of the names of the zones that the host might be in. This column only applies to IPSEC tunnels where it enables ISAKMP traffic to
flow through the tunnel to the remote gateway(s).
EXAMPLE
Example 1:
IPSec tunnel.
The remote gateway is 2001:cec792b4:1::44. The tunnel does not use the AH protocol
#TYPE ZONE GATEWAY
ipsec:noah net 2002:cec792b4:1::44
Example 2:
Road Warrior (LapTop that may connect from anywhere) where the "gw" zone is used to represent the remote LapTop
#TYPE ZONE GATEWAY GATEWAY ZONES
ipsec net ::/0 gw
Example 3:
Host 2001:cec792b4:1::44 is a standalone system connected via an ipsec tunnel to the firewall system. The host is in zone gw.
#TYPE ZONE GATEWAY GATEWAY ZONES
ipsec net 2001:cec792b4:1::44 gw
Example 4:
OPENVPN tunnel. The remote gateway is 2001:cec792b4:1::44 and openvpn uses port 7777.
#TYPE ZONE GATEWAY GATEWAY ZONES
openvpn:7777 net 2001:cec792b4:1::44
Example 8:
You have a tunnel that is not one of the supported types. Your tunnel uses UDP port 4444. The other end of the tunnel is
2001:cec792b4:1::44.
#TYPE ZONE GATEWAY GATEWAY ZONES
generic:udp:4444 net 2001:cec792b4:1::44
FILES
/etc/shorewall6/tunnels
SEE ALSO
http://shorewall.net/configuration_file_basics.htm#Pairs
shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5), shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5),
shorewall6-maclist(5), shoewall6-netmap(5),shorewall6-params(5), shorewall6-policy(5), shorewall6-providers(5), shorewall6-rtrules(5),
shorewall6-routestopped(5), shorewall6-rules(5), shorewall6.conf(5), shorewall6-secmarks(5), shorewall6-tcclasses(5),
shorewall6-tcdevices(5), shorewall6-tcrules(5), shorewall6-tos(5), shorewall6-zones(5)NOTES
1. shorewall6-exclusion
http://www.shorewall.net/manpages6/shorewall6-exclusion.html
[FIXME: source] 06/28/2012 SHOREWALL6-TUNNELS(5)