Mpd has extensive logging system supporting syslog. To direct logs +
Mpd has extensive logging system supporting syslog. To direct logs into a file add lines
!mpd @@ -35,15 +35,13 @@ SIGHUP to syslogd to reread config.
Make sure you have set gateway_enable="YES"
in /etc/rc.conf, otherwise your FreeBSD box will not
-route packets.
-Alternately, invoke sysctl -w net.inet.ip.forwarding=1
-for immediate effect.
Also, check your firewall settings. Mpd will create new interfaces which may need to be incorporated into your firewall rules. If you're doing PPTP, you need to allow TCP port 1723 and IP protocol 47 (GRE).
-Make sure you have all the required netgraph KLD's loaded. +
Make sure you have all the required netgraph KLD's loaded.
You can check them by doing kldstat -v | grep ng_ .
Usually these are loaded on demand. If not, you can load them
manually using kldload(8).
kldload(8).
-Upgrade to a version of FreeBSD newer than 4.7-RELEASE. Or apply -http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netgraph/ng_pptpgre.c.diff?r1=1.25&r2=1.26 -manually.
- -Make sure your mpd.conf file formatted properly.
+
Make sure your mpd.conf file formatted properly.
Labels must be left-justified, while other lines must not.
Double-check the shared secret in the RADIUS servers config and the +
Double-check the shared secret in the RADIUS servers config and the
one specified in mpd.conf or radius.conf.
Check the ports of the RADIUS server: they should be 1812 (authentication)
and 1813 (accounting), wich are also the default ports of mpd. In
the past unofficial port numbers (1645 and 1646) were used for RADIUS,
but these are deprecated.
This is often caused by a combination of (a) using netgraph in KLD module +
This is often caused by a combination of (a) using netgraph in KLD module
form instead of statically compiling the various modules into the kernel
via kernel config(8) options, and (b) increasing your
kernel security level (see the init(8) man page), which prevents
KLD modules from being loaded. Change one of these things to fix the problem.
This is because mpd is trying to ``redial,'' which of course is not +
This is because mpd is trying to ``redial'' which of course is not
appropriate for dial-in links. Use set link max-redial -1 and
set bundle yes noretry to disable the redial function.
Windows XP insists on a very low MTU (usualy 1396 Bytes), this needs -fragmentation, if bigger packets should be transmited over the link. -Fragmentation is negotiated at ICMP level, if there is a bad router -somewhere in the network, who drops such packets, then the connection -seems to hang. +
Windows XP insists on a very low MTU (usually 1396 Bytes). This needs
+fragmentation if bigger packets should be transmitted over the link.
+Fragmentation is negotiated at ICMP level. If there is a bad router
+somewhere in the network dropping such packets then the connection
+hangs.
The first thing what you can try is reducing mpd's MTU value, by
setting: set link mtu 1300 and set bundle disable multilink,
this should help in most cases.
-For TCP connections it's possible enabling the TCP-MSS-Fix:
-set iface enable tcpmssfix (available since mpd-3.15).
set iface enable tcpmssfix.
Upgrade the IOS of your device, see:
CSCdu30944 MPPE rejects stateless Fixed in 12.3(11.4)