|
||||||||
As <pptpd><localip>192.168.1.51</localip> is in the range of your sis lan 192.168.1.50/24 I think your trouble is here. Either change /24 on sis or use another subnet for pptp (it's what I did sucessfully : LAN : 192.168.1.1 / 24 local ip of pptpd :192.168.2.1 remote ip : 192.168.2.16 / 28 Thierry ----- Original Message ----- From: "Adam Hirsch" <adam at baz dot org> To: "m0n0wall users" <m0n0wall at lists dot m0n0 dot ch> Sent: Tuesday, April 20, 2004 11:34 PM Subject: [m0n0wall] PPTP connection from OS X > Anyone used the built-in PPTP VPN client on OS X to successfully connect to > m0n0wall v1.0? > > I've got it set up to the point where it begins negotiating, pauses for a > while, and then reports that the PPTP server closed the connection. The > only suspicious logged line on the m0n0wall side is: > > mpd: [pptpc0] error writing len 42 frame to bypass: Can't assign requested address > > which seems odd, as the LAN interface for the firewall is: > > <if>sis0</if> > <ipaddr>192.168.1.50</ipaddr> > <subnet>24</subnet> > > and the pptpd config looks pretty much smack in the heart of > 192.168.1.0/24: > > <pptpd> > <mode>server</mode> > <redir/> > <localip>192.168.1.51</localip> > <remoteip>192.168.1.208</remoteip> > <user> > <name>YYYYY</name> > <password>xxxxx</password> > </user> > <radius> > <server/> > <secret/> > </radius> > </pptpd> > > Anyone had any success with this? I'm not quite sure where to start poking. > > tx, > > Adam > > p.s. mildly obfuscated logs below. > > mpd: [pptpc0] error writing len 42 frame to bypass: Can't assign requested address > mpd: pptp0-0: ignoring SetLinkInfo > mpd: [pptpc0] LCP: SendConfigReq #22 > mpd: ACFCOMP > mpd: PROTOCOMP > mpd: MRU 1500 > mpd: MAGICNUM 34cde244 > mpd: AUTHPROTO CHAP MSOFTv2 > mpd: MP MRRU 1600 > mpd: MP SHORTSEQ > mpd: ENDPOINTDISC [802.1] 00 00 24 c1 ce 3c > mpd: [pptpc0] error writing len 42 frame to bypass: Can't assign requested address > mpd: [pptpc0] LCP: SendConfigReq #23 > > [...] > > mpd: [pptpc0] LCP: state change Req-Sent --> Stopped > mpd: [pptpc0] LCP: LayerFinish > mpd: [pptpc0] LCP: parameter negotiation failed > mpd: [pptpc0] LCP: LayerFinish > mpd: [pptpc0] device: CLOSE event in state UP > mpd: pptp0-0: clearing call > mpd: pptp0-0: killing channel > mpd: [pptpc0] PPTP call terminated > mpd: [pptpc0] IFACE: Close event > mpd: [pptpc0] IPCP: Close event > mpd: [pptpc0] IPCP: state change Starting --> Initial > mpd: [pptpc0] IPCP: LayerFinish > mpd: [pptpc0] IFACE: Close event > mpd: pptp0: closing connection with 71.292.78.11:5140 > mpd: [pptpc0] IFACE: Close event > mpd: [pptpc0] device is now in state CLOSING > mpd: [pptpc0] bundle: CLOSE event in state OPENED > mpd: [pptpc0] closing link "pptpc0"... > mpd: [pptpc0] device: CLOSE event in state CLOSING > mpd: [pptpc0] device is now in state CLOSING > mpd: [pptpc0] link: CLOSE event > mpd: [pptpc0] LCP: Close event > mpd: [pptpc0] LCP: state change Stopped --> Closed > mpd: [pptpc0] device: DOWN event in state CLOSING > mpd: [pptpc0] device is now in state DOWN > mpd: [pptpc0] link: DOWN event > mpd: [pptpc0] LCP: Down event > mpd: [pptpc0] LCP: state change Closed --> Initial > mpd: [pptpc0] LCP: phase shift ESTABLISH --> DEAD > mpd: [pptpc0] device: DOWN event in state DOWN > mpd: [pptpc0] device is now in state DOWN > mpd: [pptpc0] link: DOWN event > mpd: [pptpc0] LCP: Down event > mpd: pptp0: ctrl connection closed by peer > mpd: pptp0: killing connection with 71.292.78.11:5140 > > -- > Well, you win some, you lose some, and then <adam at baz dot org> > there's that little-known third category. - Al Gore <adam hirsch> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch > |