10-23-2012
ikn3, thanks a lot for the hint.
'ping -I eth0 ip' is not working.
'ping -I eth1 ip' is working.
How do I determine which interface is the default one that ping uses?
Thanks!
10 More Discussions You Might Find Interesting
1. IP Networking
We are unable to bring one of our linux boxes into the network once it was restarted. But once we stop and start the network service. We are able to ping the gateway and get into network. After a minute or two we get the following reponse for the ping command
64 bytes from 124.168.215.40:... (6 Replies)
Discussion started by: chrisanto_2000
6 Replies
2. IP Networking
Hello this is my first post at this forum.
Apologize for my lack of network understanding
but Im posting to learn.
I have a problem reaching default gateway 10.18.110.1
If I use my laptop I can ping 10.18.110.1 but with our red hat multihomed server the gateway does not respond to ping.
cat... (11 Replies)
Discussion started by: vettec3
11 Replies
3. Solaris
I was install new solaris10 on m4000 model after that i "ping -s" to default gateway but it's take longtime (2 Min) to reply and if i use "ping" only it's reply to fase(2 sec). any body who can tell me about my problem and how to fix it please. i'm try to fix several days. (2 Replies)
Discussion started by: cesmk
2 Replies
4. AIX
Hello,
I am new to Unix :D and have been trying to configure an AIX server running 5.3. I used smitty or smit to configure interface 0 on the server. I am able to ping the IP I set, however I am still unable to ping the gateway. I configured the IP by navigating to Communications Applications... (6 Replies)
Discussion started by: cdub50
6 Replies
5. Red Hat
I know the subject line is very similar to: destination host unreachable
but the problem with my machine appears to be somewhat different from that thread. apologies if I missed something from there.
We recently moved a machine physically and from one subnet to another . I used... (1 Reply)
Discussion started by: mirage
1 Replies
6. UNIX for Dummies Questions & Answers
I have NCR MP-RAS unix. I have been trying for several months to get our network working since we had never used it before. I have setup all routes that I can think of. I know it has something to do with the routing table, because out of sheer luck I was able to get it working, and than like a... (4 Replies)
Discussion started by: Rutgerncas
4 Replies
7. AIX
I just reinstalled a fresh install of 5300 07 on an old 44p model 170, after installing I set an IP Address on en2 and I tried to the ping default gateway, no response. I tried a
startsrc -g tcpip
... and then I can ping the default gateway. I broke the ping and tried again to ping. I cannot... (1 Reply)
Discussion started by: asyed123
1 Replies
8. AIX
Hi,
I installed AIX 7.1 on a blade though (hmc with vio). I can ping the IP address, but not the gateway. Is there anything that I should configure?
Is there anything that I have to check with vio setting or Am I missing any configuration?
Please let me know further.
Thank you (5 Replies)
Discussion started by: pjeedu2247
5 Replies
9. UNIX for Advanced & Expert Users
I have setup a Linux machine on my server but for some reason Im unable to reach my default gateway. This is causing me to not communicate with the outside world (unable to connect to CentOS repos)
# ifconfig
enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet... (3 Replies)
Discussion started by: Junaid Subhani
3 Replies
10. UNIX for Beginners Questions & Answers
Dear friends
I use RedHat 6.5, which sets the gateway in the configuration file / etc / sysconfig / network as GATEWAY = 192.168.1.26, and the gateway in the configuration file / etc / sysconfig / network-scripts / ifcfg-eth11 as GATEWAY = 192.168.1.256. The two gateways are different.... (6 Replies)
Discussion started by: tanpeng
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)