This is error in the log file
|
Jul 11 17:15:56
|
mpd: MAGICNUM 26a82333
|
|
Jul 11 17:15:56
|
mpd: AUTHPROTO CHAP MD5
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: rec'd Configure Nak #27 link 0
(Ack-Sent)
|
|
Jul 11 17:15:56
|
mpd: MRU 1460
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: SendConfigReq #28
|
|
Jul 11 17:15:56
|
mpd: MRU 1460
|
|
Jul 11 17:15:56
|
mpd: MAGICNUM 26a82333
|
|
Jul 11 17:15:56
|
mpd: AUTHPROTO CHAP MD5
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: rec'd Configure Nak #28 link 0
(Ack-Sent)
|
|
Jul 11 17:15:56
|
mpd: MRU 1460
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: SendConfigReq #29
|
|
Jul 11 17:15:56
|
mpd: MRU 1460
|
|
Jul 11 17:15:56
|
mpd: MAGICNUM 26a82333
|
|
Jul 11 17:15:56
|
mpd: AUTHPROTO CHAP MD5
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: rec'd Configure Nak #29 link 0
(Ack-Sent)
|
|
Jul 11 17:15:56
|
mpd: MRU 1460
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: SendConfigReq #30
|
|
Jul 11 17:15:56
|
mpd: MRU 1460
|
|
Jul 11 17:15:56
|
mpd: MAGICNUM 26a82333
|
|
Jul 11 17:15:56
|
mpd: AUTHPROTO CHAP MD5
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: rec'd Configure Nak #30 link 0
(Ack-Sent)
|
|
Jul 11 17:15:56
|
mpd: MRU 1460
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: not converging
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: parameter negotiation failed
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: state change Ack-Sent --> Stopped
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: LayerFinish
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] device: CLOSE event in state UP
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] device is now in state CLOSING
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] device: DOWN event in state CLOSING
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] device is now in state DOWN
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] link: DOWN event
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: Down event
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: state change Stopped --> Starting
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: phase shift ESTABLISH --> DEAD
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: LayerStart
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: Close event
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: state change Starting --> Initial
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: LayerFinish
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] closing link "pppoe0"...
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] IPCP: Close event
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] IPCP: state change Starting --> Initial
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] IPCP: LayerFinish
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] bundle: CLOSE event in state OPENED
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] link: CLOSE event
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] LCP: Close event
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] device: OPEN event in state DOWN
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] pausing 6 seconds before open
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] device is now in state DOWN
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] device: CLOSE event in state DOWN
|
|
Jul 11 17:15:56
|
mpd: [pppoe0] device is now in state DOWN
|
De: alan walters
[mailto:[EMAIL PROTECTED]
Enviado el: Martes, 11 de Julio de
2006 01:40 p.m.
Para: [email protected]
Asunto: RE: [pfSense Support]
PPPOE Server
It failes after saying
registering on network???
Or what sequence does it
go through before it failes
From:
juan pablo burd [mailto:[EMAIL PROTECTED]]
Sent: 11 July 2006 17:27
To: [email protected]
Subject: RE: [pfSense Support]
PPPOE Server
Via ethernet, connected with winpoet
De: alan walters
[mailto:[EMAIL PROTECTED]
Enviado el: Martes, 11 de Julio de
2006 01:12 p.m.
Para: [email protected]
Asunto: RE: [pfSense Support]
PPPOE Server
Mtu issue most likely, we
see this problem also if the client continues to authenticate
Without waiting.
Is this on a wired
port???/
From:
juan pablo burd [mailto:[EMAIL PROTECTED]]
Sent: 11 July 2006 14:17
To: [email protected]
Subject: [pfSense Support] PPPOE
Server
I have the problem
Clients Windows 2000 profesional no connect with pfsense
pppoe Server (error 619), other (XP,98,95 2003) yes…. why
__________ Informacisn de NOD32, revisisn 1.1653 (20060711) __________
Este mensaje ha sido analizado con NOD32 antivirus system
http://www.nod32.com
__________ Informacisn de NOD32, revisisn 1.1653 (20060711) __________
Este mensaje ha sido analizado con NOD32 antivirus system
http://www.nod32.com