06-10-2002
hi
do u have firwall sort of thing , within ur network!!!
u tried pinging?
try tht.
raju
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi All,
I have written a script called findwho.sh
findwho.sh in Development Server
========
who -M>x
I want to copy the file findwho.sh
into Production Server and
run this script on it then output file x copy
back to the Development Server
1) Every time ftp findwho.sh to... (4 Replies)
Discussion started by: krishna
4 Replies
2. Shell Programming and Scripting
Now my task is
there are two servers A and B.
i only can put unix script in server A and database is on server B.
can I write a script in serer A which could telnet to server B and run the script which include sql script and save the output file in server A.
did I make my problem clear? (2 Replies)
Discussion started by: YoYo
2 Replies
3. Programming
hello sir and all my friends
i have a serious problems in creating a telnet protocol with c-program in unix. if any one have this program then please reply me on this mail address.
email address removed (4 Replies)
Discussion started by: abhijit deka
4 Replies
4. AIX
I have some AIX 4.3 machines which have disabled root telnet access.
When you run su - once logged on the machine requests a password and if one is supplied correctly it asks for another users password.
How do I configure this?
Any help is appreciated.
Thank you (0 Replies)
Discussion started by: uXion
0 Replies
5. SCO
Hello.
How can I limit the number of telnet connections in order that from the same IP address it can support at the maximun two simultaneus meetings on SCO Openserver 5.0.7 ?
Thanks. (2 Replies)
Discussion started by: jag
2 Replies
6. Shell Programming and Scripting
Somewhat long story:
I have a simple Perl CGI script that uses Expect to Telnet to a device and grab some data, and then spits it back to Perl for display on the Webpage.
This works for many devices I've tried, but one device just fails, it keeps rejecting the password on this device, only... (1 Reply)
Discussion started by: jondo
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I was writing one script which includes to switch to the another telnet automatically from the present telnet server. I was using rlogin but firstly it takes the same user name of the present telnet and secondly it is prompting for the password.
But i want to switch to the another telnet... (2 Replies)
Discussion started by: Prateek
2 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I want to know the difference between these two services. Both are under xinetd. Both are used for enabling and disabling Telnet service. So, can somebody please explain me the difference between the two ?
Thanks in advance :) (0 Replies)
Discussion started by: kashifsd17
0 Replies
9. Shell Programming and Scripting
Hi,
Need some help on exiting the telnet session from the script.
#!/bin/ksh
telnet <ip>
it would print some text and
it would ask for a username and pwd.
I jus need to capture the text and i need to come out of the telnet session.
is it possible without expect ? (6 Replies)
Discussion started by: giri_luck
6 Replies
10. IP Networking
Hey everyone. Something has been bothering me. The telnet program, while I know is insecure, offers a ton of functionality. I can literally test any port's availability. I can send commands to web servers, and email servers, and it's a great toubleshooting tool. can any of this be done with SSH?... (6 Replies)
Discussion started by: Lost in Cyberia
6 Replies
LEARN ABOUT DEBIAN
iodine-client-start
IODINE-CLIENT-START(8) System Administration Utilities IODINE-CLIENT-START(8)
NAME
iodine-client-start - start an iodine IPv4-over-DNS tunnel
SYNOPSIS
iodine-client-start [option]
DESCRIPTION
'iodine-client-start' starts an iodine IP-over-DNS tunnel.
-h, --help
Print help and exit
-v, --version
Print version info and exit
Invoking the program without options attempts to set up and configure an iodine IP-over-DNS tunnel using the configuration in the file
/etc/default/iodine-client or by querying the user. It tries to figure out the right way to set things up by observing the network, and if
all else fails by guessing.
QUICK CONFIGURATION
Put two lines in the file /etc/default/iodine-client
subdomain=your.tunnel.sub.domain
passwd=password_for_that_tunnel
or invoke the script with those environment variables set:
env subdomain=xxx passwd=xxx iodine-client-start
If these are not set, the script will query the user for them.
DETAILS
The configuration file consists of lines which are either comments starting with '#', or settings of the form VAR="val". Valid VARs are:
subdomain
Sample value: your.tunnel.sub.domain (no default, must be set)
passwd
Sample value: password_for_that_tunnel (no default, must be set)
testhost
Hostname to ping when testing if network is working (default: slashdot.org)
bounce_localnet
Take the local network down and then up again before starting tunnel (default: false)
test_ping_localnet
Test if the local network is working by pinging the gateway (default: true)
test_ping_tunnel
Test if the iodine tunnel is working after it has been set up by pinging the host at the other end (default: true)
test_ping_final
Test if the tunnel is working after everything is ostensibly set up by trying to ping an external host (default: true)
default_router
IP address of router on the local network---should be found automatically, set this if that fails and the program guesses wrong.
interface
Interface to use (e.g., eth1, eth0, etc) for connection to DNS server used for the iodine tunnel---should be found automatically,
set this if that fails and the program guesses wrong.
mtu
Set if tunnel MTU needs to be manually changed (lowered). Should not be necessary anymore, as recent versions of iodine negotiate an
appropriate MTU during tunnel setup. But if that negotiation does not happen, or if you are using an older version of iodine, the
default tunnel MTU is 1024, and if the local DNS server restricts to 512 byte packets you might need to use an MTU of 220.
skip_raw_udp_mode
Set "-r" option in iodine command line. With this option, iodine does not try to establish a direct UDP socket to the iodine server
on port 53. (default: true).
continue_on_error
Set if the script should continue even if a command fails. Use to test script when running as non-root. Defaults to false if run-
ning as root, true otherwise.
iodine-client-start 1.0.4 June 2014 IODINE-CLIENT-START(8)