SourceForge.net staff have launched a new Site Status page which provides regular updates regarding our ongoing datacenter migration to Chicago, scheduled downtimes, unplanned outages, and new feature launches. See it at: https://sourceforge.net/sitestatus/
Hi @all,
I try to connect 2 LANs with IPSec/Openswan
LAN 1: 192.168.0.0/24
LAN 2: 192.168.1.0/24
This is my Config:
conn HomeVPN # # Left security gateway, subnet behind it, nexthop toward right. left=192.168.1.29 ... (1 Reply)
Q: "Does Cisco 1921 router support,, act as an endpoint for, site to site VPNs using IPSec? If so, how many? "
A: If you get the Cisco 1921/k9 with the security services bundle then it will have built in security features. Cisco, typically includes IP Sec tunnels I believe as part of that... (0 Replies)
Hi,
I am trying to establish vpn between my linux server and cisco asa at client side.
I installed openswan on my cent os.
Linux Server
eth0 - 182.2.29.10
Gateway - 182.2.29.1
eth1 - 192.9.200.75
I have simple IPtables Like
WAN="eth0"
LAN="eth1" (0 Replies)
Hello, I am interested in getting the correct date and time. In Solaris, the "date" command will show me the information but only on the local system. I recall there's a command in Solaris that will extract the date and time from a website, such as Google or Yahoo.
If you know how to do this,... (1 Reply)
Setup a site to site VPN between two cisco routers.
One of the site locations is unable to access ports such as https://example.com:9001
How do I let them go into port 9001?
They can ssh, ftp, telnet and everything else.
Is this a VPN issue or ACL access issue?
I put
permit ip host... (0 Replies)
GSSAPI::Status(3pm) User Contributed Perl Documentation GSSAPI::Status(3pm)NAME
GSSAPI::Status - methods for handlings GSSAPI statuses
SYNOPSIS
use GSSAPI;
$status = GSSAPI::Status->new(GSS_S_COMPLETE, 0);
if (GSS_ERROR($status->major)) {
die "a horrible death";
}
if (! $status) { # another way of writing the above
die "a horrible death";
}
$status = $some_GSSAPI->someop($args1, etc);
if ($status) {
foreach ($status->generic_message, $status->specific_message) {
print "GSSAPI error: $_
";
}
die "help me";
}
DESCRIPTION
"GSSAPI::Status" objects are returned by most other GSSAPI operations. Such statuses consist of a GSSAPI generic code and, for most
operations, a mechanism specific code. These numeric codes can be accessed via the methods "major" and "minor". The standard textual
messages that go with the current status can be obtained via the "generic_message" and "specific_message" methods. Each of these returns a
list of text which should presumably be displayed in order.
The generic code part of a GSSAPI::Status is composed of three subfields that can be accessed with the "GSS_CALLING_ERROR",
"GSS_ROUTINE_ERROR", and "GSS_SUPPLEMENTARY_INFO" functions. The returned values can be compared against the constants whose names start
with "GSS_S_" if your code wants to handle particular errors itself. The "GSS_ERROR" function returns true if and only if the given
generic code contains neither a calling error nor a routine error.
When evaluated in a boolean context, a "GSSAPI::Status" object will be true if and only if the major status code is "GSS_S_COMPLETE".
When evaluated in a string contect, a "GSSAPI::Status" object will return the generic and specific messages all joined together with
newlines. This may or may not make "die $status" work usefully.
BUGS
The base objects are currently implmented as a blessed C structure containing the major and minor status codes. It should probably be a
blessed array or hash instead, thereby cutting down on the amount of C code involved and making it more flexible.
AUTHOR
Philip Guenther <pguen@cpan.org>
SEE ALSO perl(1) RFC2743
perl v5.14.2 2008-02-02 GSSAPI::Status(3pm)