[BACK]Return to mpd46.html CVS log [TXT] [DIR] Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / mpd / doc
File:  [ELWIX - Embedded LightWeight unIX -] / embedaddon / mpd / doc / mpd46.html
Revision 1.1.1.4 (vendor branch): download - view: text, annotated - select for diffs - revision graph
Wed Mar 17 00:39:23 2021 UTC (3 years, 9 months ago) by misho
Branches: mpd, MAIN
CVS tags: v5_9p16, v5_9, HEAD
mpd 5.9

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>UDP device type commands</TITLE>
</HEAD>
<BODY text="#000000" bgcolor="#ffffff">

<A HREF="mpd.html"><EM>Mpd 5.9 User Manual</EM></A>
 <b>:</b> <A HREF="mpd42.html"><EM>Device Types</EM></A>
 <b>:</b> <EM>UDP device type commands</EM><BR>
<b>Previous:</b> <A HREF="mpd45.html"><EM>TCP device type commands</EM></A><BR>
<b>Next:</b> <A HREF="mpd47.html"><EM>PPTP device type commands</EM></A>


<HR NOSHADE>
  <H2><A NAME="46"></A>5.4. UDP device type commands<A NAME="udp"></A></H2>
<p>This chapter describes commands that are specific to UDP type links.
These commands apply to the currently active link, and are only
valid if the currently active link has type <b>udp</b>.</p>

<p>It is suggested that the <code>set iface mtu</code> command be used
when this link type is in use to avoid IP fragmentation if you want
to get something better channel utilization.</p>

<p><b>Note:</b> Technically this device type is not completely correct, 
because PPP links are not allowed to re-order frames, yet UDP packets can
be delivered out of order. Therefore, if you use this link type you
should not enable multi-link PPP, PPP encryption, or PPP compression.
Otherwise, out of order frames will be dropped, leading to performance
degradation.</p>
<p>
<dl>

<dt><b><code>set udp self <em>ipaddr</em> [ <em>port</em> ]</code></b><dd><p>Sets the local IP address and port for the UDP connection.
If none is specified, any suitable local IP address is used.
Port specification is required for incoming connection accepting.</p>

<dt><b><code>set udp peer <em>ipaddr</em> [ <em>port</em> ]</code></b><dd><p>Sets the peer IP address and port for the UDP connection.
Address and port specification is required for connection originating.
For incoming connections it is not required, but can limit who can connect to us.</p>

</dl>
</p>

<p>The following options are supported:</p>
<p>
<dl>

<dt><b><code>resolve-once</code></b><dd><p>Enables resolving peer address only once, on startup, or on manual
typing in CLI.</p>
<p>The default is enable.</p>

</dl>

</p>


 <HR NOSHADE>
<A HREF="mpd.html"><EM>Mpd 5.9 User Manual</EM></A>
 <b>:</b> <A HREF="mpd42.html"><EM>Device Types</EM></A>
 <b>:</b> <EM>UDP device type commands</EM><BR>
<b>Previous:</b> <A HREF="mpd45.html"><EM>TCP device type commands</EM></A><BR>
<b>Next:</b> <A HREF="mpd47.html"><EM>PPTP device type commands</EM></A>



</BODY>
</HTML>
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>