Ping Tunnel 0.7 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Ping Tunnel 0.7 (Default branch)
# 1  
Old 01-14-2009
Ping Tunnel 0.7 (Default branch)

Ping Tunnel is a tool for reliably tunneling TCP connections over ICMP echo request and reply packets (commonly known as ping requests and replies). It is useful for evading firewalls that, for whatever reason, prevent outgoing TCP connections, but allow in- and outgoing ICMP packets. The tunnel works by having a proxy run on a machine ping-able from the inside of the firewall, with the client running on the local machine from which TCP access is required.License: BSD License (revised)Changes:
This release adds support for syslog and compilation on Windows. It also enables tunneling over UDP port 53, and fixes a few minor bugs (in particular, ptunnel should no longer crash due to failed DNS lookups).Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Programming

Ping test sends mail when ping fails

help with bash script! im am working on this script to make sure my server will stay online, so i made this script.. HOSTS="192.168.138.155" COUNT=4 pingtest(){ for myhost in "$@" do ping -c "$COUNT" "$myhost" &&return 1 done return 0 } if pingtest $HOSTS #100% failed... (4 Replies)
Discussion started by: mort3924
4 Replies

2. Ubuntu

VPN tunnel to UDP tunnel

I have a program which uses TCP connection for VPN tunnel. How do i Change TCP tunnel to UDP tunnel?.. (1 Reply)
Discussion started by: sahithi
1 Replies
Login or Register to Ask a Question
RMCPING(8)						      System Manager Commands							RMCPING(8)

NAME
rmcpping - send RMCP Ping to network hosts SYNOPSIS
rmcpping [OPTION...] destination DESCRIPTION
rmcpping uses the RMCP Ping request datagram to elicit an RMCP Pong response from a remote host. The utility can be used to verify if a remote host supports RMCP or IPMI. The initial starting sequence number will be randomized. rmcpping will return 0 to the environment if it receives atleast 1 response from the remote host. Otherwise, it exits with a value of 1. OPTIONS
The following options are available -h Output help menu. -V Output version. -c count Stop after sending count packets. -i interval Wait interval seconds between sending each packet. The default is to wait for one second between each packet. -I interface address Set source address to specified interface address. Argument may be numeric IP address or name of device. -t timeout Time to wait for a response, in seconds. Default is five seconds. -v Verbose output. -s num Specify an initial starting sequence number. The default is to use a random initial sequence number. -d Turn on debugging. KNOWN ISSUES
It has been observed that some remote BMCs can get "confused" and delay packet responses if duplicate packets (with duplicate sequence num- bers) are sent in succession very quickly. There is no known way to cleanly deal with a "confused" BMC other than the wait awhile. Unlike ping(8), local network devicess (e.g. 127.0.0.1) cannot be "pinged". REPORTING BUGS
Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>. COPYRIGHT
Copyright (C) 2007-2012 Lawrence Livermore National Security, LLC. Copyright (C) 2003-2007 The Regents of the University of California. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version. ORIGIN
Command and manpage based off ping(8). SEE ALSO
freeipmi(7), ping(8), ipmiping(8) http://www.gnu.org/software/freeipmi/ rmcpping 1.1.5 2012-06-15 RMCPING(8)