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>Troubleshooting</TITLE>
6: </HEAD>
7: <BODY text="#000000" bgcolor="#ffffff">
8:
9: <A HREF="mpd.html"><EM>Mpd 5.9 User Manual</EM></A>
10: <b>:</b> <A HREF="mpd62.html"><EM>Troubleshooting</EM></A>
11: <b>:</b> <EM>Troubleshooting</EM><BR>
12: <b>Previous:</b> <A HREF="mpd62.html"><EM>Troubleshooting</EM></A><BR>
13: <b>Next:</b> <A HREF="mpd64.html"><EM>Internals</EM></A>
14:
15:
16: <HR NOSHADE>
17: <H2><A NAME="63"></A>7.1. Troubleshooting<A NAME="trouble"></A></H2>
18: <p>Some tips for troubleshooting.</p>
19:
20: <p>For further help, ask to the <code>freebsd-net@freebsd.org</code>
21: mailing list or sourceforge.net mpd project forum.</p>
22: <p>
23: <dl>
24:
25: <dt><b><b>It does not work and I do not understand why.</b></b><dd><p>Mpd has extensive logging system supporting syslog. To direct logs
26: into a file add lines
27: <pre>
28: !mpd
29: *.* /var/log/mpd.log
30: </pre>
31:
32: into your /etc/syslog.conf file, create /var/log/mpd.log file and send
33: SIGHUP to syslogd to reread config.</p>
34: <p>To enable all possible logging you can use 'log +all' command.</p>
35:
36: <dt><b><b>Packets won't flow.</b></b><dd><p>Make sure you have set <code><b>gateway_enable="YES"</b></code>
37: in <code>/etc/rc.conf</code>, otherwise your FreeBSD box will not
38: route packets.</p>
39: <p>Also, check your firewall settings. Mpd will create new interfaces
40: which may need to be incorporated into your firewall rules.
41: If you're doing PPTP, you need to allow TCP port 1723 and IP protocol
42: 47 (GRE).</p>
43:
44: <dt><b><b>It does not work and there are strange netgraph-related errors in the log.</b></b><dd><p>Make sure you have all the required netgraph KLD's loaded.
45: You can check them by doing <code> kldstat -v | grep ng_ </code>.</p>
46: <p>Usually these are loaded on demand. If not, you can load them
47: manually using <code>kldload(8)</code>.</p>
48: <p>The following node types are or may be needed:</p>
49: <p>
50: <ul>
51: <li><code>ng_async</code></li>
52: <li><code>ng_bpf</code></li>
53: <li><code>ng_car</code></li>
54: <li><code>ng_deflate</code></li>
55: <li><code>ng_ether</code></li>
56: <li><code>ng_iface</code></li>
57: <li><code>ng_ksocket</code></li>
58: <li><code>ng_l2tp</code></li>
59: <li><code>ng_mppc</code></li>
60: <li><code>ng_ppp</code></li>
61: <li><code>ng_pppoe</code></li>
62: <li><code>ng_pptpgre</code></li>
63: <li><code>ng_nat</code></li>
64: <li><code>ng_netflow</code></li>
65: <li><code>ng_pred1</code></li>
66: <li><code>ng_socket</code></li>
67: <li><code>ng_tcpmss</code></li>
68: <li><code>ng_tee</code></li>
69: <li><code>ng_tty</code></li>
70: <li><code>ng_vjc</code></li>
71: </ul>
72: </p>
73:
74: <dt><b><b>My configuration does not seem to be working as expected.</b></b><dd><p>Make sure your <code>mpd.conf</code> file formatted properly.
75: Labels must be left-justified, while other lines must not.</p>
76:
77: <dt><b><b>I am getting no valid response from the RADIUS server.</b></b><dd><p>Double-check the shared secret in the RADIUS servers config and the
78: one specified in <code>mpd.conf</code> or <code>radius.conf</code>.
79: Check the ports of the RADIUS server: they should be 1812 (authentication)
80: and 1813 (accounting), wich are also the default ports of mpd. In
81: the past unofficial port numbers (1645 and 1646) were used for RADIUS,
82: but these are deprecated.</p>
83:
84: <dt><b><b>I am getting ``Operation not permitted'' errors trying to run mpd.</b></b><dd><p>This is often caused by a combination of (a) using netgraph in KLD module
85: form instead of statically compiling the various modules into the kernel
86: via kernel <code>config(8)</code> options, and (b) increasing your
87: kernel security level (see the <code>init(8)</code> man page), which prevents
88: KLD modules from being loaded. Change one of these things to fix the problem.</p>
89:
90: <dt><b><b>I have configured a link for dial-in and sometimes after disconnecting
91: mpd gets into some kind of infinite loop.</b></b><dd><p>This is because mpd is trying to ``redial'' which of course is not
92: appropriate for dial-in links. Use <code>set link max-redial -1</code> and
93: <code>set bundle yes noretry</code> to disable the redial function.</p>
94:
95: <dt><b><b>I use mpd as PPTP server for Windows XP clients. While accessing bigger
96: websites or listing larger ftp directories the connection
97: seems to hang.</b></b><dd><p>Windows XP insists on a very low MTU (usually 1396 Bytes). This needs
98: fragmentation if bigger packets should be transmitted over the link.
99: Fragmentation is negotiated at ICMP level. If there is a bad router
100: somewhere in the network dropping such packets then the connection
101: hangs.
102: The first thing what you can try is reducing mpd's MTU value, by
103: setting: <code>set link mtu 1300</code> and <code>set bundle disable multilink</code>,
104: this should help in most cases.
105: For TCP connections it is possible enabling the TCP-MSS-Fix:
106: <code>set iface enable tcpmssfix</code>.</p>
107:
108: <dt><b><b>Problems with MPPE stateless when connecting to Cisco devices.</b></b><dd><p>Upgrade the IOS of your device, see:
109: <code>CSCdu30944 MPPE rejects stateless Fixed in 12.3(11.4)</code></p>
110:
111: </dl>
112: </p>
113:
114: <HR NOSHADE>
115: <A HREF="mpd.html"><EM>Mpd 5.9 User Manual</EM></A>
116: <b>:</b> <A HREF="mpd62.html"><EM>Troubleshooting</EM></A>
117: <b>:</b> <EM>Troubleshooting</EM><BR>
118: <b>Previous:</b> <A HREF="mpd62.html"><EM>Troubleshooting</EM></A><BR>
119: <b>Next:</b> <A HREF="mpd64.html"><EM>Internals</EM></A>
120:
121:
122:
123: </BODY>
124: </HTML>
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>
![[BACK]](/icons/cvsweb/back.gif){kind=icon}
Return to mpd63.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