[Help] - 2 VM solaris pingable Post: 302538630

5 More Discussions You Might Find Interesting

1. IP Networking

Serious un-pingable stumper of a problem...

I have been busting my head over a network issue at work recently. I believe the problem to be in the L2 domain, but "the powers that be" believe that it looks more like a server port related problem. And the biggest problem of all is that EVERYBODY in the Engineering Department uses this...

2. Shell Programming and Scripting

need to check whether a sever is pingable or not inside the script

Hi, need to write a script which will check number of ip address are able to ping or not ..

3. Solaris

Unable to login using ssh,telnet onto my solaris machine with solaris 10 installed

Hi, I am unable to login into my terminal hosting Solaris 10 and get the below error message "Server refused to allocate pty ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory " Is there anyways i can get into my machine and what kind of changes are required to be...

4. UNIX for Dummies Questions & Answers

host not booting, but is pingable

hi there. im having a problem with a host at the moment, i can ping the host and responds with host is alive. i cannot telnet, rsh or anything else to it... it tells me connection refused. when i run a ckport on it i get answers from : *** successful - smtp *** successful - sunrpc ...

5. Shell Programming and Scripting

validating(pingable or not) remote ip address in shell script

i need to verify whether the ip adress given as input to the shell script is pingable or not... that is whether the ip is alive and responding.. ping $ip_adress the above wont work in script because the execution is continuous... so the shell script keeps will dwell in this pinging process......

LEARN ABOUT SUSE

ipsec_tncfg

IPSEC_TNCFG(8)                                                    [FIXME: manual]                                                   IPSEC_TNCFG(8)

NAME

       ipsec_tncfg - manipulate KLIPS virtual interfaces

SYNOPSIS

       ipsec tncfg
             ipsec tncfg --create virtual
             ipsec tncfg --delete virtual
             ipsec tncfg --attach --virtual virtual --physical physical
             ipsec tncfg --detach --virtual virtual
             ipsec tncfg --clear
             ipsec tncfg --version
             ipsec tncfg --help

OBSOLETE

       Note that tncfg is only supported on the classic KLIPS stack. It is not supported on any other stack and will be completely removed in
       future versions. A replacement command still needs to be designed

DESCRIPTION

       The historical use of tncfg is to attach/detach IPsec virtual interfaces (e.g. ipsec0) to/from physical interfaces (e.g. eth0) through
       which packets will be forwarded once processed by KLIPS.

       The modern use of tncfg is to create and delete virtual interfaces known as mastXXX. mast stands for Mooring and XXX.

       The form with no additional arguments lists the contents of /proc/net/ipsec_tncfg. The format of /proc/net/ipsec_tncfg is discussed in
       ipsec_tncfg(5).

       The --attach form attaches the virtual interface to the physical one.

       The --detach form detaches the virtual interface from whichever physical interface it is attached to.

       The --clear form clears all the virtual interfaces from whichever physical interfaces they were attached to.

       Virtual interfaces typically have names like ipsec0 or mast0 while physical interfaces typically have names like eth0 or ppp0.

EXAMPLES

       ipsec tncfg --create mast12
           creates the mast12 device.

       ipsec tncfg --create ipsec4
           creates an ipsec4 device, but does not attach it.

       ipsec tncfg --attach --virtual ipsec0 --physical eth0
           attaches the ipsec0 virtual device to the eth0 physical device.

FILES

       /proc/net/ipsec_tncfg, /usr/local/bin/ipsec

SEE ALSO

       ipsec(8), ipsec_manual(8), ipsec_eroute(8), ipsec_spi(8), ipsec_spigrp(8), ipsec_klipsdebug(8), ipsec_tncfg(5)

HISTORY

       Written for the Linux FreeS/WAN project <http://www.freeswan.org/> by Richard Guy Briggs.

[FIXME: source]                                                     10/06/2010                                                      IPSEC_TNCFG(8)