Kernel Panic when using mpd VPN Tunnel
Hello all, I have a Digital AlphaPC 164LX 533 MHz, running FreeBSD 4.11-RELEASE I have installed /usr/ports/net/mpd and attempted to make a vpn connection and after authenticating it seems to bring the machine to a panic with the following info in the messages file. May 3 17:20:35 medusa /kernel: May 3 17:20:35 medusa /kernel: fatal kernel trap: May 3 17:20:35 medusa /kernel: May 3 17:20:35 medusa /kernel: trap entry = 0x4 (unaligned access fault) May 3 17:20:35 medusa /kernel: a0 = 0xfe5cb5ce May 3 17:20:35 medusa /kernel: a1 = 0x28 May 3 17:20:35 medusa /kernel: a2 = 0x1 May 3 17:20:35 medusa /kernel: pc = 0xfc4da0a0 May 3 17:20:35 medusa /kernel: ra = 0xfc4dabec May 3 17:20:35 medusa /kernel: curproc= 0xfe00098d6300 May 3 17:20:35 medusa /kernel: pid = 189, comm = mpd May 3 17:20:35 medusa /kernel: May 3 17:20:35 medusa /kernel: panic: trap May 3 17:20:35 medusa /kernel: Now the how to I was following asked that I make sure that the kernel is compiled with the following device option. device tun # Packet tunnel. This line was in the kernel config but was listed as follows pseudo-device tun # Packet tunnel. I have tried using both versions and have seen the same kernel panic each time. Any one have any tips for me? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Panic when using mpd VPN Tunnel
On Thursday 04 May 2006 15:52, Shawn Guillemette wrote: Hello all, I have a Digital AlphaPC 164LX 533 MHz, running FreeBSD 4.11-RELEASE I have installed /usr/ports/net/mpd and attempted to make a vpn connection What kind of VPN? mpd does ppp over serial lines, ethernet, udp and pptp. and after authenticating it seems to bring the machine to a panic with the following info in the messages file. May 3 17:20:35 medusa /kernel: May 3 17:20:35 medusa /kernel: fatal kernel trap: May 3 17:20:35 medusa /kernel: May 3 17:20:35 medusa /kernel: trap entry = 0x4 (unaligned access fault) May 3 17:20:35 medusa /kernel: a0 = 0xfe5cb5ce May 3 17:20:35 medusa /kernel: a1 = 0x28 May 3 17:20:35 medusa /kernel: a2 = 0x1 May 3 17:20:35 medusa /kernel: pc = 0xfc4da0a0 May 3 17:20:35 medusa /kernel: ra = 0xfc4dabec May 3 17:20:35 medusa /kernel: curproc= 0xfe00098d6300 May 3 17:20:35 medusa /kernel: pid = 189, comm = mpd May 3 17:20:35 medusa /kernel: May 3 17:20:35 medusa /kernel: panic: trap May 3 17:20:35 medusa /kernel: Now the how to I was following asked that I make sure that the kernel is compiled with the following device option. device tun # Packet tunnel. I don't know how tun(4) is relevant This line was in the kernel config but was listed as follows pseudo-device tun # Packet tunnel. I have tried using both versions and have seen the same kernel panic each time. Any one have any tips for me? Describe what you want to do please. what kind of VPN and what the peers are. I am using mpd for a long time and never had a panic(well, almost) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mpd VPN Server / W2K Clients
Hello Jonathan, I found this thread from a long time ago at FreeBSD addicts: http://lists.freebsd.org/pipermail/freebsd-questions/2003-December/027869.ht ml I'm having absolutely identical problem with my MPD (it used to work and then it just stopped, who knows why). I tried to follow up on that solution you posted, but that page no longer opens up. Any help is greatly appreciated. Thank you much! -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.1 - Release Date: 4/1/2005 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mpd VPN Server / W2K Clients
- Original Message - From: Anton Zavrin [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Monday, April 04, 2005 9:27 AM Subject: mpd VPN Server / W2K Clients Hello Jonathan, I found this thread from a long time ago at FreeBSD addicts: http://lists.freebsd.org/pipermail/freebsd-questions/2003-December/027869.ht ml I'm having absolutely identical problem with my MPD (it used to work and then it just stopped, who knows why). I tried to follow up on that solution you posted, but that page no longer opens up. Any help is greatly appreciated. Thank you much! -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.1 - Release Date: 4/1/2005 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Anton, some things too look for here. Are the remote systems using Win XP? If so, are their firewalls configured to allow traffic from your network on TCP ports 1723? Also, is GRE being blocked at any point between your mpd system and their end? If it just stopped working, has anyone placed a firmware firewall device in recently? Many of them that I've run across recently don't even know what GRE is so a specific entry has to be made to allow protocol 47 to pass freely in order to get pptp to function properly. Hope it helps. -- Micheal Patterson Senior Communications Systems Engineer 405-917-0600 Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
MPD VPN questions...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello all, I have MPD setup to create pptp VPN. I have a couple of questions. 1) How do I make traffic coming from a host that's connected to the VPN look like it's coming from a VPN IP address? Currently it comes from their real, i.e. public IP address. 2) I use SSL for mail retrieval currently. Right now, if I'm connected to my VPN, if I try to retrieve email, I get nothing. If I look in /var/log/messages, I see the following: Oct 3 19:43:09 grog qpopper[730]: (v4.0.5) TLSv1/SSLv3 handshake with client at 0-1pool198-217.nas2.fargo1.nd.us.da.qwest.net (67.1.198.217); new session-id; cipher: RC4-SHA (RC4-SHA SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=SHA1), 128 bits Oct 3 19:43:14 grog qpopper[730]: I/O Error Oct 3 19:43:14 grog qpopper[730]: Error writing to client Oct 3 19:43:14 grog qpopper[730]: I/O Error Oct 3 19:43:14 grog qpopper[730]: Error writing to client Oct 3 19:43:14 grog qpopper[730]: I/O Error Oct 3 19:43:14 grog qpopper[730]: Error writing to client Oct 3 19:43:14 grog qpopper[730]: OpenSSL Error during write Oct 3 19:43:14 grog qpopper[730]: ...SSL error: error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry Oct 3 19:43:14 grog qpopper[730]: Error writing to client Oct 3 19:43:14 grog qpopper[730]: ecrist at 0-1pool198-217.nas2.fargo1.nd.us.da.qwest.net (67.1.198.217): -ERR POP hangup from grog.secure-computing.net Oct 3 19:43:14 grog qpopper[730]: OpenSSL Error during write Oct 3 19:43:14 grog qpopper[730]: ...SSL error: error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry Oct 3 19:43:14 grog qpopper[730]: Error writing to client Oct 3 19:43:14 grog qpopper[730]: Stats: ecrist 0 0 1313 6756817 0-1pool198-217.nas2.fargo1.nd.us.da.qwest.net 67.1.198.217 Oct 3 19:43:14 grog qpopper[730]: OpenSSL Error during write Oct 3 19:43:14 grog qpopper[730]: ...SSL error: error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry Oct 3 19:43:14 grog qpopper[730]: Error writing to client Any idea why this would be? I have a feeling it's because the server is trying to send to my public IP address, but that's being blocked by the VPN from the server side. I'm all confused now. Thanks for you help. - - Eric F Crist Secure Computing Networks -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iEYEARECAAYFAkFgncIACgkQRAAY9knOW+oUJgCggigbs5qukKUfx/FrATkQmCRw XtYAn3ez+59mSKr4K/U9cE8M0xrR3Vi1 =Km4Q -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: mpd VPN Server / W2K Clients
Hello, I am trying to configure mpd for road warrior w2k clients to connect to, and I'm running into a few issues, hoping some of you could help out. I'm not sure if there are other issues that need to be configured differently besides mpd, like ppp or natd, etc. Or do you need to change options in the W2K VPN client. Below are my specs, mpd config files, and error message. Please let me know if you have any I know its been a while since you posted (I don't get to read this list as often as I'd like to), but in case you didn't get it working, the thing that threw me for a while was putting gateway_enable=yes in rc.conf (syntax might be slightly different). Its in the MPD readme file, but you don't see that file when installing from ports. ;) Don't forget to run some sort of firewall so you only allow pptp traffic to bridge that connection. Brent ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mpd VPN Server / W2K Clients
Hello, I am trying to configure mpd for road warrior w2k clients to connect to, and I'm running into a few issues, hoping some of you could help out. I'm not sure if there are other issues that need to be configured differently besides mpd, like ppp or natd, etc. Or do you need to change options in the W2K VPN client. Below are my specs, mpd config files, and error message. Please let me know if you have any suggestions. THANKS!!! --- Heres my specs on my testing box: --- FreeBSD 4.9 WAN IP: 1.2.3.4 LAN IP: 10.30.30.1 MPD version: 3.15 Recompiled with these options IPFIREWALL, DUMMYNET, BRIDGE, IPSEC: Pretty basic testing firewall system. Running ipfw, natd --- Mpd.conf: --- default: load pptp0 pptp0: new -i ng0 pptp0 pptp0 set ipcp ranges 10.30.30.100/24 10.30.30.230/24 load pptp pptp: set iface disable on-demand set iface enable proxy-arp set iface idle 1800 set link yes acfcomp protocomp set link no chap set link enable pap set link mtu 1460 set link mru 1460 set link keep-alive 10 60 set ipcp yes vjcomp set ipcp dns 6.7.8.9 set bundle enable compression set ccp yes mpp-compress set ccp yes mppc set ccp yes mpp-e40 set ccp yes mpp-e56 set ccp yes mpp-e128 set ccp yes mpp-stateless --- Mpd.links: --- pptp0: set link type pptp set pptp self 1.2.3.4 set pptp enable incoming set pptp disable originate --- Mpd.secret: --- Johnpassword --- When a W2K client(24.24.24.24) tries to connect, this is what is displayed on the server: --- Multi-link PPP for FreeBSD, by Archie L. Cobbs. Based on iij-ppp, by Toshiharu OHNO. mpd: pid 3472, version 3.15 ([EMAIL PROTECTED] 12:19 1-Dec-2003) [pptp0] ppp node is mpd3472-pptp0 mpd: local IP address for PPTP is 1.2.3.4 [pptp0] using interface ng0 [pptp0:pptp0] mpd: PPTP connection from 24.24.24.24:1275 pptp0: attached to connection with 24.24.24.24:1275 [pptp0] IFACE: Open event [pptp0] IPCP: Open event [pptp0] IPCP: state change Initial -- Starting [pptp0] IPCP: LayerStart [pptp0] IPCP: Open event [pptp0] bundle: OPEN event in state CLOSED [pptp0] opening link pptp0... [pptp0] link: OPEN event [pptp0] LCP: Open event [pptp0] LCP: state change Initial -- Starting [pptp0] LCP: LayerStart [pptp0] device: OPEN event in state DOWN [pptp0] attaching to peer's outgoing call [pptp0] device is now in state OPENING [pptp0] device: UP event in state OPENING [pptp0] device is now in state UP [pptp0] link: UP event [pptp0] link: origination is remote [pptp0] LCP: Up event [pptp0] LCP: state change Starting -- Req-Sent [pptp0] LCP: phase shift DEAD -- ESTABLISH [pptp0] LCP: SendConfigReq #1 ACFCOMP PROTOCOMP MRU 1460 MAGICNUM 7ad4aee0 AUTHPROTO PAP MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 04 75 c3 99 19 pptp0-0: ignoring SetLinkInfo [pptp0] LCP: rec'd Configure Request #0 link 0 (Req-Sent) MRU 1400 MAGICNUM 76ca7995 PROTOCOMP ACFCOMP CALLBACK Not supported [pptp0] LCP: SendConfigRej #0 CALLBACK [pptp0] LCP: rec'd Configure Reject #1 link 0 (Req-Sent) MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 04 75 c3 99 19 [pptp0] LCP: SendConfigReq #2 ACFCOMP PROTOCOMP MRU 1460 MAGICNUM 7ad4aee0 AUTHPROTO PAP [pptp0] LCP: rec'd Configure Request #1 link 0 (Req-Sent) MRU 1400 MAGICNUM 76ca7995 PROTOCOMP ACFCOMP [pptp0] LCP: SendConfigAck #1 MRU 1400 MAGICNUM 76ca7995 PROTOCOMP ACFCOMP [pptp0] LCP: state change Req-Sent -- Ack-Sent [pptp0] LCP: rec'd Configure Nak #2 link 0 (Ack-Sent) AUTHPROTO CHAP MSOFTv2 [pptp0] LCP: SendConfigReq #3 ACFCOMP PROTOCOMP MRU 1460 MAGICNUM 7ad4aee0 AUTHPROTO PAP [pptp0] LCP: rec'd Configure Nak #3 link 0 (Ack-Sent) AUTHPROTO CHAP MSOFT [pptp0] LCP: SendConfigReq #4 ACFCOMP PROTOCOMP MRU 1460 MAGICNUM 7ad4aee0 AUTHPROTO PAP [pptp0] LCP: rec'd Configure Nak #4 link 0 (Ack-Sent) AUTHPROTO CHAP MSOFT [pptp0] LCP: SendConfigReq #5 ACFCOMP PROTOCOMP MRU 1460 MAGICNUM 7ad4aee0 AUTHPROTO PAP [pptp0] LCP: rec'd Configure Nak #5 link 0 (Ack-Sent) AUTHPROTO CHAP MSOFT [pptp0] LCP: SendConfigReq #6 ACFCOMP PROTOCOMP MRU 1460 MAGICNUM 7ad4aee0 AUTHPROTO PAP [pptp0] LCP: rec'd Configure Nak #6 link 0 (Ack-Sent) AUTHPROTO CHAP MSOFT [pptp0] LCP: SendConfigReq #7 ACFCOMP PROTOCOMP MRU 1460 MAGICNUM 7ad4aee0 AUTHPROTO PAP [pptp0] LCP: rec'd Configure Nak #7 link 0 (Ack-Sent) AUTHPROTO CHAP MSOFT [pptp0] LCP: SendConfigReq #8 ACFCOMP PROTOCOMP MRU 1460 MAGICNUM 7ad4aee0 AUTHPROTO PAP [pptp0] LCP: SendConfigReq #9 ACFCOMP PROTOCOMP MRU 1460 MAGICNUM 7ad4aee0 AUTHPROTO PAP [pptp0] LCP: rec'd Configure Nak #9 link 0 (Ack-Sent) AUTHPROTO CHAP MSOFT [pptp0] LCP: SendConfigReq #10 ACFCOMP PROTOCOMP MRU 1460 MAGICNUM 7ad4aee0 AUTHPROTO PAP [pptp0] LCP: rec'd Configure Nak #10 link 0 (Ack-Sent) AUTHPROTO
Re: mpd VPN Server / W2K Clients
Bill Asher wrote: Hello, I am trying to configure mpd for road warrior w2k clients to connect to, and I'm running into a few issues, hoping some of you could help out. I'm not sure if there are other issues that need to be configured differently besides mpd, like ppp or natd, etc. Or do you need to change options in the W2K VPN client. Below are my specs, mpd config files, and error message. Please let me know if you have any suggestions. THANKS!!! *snip* i recently posted a howto on getting mpd up an working with winxp. the steps should be almost identical. you can find it here. if it still dosn't work, feel free to follow up to me directly. http://freebsdaddicts.org/modules.php?name=Sectionsop=viewarticleartid=9 ~j -- Yesterday upon the stair I saw a man who wasn't there, he wasn't there again today, oh how i wish he'd go away Rev. Jonathan T. Sage Lighting / Set Designer Professional Web Design [HTTP://thr.msu.edu] [EMAIL PROTECTED] [PGP: www.keyserver.net] pgp0.pgp Description: PGP signature
mpd - vpn help
Hi, I have set up a pptp server using mpd. I can connect from a windows client through the firewall without any issues. My problem is routing. The windows machine gets an IP of say 192.168.1.251, and is issued a gateway of the same IP. All I can do from there is ping the pptp server. I can't figure out how to give it a proper gateway. I would appreciate some help me with relevant lines for both mpd.conf and mpd.links. I would prefer to just use a section of the local LAN (say 192.168.1.240/29), rather than add another subnet, but whatever works. 192.168.1.0/24 LAN 192.168.1.126 gateway for above network 192.168.1.81 pptd server running mpd Thanks in advance for any help, Jeanne ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intermittent failures with mpd VPN
Hm well answering my own question, I have discovered the problem lies in my linksys router off my cable modem at home. Suddenly the pptp pass-through feature has become pptp pass-through every so often. Upgrading the firmware didn't help. The funny thing is, a co-worker of mine started to have the exact same problem at the exact same time -- 50 miles away and with a different router (d-link). We both have the same home ISP, Comcast (a very sucky company btw), which is really the only link between us. mysterious. -Jeff --- Jeff Leary [EMAIL PROTECTED] wrote: Hi, I have a 4.5-release firewall / VPN server which has been humming along without a glitch since 4.5-release first came out. I have applied only relevant patches during this time since this box's only job is ipfilter, ipnat, and mpd. Just recently there's been this intermittent behavior of not being able to login -- but if you keep trying you'll eventually get in after 4 or 5 attempts. snip enormous post __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Intermittent failures with mpd VPN
Hi, I have a 4.5-release firewall / VPN server which has been humming along without a glitch since 4.5-release first came out. I have applied only relevant patches during this time since this box's only job is ipfilter, ipnat, and mpd. Just recently there's been this intermittent behavior of not being able to login -- but if you keep trying you'll eventually get in after 4 or 5 attempts. Failed logins look like PPTP connection from 1.2.3.4:1705 pptp0: attached to connection with 1.2.3.4:1705 [pptp0] IFACE: Open event [pptp0] IPCP: Open event [pptp0] IPCP: state change Initial -- Starting [pptp0] IPCP: LayerStart [pptp0] IPCP: Open event [pptp0] bundle: OPEN event in state CLOSED [pptp0] opening link pptp0... [pptp0] link: OPEN event [pptp0] LCP: Open event [pptp0] LCP: state change Initial -- Starting [pptp0] LCP: LayerStart [pptp0] device: OPEN event in state DOWN [pptp0] attaching to peer's outgoing call [pptp0] device is now in state OPENING [pptp0] device: UP event in state OPENING [pptp0] device is now in state UP [pptp0] link: UP event [pptp0] link: origination is remote [pptp0] LCP: Up event [pptp0] LCP: state change Starting -- Req-Sent [pptp0] LCP: phase shift DEAD -- ESTABLISH [pptp0] LCP: SendConfigReq #50 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM 88c318a0 AUTHPROTO CHAP MSOFTv2 MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 10 4b 06 de cf pptp0-0: ignoring SetLinkInfo [pptp0] LCP: rec'd Configure Request #0 link 0 (Req-Sent) MAGICNUM 3b27257f PROTOCOMP ACFCOMP CALLBACK Not supported MP MRRU 1614 ENDPOINTDISC [LOCAL] MAC address snipped [pptp0] LCP: SendConfigRej #0 CALLBACK [pptp0] LCP: SendConfigReq #51 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM 88c318a0 AUTHPROTO CHAP MSOFTv2 MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 10 4b 06 de cf [pptp0] LCP: rec'd Configure Request #1 link 0 (Req-Sent) MAGICNUM 3b27257f PROTOCOMP ACFCOMP CALLBACK Not supported MP MRRU 1614 ENDPOINTDISC [LOCAL] MAC address snipped [pptp0] LCP: SendConfigRej #1 CALLBACK [pptp0] LCP: SendConfigReq #52 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM 88c318a0 AUTHPROTO CHAP MSOFTv2 MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 10 4b 06 de cf [pptp0] LCP: rec'd Configure Request #2 link 0 (Req-Sent) MAGICNUM 3b27257f PROTOCOMP ACFCOMP CALLBACK Not supported MP MRRU 1614 ENDPOINTDISC [LOCAL] MAC address snipped [pptp0] LCP: SendConfigRej #2 CALLBACK [pptp0] LCP: SendConfigReq #53 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM 88c318a0 AUTHPROTO CHAP MSOFTv2 MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 10 4b 06 de cf [pptp0] LCP: SendConfigReq #54 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM 88c318a0 AUTHPROTO CHAP MSOFTv2 MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 10 4b 06 de cf [pptp0] LCP: rec'd Configure Request #3 link 0 (Req-Sent) MAGICNUM 3b27257f PROTOCOMP ACFCOMP CALLBACK Not supported MP MRRU 1614 ENDPOINTDISC [LOCAL] MAC address snipped [pptp0] LCP: SendConfigRej #3 CALLBACK [pptp0] LCP: SendConfigReq #55 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM 88c318a0 AUTHPROTO CHAP MSOFTv2 MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 10 4b 06 de cf [pptp0] LCP: SendConfigReq #56 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM 88c318a0 AUTHPROTO CHAP MSOFTv2 MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 10 4b 06 de cf [pptp0] LCP: rec'd Configure Request #4 link 0 (Req-Sent) MAGICNUM 3b27257f PROTOCOMP ACFCOMP CALLBACK Not supported MP MRRU 1614 ENDPOINTDISC [LOCAL] MAC address snipped [pptp0] LCP: SendConfigRej #4 CALLBACK [pptp0] LCP: SendConfigReq #57 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM 88c318a0 AUTHPROTO CHAP MSOFTv2 MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 10 4b 06 de cf [pptp0] LCP: SendConfigReq #58 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM 88c318a0 AUTHPROTO CHAP MSOFTv2 MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 10 4b 06 de cf [pptp0] LCP: rec'd Configure Request #5 link 0 (Req-Sent) MAGICNUM 3b27257f PROTOCOMP ACFCOMP CALLBACK Not supported MP MRRU 1614 ENDPOINTDISC [LOCAL] MAC address snipped [pptp0] LCP: not converging [pptp0] LCP: parameter negotiation failed [pptp0] LCP: state change Req-Sent -- Stopped [pptp0] LCP: LayerFinish [pptp0] device: CLOSE event in state UP pptp0-0: clearing call pptp0-0: killing channel [pptp0] PPTP call terminated [pptp0] IFACE: Close event [pptp0] IPCP: Close event [pptp0] IPCP: state change Starting -- Initial [pptp0] IPCP: LayerFinish [pptp0] IFACE: Close event pptp0: closing connection with 1.2.3.4:1705 [pptp0] IFACE: Close event [pptp0] device is now in state CLOSING [pptp0] bundle: CLOSE event in state OPENED [pptp0] closing
RE: MPD/VPN
Hi, Long ago I had the same problem. You should check the XP client and it connection settings. I can't remember the exact trick and I have no XP machine here to test it right now, but there is some problems with multilink. You should disable multilink on XP machine or you should enable it on both sides. The problem is that I can't remember which of these 2 solutions worked with me. Best regards, Ivailo Tanusheff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Scott Pilz Sent: Monday, January 13, 2003 7:16 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: MPD/VPN I'm open to suggestions on this one. I have tried everything :( I'm hoping that someone else ran into this problem and knows how to fix it. MPD/FREEBSD as a VPN server. Multiple clients (windows and unix). Windows 98: Works great, connects, tiny performance drop in speed, hardly noticeable. Windows 2000: Works just as well as Windows 98 if not better. Windows XP: I can connect, ping through the VPN, even load tiny web pages and telnet out - but anything large stalls completely. I've tried multiple XP machines, they all do the same thing. It is my understanding that this is a MTU issue - but I find it very hard to believe that Microsoft products need configuration before they work, such as a MTU change. Heres mpd.conf for what it's worth (I've excluded the clients): client_standard: set iface disable on-demand set iface enable proxy-arp set iface idle 86400 set bundle disable multilink set link yes acfcomp protocomp set link disable pap set link enable chap set link keep-alive 10 60 set ipcp yes vjcomp set ipcp dns 66.170.64.1 66.170.64.13 set bundle enable compression set bundle enable crypt-reqd set ccp yes mppc set ccp yes mpp-e40 set ccp yes mpp-e128 set ccp yes mpp-stateless One other thing - I notice that the two clients that do work (any Windows 98 or 2000 box) has a MTU of 1496 on the server: ng0: flags=88d1UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST mtu 1496 The ones that don't vary but are NOT 1496. Any input would be helpful at this point. bangs head into desk Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
MPD/VPN
I'm open to suggestions on this one. I have tried everything :( I'm hoping that someone else ran into this problem and knows how to fix it. MPD/FREEBSD as a VPN server. Multiple clients (windows and unix). Windows 98: Works great, connects, tiny performance drop in speed, hardly noticeable. Windows 2000: Works just as well as Windows 98 if not better. Windows XP: I can connect, ping through the VPN, even load tiny web pages and telnet out - but anything large stalls completely. I've tried multiple XP machines, they all do the same thing. It is my understanding that this is a MTU issue - but I find it very hard to believe that Microsoft products need configuration before they work, such as a MTU change. Heres mpd.conf for what it's worth (I've excluded the clients): client_standard: set iface disable on-demand set iface enable proxy-arp set iface idle 86400 set bundle disable multilink set link yes acfcomp protocomp set link disable pap set link enable chap set link keep-alive 10 60 set ipcp yes vjcomp set ipcp dns 66.170.64.1 66.170.64.13 set bundle enable compression set bundle enable crypt-reqd set ccp yes mppc set ccp yes mpp-e40 set ccp yes mpp-e128 set ccp yes mpp-stateless One other thing - I notice that the two clients that do work (any Windows 98 or 2000 box) has a MTU of 1496 on the server: ng0: flags=88d1UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST mtu 1496 The ones that don't vary but are NOT 1496. Any input would be helpful at this point. bangs head into desk Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
mpd VPN Routing
Has anyone managed to connect two LANs via an mpd tunnel and get packets to flow from one LAN to another? Something like this: Home LAN---Home Firewallmpd tunnelOffice Peer---Office LAN I can reach any host on the office LAN from the home firewall over the mpd tunnel, but hosts behind the home firewall cannot do more than ping the local end of the mpd tunnel. I have tried a few things, including: routing table entries for the office LAN on Home LAN hosts, pointing to the remote end of the mpd tunnel, with a routing table entry to reach the remote end of the tunnel via the local end of the tunnel ipfw add pass all from any to any via ng1 (ng1 is the mpd tunnel interface) Is this even possible? Thanks, -- Chris BeHanna Software Engineer (Remove bogus before responding.) [EMAIL PROTECTED] Turning coffee into software since 1990. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
