Sponsored Content
Top Forums Programming How detect TCP/IP socket shutdown when ethernet cable is disconnected Post 302435857 by Corona688 on Thursday 8th of July 2010 10:42:48 AM
Old 07-08-2010
TCP does best-effort delivery, which is why it has such obnoxiously long timeouts. I've seen it survive 10-minute network outages. It's really not designed to do what you want. Try pinging your host to see if it responds or not.
 

10 More Discussions You Might Find Interesting

1. Solaris

Monitor displays Cable disconnected

Hi all This is my first post in this forums. I hope some one can help me with this my Sun Ultra 60 worked fine couple of months back when i used a dell (1280x1024). i move to a MN last month n bought a new sony monitor with (1280x1024) but when i connect it to the box it monitor displays... (1 Reply)
Discussion started by: venuavula
1 Replies

2. Programming

can-not detect TCP disconnects well

Hello everyone. Thanks for reading. I am using Ubuntu 7.04 to experience this problem: I have written my own programs that communicate to eachother and I am having a hard time detecting a TCP socket disconnect when the remote side's computer has a power-failure (for example). On the computer... (6 Replies)
Discussion started by: pjwhite
6 Replies

3. Red Hat

[RHEL4.5] server shutdown when I unplug the ethernet cable

hi.. I unplug my eth0 lan cable.. and suddenly my system shutdown... no idea :eek::confused: (3 Replies)
Discussion started by: flekzout
3 Replies

4. IP Networking

How to handle unplugging ethernet cable in socket programming

Hi, I am trying to implement a server-client socket communication. My server and clients are in different PCs. During communications if the ethernet cable is removed from the server side it shows broken pipe due to unable to write on the socket. I want to know how to check whether the ethernet... (0 Replies)
Discussion started by: JagadishB
0 Replies

5. IP Networking

Two Servers via ethernet crossover cable

Hi, I'm trying to communicate two servers (HP DLProliant 380 G5) via a crossover cable, but I don't get them to ping each other. I am working in RHEL 4. These are the steps I've performed: 1) Plugged the crossover cables in eth2. (note: The cable is brand new. Also I built one myself... (3 Replies)
Discussion started by: jrodriguez365
3 Replies

6. UNIX for Dummies Questions & Answers

How to change ethernet cable of iscsi initiator (iscsi client)?

how to change ethernet cable of iscsi initiator (iscsi client) (0 Replies)
Discussion started by: pankajd
0 Replies

7. AIX

How to detect the network cable status with c programming on AIX

Hello, Is there any API or any other approach to detect whether the network cable is connected to the network adapter, say, en0, en1 or en2? The OS is AIX6.1. Thank you. (4 Replies)
Discussion started by: zephyrbj
4 Replies

8. Programming

[C++] [Unix] TCP non-blocking. Detect server disconnection procedure over, from client.

Hello! I searched forum for similar topic, with no luck, if you know one, delete this topic, and send me private message with link please. Little background: I have a lot of clients and one serwer. Client can make multiple connections on different ports and ips, but only one can be acctive... (2 Replies)
Discussion started by: ikeban
2 Replies

9. IP Networking

Packets sent from Linux TCP socket

Hello, Our software is using a TCP socket (AF_INET, SOCK_STREAM) to communicate with an Ethernet device. When we send a message, the message object writes itself in full onto the socket's stream buffer before the software invokes send() from socket.h. I'm still researching, but have 2... (1 Reply)
Discussion started by: bix_20002000
1 Replies

10. IP Networking

Detect Socket timeout in tcpdump capture

Hello, I detect these errors in my logs : Socket timeout calling url http://server:port/bla/soap/selfcare/infoRapide] Unable to make proxyRequest I've made a tcpdump capture this way : tcpdump -i eth0 -s 0 -w /app/captura.pcap port 8080 But I'm fairly new in reading .pcap files with... (0 Replies)
Discussion started by: black_fender
0 Replies
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)
All times are GMT -4. The time now is 04:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy