Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

stunc(1) [debian man page]

stunc(1)							  sofia-sip-utils							  stunc(1)

NAME

       stunc - STUN test client.  STUN test client

       Author:
	   Pekka Pessi <Pekka.Pessi@nokia.com>

	   Martti Mela <Martti.Mela@nokia.com>

	   Kai Vehmanen <Kai.Vehmanen@nokia.com>

       Date:
	   Created: Thu Jul 24 17:21:00 2003 ppessi

Synopsis
       stunc [OPTIONS] <stun-server-address>

Description
       The stunc utility can be used to gather information about possible NAT devices that are located between the client and STUN server.

       stunc can provide the following information: the IP address and port as seen by the STUN server, detecting presence of NATs, and hints on
       the type of address translation done. It should be noted that the results of NAT type and life-time detection should be considered as
       hints. There is no guarantee that NAT(s) will handle future packets in the same way.

Command Line Options
       The stunc utility accepts following command line options:

       -b  Perform a STUN binding discovery. stunc will report the client transport address (IP:port) as seen by the STUN server. In the presence
	   of NATs, this address is allocated by the NAT closest to the STUN server.

       -l  Perform a STUN binding life-time check.

       -n  Perform a STUN binding type check. Notice that the results are only hints. Nondeterministic behaviour, resource exhaustion, or reboots
	   of network elements can cause changes in NAT behaviour between successive runs of stunc.

       -r  Randomize the local port. Otherwise stunc let's the operating system select a free port.

       -s  Request a shared-secret over TLS. Tests whether the STUN server supports the shared-secret mechanism (needed to protect message
	   integrity). Can be combined with -b, -l and -n.

Return Codes
       0when successful 1when any errors detected

Examples
       Discover the NAT binding, use a random local port:

	$ stunc stunserver.org -b -r

Environment
       #STUN_DEBUG

Reporting Bugs
       Report bugs to <sofia-sip-devel@lists.sourceforge.net>.

Authors
       o Pekka Pessi <pekka -dot pessi -at- nokia -dot- com>

       o Martti Mela <martti -dot mela -at- nokia -dot- com>

       o Kai Vehmanen <kai -dot vehmanen -at- nokia -dot- com>

Copyright
       Copyright (C) 2005,2006 Nokia Corporation.

       This program is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
       PARTICULAR PURPOSE.

Version 1.12.11devel						  Sat May 7 2011							  stunc(1)

Check Out this Related Man Page

TFTP-PROXY(8)						    BSD System Manager's Manual 					     TFTP-PROXY(8)

NAME

     tftp-proxy -- Internet Trivial File Transfer Protocol proxy

SYNOPSIS

     tftp-proxy [-v] [-w transwait]

DESCRIPTION

     tftp-proxy is a proxy for the Internet Trivial File Transfer Protocol invoked by the inetd(8) internet server.  TFTP connections should be
     redirected to the proxy using the pf(4) rdr command, after which the proxy connects to the server on behalf of the client.

     The proxy establishes a pf(4) rdr rule using the anchor facility to rewrite packets between the client and the server.  Once the rule is
     established, tftp-proxy forwards the initial request from the client to the server to begin the transfer.	After transwait seconds, the pf(4)
     NAT state is assumed to have been established and the rdr rule is deleted and the program exits.  Once the transfer between the client and
     the server is completed, the NAT state will naturally expire.

     Assuming the TFTP command request is from $client to $server, the proxy connected to the server using the $proxy source address, and $port is
     negotiated, tftp-proxy adds the following rule to the anchor:

	   rdr proto udp from $server to $proxy port $port -> $client

     The options are as follows:

     -v      Log the connection and request information to syslogd(8).

     -w transwait
	     Number of seconds to wait for the data transmission to begin before removing the pf(4) rdr rule.  The default is 2 seconds.

CONFIGURATION

     To make use of the proxy, pf.conf(5) needs the following rules.  The anchors are mandatory.  Adjust the rules as needed for your configura-
     tion.

     In the NAT section:

	   nat on $ext_if from $int_if -> ($ext_if:0)

	   no nat on $ext_if to port tftp

	   rdr-anchor "tftp-proxy/*"
	   rdr on $int_if proto udp from $lan to any port tftp -> 
	       127.0.0.1 port 6969

     In the filter section, an anchor must be added to hold the pass rules:

	   anchor "tftp-proxy/*"

     inetd(8) must be configured to spawn the proxy on the port that packets are being forwarded to by pf(4).  An example inetd.conf(5) entry fol-
     lows:

	   127.0.0.1:6969  dgram   udp	   wait    root 
		   /usr/libexec/tftp-proxy tftp-proxy

SEE ALSO

     tftp(1), pf(4), pf.conf(5), ftp-proxy(8), inetd(8), syslogd(8), tftpd(8)

CAVEATS

     tftp-proxy chroots to /var/chroot/tftp-proxy and changes to user ``_proxy'' to drop privileges.

BSD
								   May 31, 2007 							       BSD
Man Page