07-13-2011
[Help] - 2 VM solaris pingable
Hi,
I have 2 VM of Solaris ( 2nd one full clone )
1st VM - 192.168.1.30
2nd VM - 192.168.1.31
My need : ping both VM from each other
I have added host entry in /etc/hosts of both server but unable to ping each other from solaris console...
Pls advice
5 More Discussions You Might Find Interesting
1. IP Networking
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... (1 Reply)
Discussion started by: jjinno
1 Replies
2. Shell Programming and Scripting
Hi,
need to write a script which will check number of ip address are able to ping or not .. (2 Replies)
Discussion started by: mail2sant
2 Replies
3. Solaris
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... (7 Replies)
Discussion started by: sankasu
7 Replies
4. UNIX for Dummies Questions & Answers
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
... (6 Replies)
Discussion started by: brian112
6 Replies
5. Shell Programming and Scripting
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...... (8 Replies)
Discussion started by: vivek d r
8 Replies
LEARN ABOUT DEBIAN
vde_tunctl
VDE_TUNCTL(8) System Manager's Manual VDE_TUNCTL(8)
NAME
vde_tunctl -- create and manage persistent TUN/TAP interfaces
SYNOPSIS
vde_tunctl [-f tun-clone-device] [-u owner] [-t device-name]
vde_tunctl [-f tun-clone-device] -d device-name
DESCRIPTION
vde_tunctl allows the host sysadmin to preconfigure a TUN/TAP device for use by a particular user. That user may open and use the device,
but may not change any aspects of the host side of the interface.
vde_tunctl is a simple copy of tunctl done for practical purposes.
USAGE
To create an interface for use by a particular user, invoke tunctl without the -d option:
# vde_tunctl -u someuser
Set 'tap0' persistent and owned by uid 500
Then, configure the interface as normal:
# ifconfig tap0 192.168.0.254 up
# route add -host 192.168.0.253 dev tap0
# bash -c 'echo 1 > /proc/sys/net/ipv4/conf/tap0/proxy_arp'
# arp -Ds 192.168.0.253 eth0 pub
To delete the interface, use the -d option:
# vde_tunctl -d tap0
Set 'tap0' nonpersistent
SEE ALSO
vde_switch(1) vde_plug2tap(1)
AUTHOR
tunctl was written by Jeff Dike jdike@karaya.com
This manual page is based on tunctl manual page written by Matt Zimmerman mdz@debian.org for the Debian GNU/Linux system.
VDE_TUNCTL(8)