Annotation of embedaddon/mpd/doc/mpd46.html, revision 1.1.1.2
1.1 misho 1: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
2: <HTML>
3: <HEAD>
4: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
5: <TITLE>UDP device type commands</TITLE>
6: </HEAD>
7: <BODY text="#000000" bgcolor="#ffffff">
8:
1.1.1.2 ! misho 9: <A HREF="mpd.html"><EM>Mpd 5.7 User Manual</EM></A>
1.1 misho 10: <b>:</b> <A HREF="mpd42.html"><EM>Device Types</EM></A>
11: <b>:</b> <EM>UDP device type commands</EM><BR>
12: <b>Previous:</b> <A HREF="mpd45.html"><EM>TCP device type commands</EM></A><BR>
13: <b>Next:</b> <A HREF="mpd47.html"><EM>PPTP device type commands</EM></A>
14:
15:
16: <HR NOSHADE>
17: <H2><A NAME="46"></A>5.4. UDP device type commands<A NAME="udp"></A></H2>
18: <p>This chapter describes commands that are specific to UDP type links.
19: These commands apply to the currently active link, and are only
20: valid if the currently active link has type <b>udp</b>.</p>
21:
22: <p>It is suggested that the <code>set iface mtu</code> command be used
23: when this link type is in use to avoid IP fragmentation if you want
24: to get something better channel utilization.</p>
25:
26: <p><b>Note:</b> Technically this device type is not completely correct,
27: because PPP links are not allowed to re-order frames, yet UDP packets can
28: be delivered out of order. Therefore, if you use this link type you
29: should not enable multi-link PPP, PPP encryption, or PPP compression.
30: Otherwise, out of order frames will be dropped, leading to performance
31: degradation.</p>
32: <p>
33: <dl>
34:
35: <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.
36: If none is specified, any suitable local IP address is used.
37: Port specification is required for incoming connection accepting.</p>
38:
39: <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.
40: Address and port specification is required for connection originating.
41: For incoming connections it is not required, but can limit who can connect to us.</p>
42:
43: </dl>
44: </p>
45:
46: <p>The following options are supported:</p>
47: <p>
48: <dl>
49:
50: <dt><b><code>resolve-once</code></b><dd><p>Enables resolving peer address only once, on startup, or on manual
51: typing in CLI.</p>
52: <p>The default is enable.</p>
53:
54: </dl>
55:
56: </p>
57:
58:
59: <HR NOSHADE>
1.1.1.2 ! misho 60: <A HREF="mpd.html"><EM>Mpd 5.7 User Manual</EM></A>
1.1 misho 61: <b>:</b> <A HREF="mpd42.html"><EM>Device Types</EM></A>
62: <b>:</b> <EM>UDP device type commands</EM><BR>
63: <b>Previous:</b> <A HREF="mpd45.html"><EM>TCP device type commands</EM></A><BR>
64: <b>Next:</b> <A HREF="mpd47.html"><EM>PPTP device type commands</EM></A>
65:
66:
67:
68: </BODY>
69: </HTML>
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>
![[BACK]](/icons/cvsweb/back.gif){kind=icon}
Return to mpd46.html CVS log ![[TXT]](/icons/cvsweb/text.gif){kind=icon}
![[DIR]](/icons/cvsweb/dir.gif){kind=icon}
Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / mpd / doc