mpd pptp server questions
Hi ! I'm using MPD 3.10 on a FreeBSD 4.4-STABLE #0: Sat Apr 13 19:16:07 CEST 2002 machine. I've setup a PPTP server allowing remote access to the local network for the Win2k integrated PPTP client. Works OK so far but I got some messages in my logs that I don't understand. I haven't found any answer nor in the manual nor Google so I'm posting here. Dec 17 13:59:02 bull mpd: 192.168.0.10 -> 192.168.0.202 Dec 17 13:59:02 bull mpd: [pptp2] IFACE: Up event Dec 17 13:59:02 bull mpd: [pptp2] exec: /sbin/ifconfig ng0 192.168.0.10 192.168.0.202 netmask 0x -link0 Dec 17 13:59:02 bull mpd: [pptp2] exec: /usr/sbin/arp -s 192.168.0.202 0:b0:d0:e1:48:74 pub Dec 17 13:59:02 bull mpd: [pptp2] exec: /sbin/route add 192.168.0.0 192.168.0.202 -netmask 0xff00 Dec 17 13:59:02 bull mpd: [pptp2] exec: command returned 256 Dec 17 13:59:02 bull mpd: [pptp2] IFACE: Up event Dec 17 13:59:02 bull mpd: [pptp2] rec'd unexpected protocol IP on link -1 As I wrote before, my problem is only this "verbosity", the server itself is doing fine. So, my questions regarding the logs are : 1) What does "exec: command returned 256" means ? 2) What "does rec'd unexpected protocol IP on link -1" means ? BTW, my setup only allows 1 client now but I'd like to allow up to about 10-15 machines more. Any idea of the burden this would put on a PIII 866 - 512 MB - U160 SCSI server already providing some other basic net services ? Do you think it's feasible ? Thanks in advance for any help & advice. Yann Nottara -- System & Network administrator Almonde Tel : +33 1 58 18 66 84 Fax : +33 1 58 18 66 99 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: mpd pptp server questions
Archie Cobbs wrote: Yann Nottara wrote: [...] So, my questions regarding the logs are : 1) What does "exec: command returned 256" means ? The "route add" command failed for some reason. Does the route already exist? So it seems, I'll have to check. 2) What "does rec'd unexpected protocol IP on link -1" means ? That's a transient error, it should really just be suppressed. The peer sent an IP packet before we were completely ready. No big deal. That's what I suspected as it didn't seem to have any influence on communications. BTW, my setup only allows 1 client now but I'd like to allow up to about 10-15 machines more. Any idea of the burden this would put on a PIII 866 - 512 MB - U160 SCSI server already providing some other basic net services ? Do you think it's feasible ? Should be no problem. -Archie Thanks for your help/assistance and for providing such a great piece of software to the community. In my case, it's one more Win2k server that I won't buy and (most important) won't "baby-sit". Yann Nottara -- System & Network administrator Almonde Tel : +33 1 58 18 66 84 Fax : +33 1 58 18 66 99 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: mpd pptp server questions
Olivier Cherrier wrote: I'm using MPD 3.10 on a FreeBSD 4.4-STABLE #0: Sat Apr 13 19:16:07 CEST Isn'it a problem to run a recent MPD application on an 'old' 4.4 system? I'd agree with you but in my case, apart from what seems to be a few unnecessary verbosity, the MPD PPTP server runs quite well. Regards, Yann Nottara -- System & Network administrator Almonde Tel : +33 1 58 18 66 84 Fax : +33 1 58 18 66 99 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
MPD 3.13 PPTP server MTU problems & questions
Hello, I've been running a FreeBSD 4.7 box with a MPD 3.13 PPTP VPN server for quite some time now and, altough it mostly works, I'd like to iron out some problems we encounter. Configuration (that gives an IP address in a 192.168.0.0/24 local network to 16 Win2k clients at this moment) is done according to the following model : MPD PPTP, DNS & Samba server is 192.168.0.10 mpd.conf * default: load pptp0 pptp0: new -i ng0 pptp0 pptp0 set iface route 192.168.0.10/24 set iface disable on-demand set iface enable proxy-arp set iface idle 3600 set bundle enable multilink set link yes acfcomp protocomp set link no pap chap set link enable chap set link keep-alive 10 60 set link mtu 1460 set ipcp yes vjcomp set ipcp ranges 192.168.0.10/32 192.168.0.204/32 set ipcp dns 192.168.0.10 set ipcp nbns 192.168.0.10 set bundle enable compression set ccp yes mppc set ccp no mpp-e40 set ccp yes mpp-e128 set ccp yes mpp-stateless ** mpd.links ** pptp0: set link type pptp set pptp self 192.168.0.10 set pptp enable incoming set pptp disable originate ** As you'll see in the logs below and from ifconfig output, altough the ngX interfaces MTU is set to 1460 with "set link mtu 1460", it stays at 1500. Any idea why ? *** [EMAIL PROTECTED] ~ $ ifconfig fxp0: flags=8843 mtu 1500 inet 192.168.0.10 netmask 0xff00 broadcast 192.168.0.255 inet6 fe80::2b0:d0ff:fee1:4874%fxp0 prefixlen 64 scopeid 0x1 ether 00:b0:d0:e1:48:74 media: Ethernet autoselect (100baseTX ) status: active fxp1: flags=8802 mtu 1500 ether 00:b0:d0:e1:48:75 media: Ethernet autoselect (none) status: no carrier lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 ppp0: flags=8010 mtu 1500 sl0: flags=c010 mtu 552 faith0: flags=8002 mtu 1500 ng0: flags=88d1 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng0 prefixlen 64 scopeid 0x7 inet 192.168.0.10 --> 192.168.0.204 netmask 0x ng1: flags=8890 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng1 prefixlen 64 scopeid 0x8 ng2: flags=8890 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng2 prefixlen 64 scopeid 0x9 ng3: flags=8890 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng3 prefixlen 64 scopeid 0xa ng4: flags=8890 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng4 prefixlen 64 scopeid 0xb ng5: flags=8890 mtu 1500 ng6: flags=8890 mtu 1500 ng7: flags=8890 mtu 1500 ng8: flags=8890 mtu 1500 ng9: flags=8890 mtu 1500 ng10: flags=8890 mtu 1500 ng11: flags=8890 mtu 1500 ng12: flags=8890 mtu 1500 ng13: flags=8890 mtu 1500 ng14: flags=8890 mtu 1500 ng15: flags=8890 mtu 1500 ng16: flags=8890 mtu 1500 mpd.log *** Jul 16 18:52:11 bull mpd: mpd: PPTP connection from 123.456.789.12:25833 Jul 16 18:52:11 bull mpd: pptp0: attached to connection with 123.456.789.12:25833 Jul 16 18:52:11 bull mpd: [pptp0] IFACE: Open event Jul 16 18:52:11 bull mpd: [pptp0] IPCP: Open event Jul 16 18:52:11 bull mpd: [pptp0] IPCP: state change Initial --> Starting Jul 16 18:52:11 bull mpd: [pptp0] IPCP: LayerStart Jul 16 18:52:11 bull mpd: [pptp0] IPCP: Open event Jul 16 18:52:11 bull mpd: [pptp0] bundle: OPEN event in state CLOSED Jul 16 18:52:11 bull mpd: [pptp0] opening link "pptp0"... Jul 16 18:52:11 bull mpd: [pptp0] link: OPEN event Jul 16 18:52:11 bull mpd: [pptp0] LCP: Open event Jul 16 18:52:11 bull mpd: [pptp0] LCP: state change Initial --> Starting Jul 16 18:52:11 bull mpd: [pptp0] LCP: LayerStart Jul 16 18:52:11 bull mpd: [pptp0] device: OPEN event in state DOWN Jul 16 18:52:11 bull mpd: [pptp0] attaching to peer's outgoing call Jul 16 18:52:11 bull mpd: [pptp0] device is now in state OPENING Jul 16 18:52:11 bull mpd: [pptp0] device: UP event in state OPENING Jul 16 18:52:11 bull mpd: [pptp0] device is now in state UP Jul 16 18:52:11 bull mpd: [pptp0] link: UP event Jul 16 18:52:11 bull mpd: [pptp0] link: origination is remote Jul 16 18:52:11 bull mpd: [pptp0] LCP: Up event Jul 16 18:52:11 bull mpd: [pptp0] LCP: state change Starting --> Req-Sent Jul 16 18:52:11 bull mpd: [pptp0] LCP: phase shift DEAD --> ESTABLISH Jul 16 18:52:11 bull mpd: [pptp0] LCP: SendConfigReq #198 Jul 16 18:52:11 bull mpd: ACFCOMP Jul 16 18:52:11 bull mpd: PROTOCOMP Jul 16 18:52:11 bull mpd: MRU 1500 Jul 16 18:52:11 bull mpd: MAGICNUM e7805d68 Jul 16 18:52:11 bull mpd: AUTHPROTO CHAP MSOFTv2 Jul 16 18:52:11 bull mpd: MP MRRU 1600 Jul 16 18:52:11 bull mpd: MP SHORTSEQ Jul 16 18:52:11 bull mpd: ENDPOINTDISC [802.1] 00 b0 d0 e1 48 74 Jul 16 18:5
Re: MPD 3.13 PPTP server MTU problems & questions
Nikolai SAOUKH wrote: | As you'll see in the logs below and from ifconfig output, altough the | ngX interfaces MTU is set to 1460 with "set link mtu 1460", it stays at | 1500. Any idea why ? The asked mtu size will be available (set) only when interface is in UP state. When the ngX is in down state it has default values. Thanks for your help. Zs you can see in the following real world example, ng0 (which IS up) MTU stays at 1500 although it's configured to be at 1460 in the mpd.conf configuration file : ng0: flags=8890 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng0 prefixlen 64 scopeid 0x7 ng1: flags=8890 mtu 1500 ng2: flags=8890 mtu 1500 ng3: flags=8890 mtu 1500 ... Any idea ? --Yann ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MPD 3.13 PPTP server MTU problems & questions
Andy Gilligan wrote: - Original Message - From: "Yann Nottara" <[EMAIL PROTECTED]> Zs you can see in the following real world example, ng0 (which IS up) MTU stays at 1500 although it's configured to be at 1460 in the mpd.conf configuration file : ng0: flags=8890 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng0 prefixlen 64 scopeid 0x7 This doesn't look UP to me :) [...] Whenever MPD receives a connection, and assigns that interface to a client, it will change the MTU and mark it as UP. At least, it does for me... Interface down, mpd running, no client connected: ng0: flags=8890 mtu 1500 inet6 fe80::209:5bff:fe2f:692c%ng0 prefixlen 64 scopeid 0x7 Client connects: ng0: flags=88d1 mtu 1396 inet 192.168.0.1 --> 192.168.0.2 netmask 0x inet6 fe80::209:5bff:fe2f:692c%ng0 prefixlen 64 scopeid 0x7 Regards, -Andy Ok, my mistake on this one :) but now, what do you think of this ? ng0: flags=88d1 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng0 prefixlen 64 scopeid 0x7 inet 192.168.0.10 --> 192.168.0.200 netmask 0x and here's the part from my mpd.conf that's related to this connection : pptp0: new -i ng0 pptp0 pptp0 set iface disable on-demand set iface enable proxy-arp set iface idle 3600 set bundle enable multilink set link yes acfcomp protocomp set link no pap chap set link enable chap set link keep-alive 10 60 set link mtu 1460 <- ! set ipcp yes vjcomp set ipcp ranges 192.168.0.10/32 192.168.0.200/32 set ipcp dns 192.168.0.10 set ipcp nbns 192.168.0.10 So, where's the catch ? --Yann ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MPD 3.13 PPTP server MTU problems & questions
Andy Gilligan wrote: - Original Message - From: "Yann Nottara" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, July 17, 2003 6:53 PM Subject: Re: MPD 3.13 PPTP server MTU problems & questions but now, what do you think of this ? ng0: flags=88d1 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng0 prefixlen 64 scopeid 0x7 inet 192.168.0.10 --> 192.168.0.200 netmask 0x and here's the part from my mpd.conf that's related to this connection : pptp0: new -i ng0 pptp0 pptp0 set iface disable on-demand set iface enable proxy-arp set iface idle 3600 set bundle enable multilink set link yes acfcomp protocomp set link no pap chap set link enable chap set link keep-alive 10 60 set link mtu 1460 <- ! set ipcp yes vjcomp set ipcp ranges 192.168.0.10/32 192.168.0.200/32 set ipcp dns 192.168.0.10 set ipcp nbns 192.168.0.10 So, where's the catch ? Pretty much the same config as myself, with the exeption that I have: set bundle enable compression set ccp yes mppc set ccp yes mpp-e40 set ccp yes mpp-e128 set ccp yes mpp-stateless Sorry, I forgot to include that part but I use it too. I've set the MTU to 1460 - as you have, which seems to give me 1396 when a client connects. So far, I've only tested this with Windows XP machines, so I'm not sure if anything OS-specific concerning the MTU is negotiated during the connect phase, or even if having MPPE enabled would affect it. My PPTP clients are all Windows 2000 machines. I imagine you've tried setting the MTU to other values? Right, and it's all the same (but now I understand why after reading a post from this thread by Archie Cobbs. Best regards, -Andy Thanks for you help & comments. --Yann ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
