Folks, I'm supporting a retail store setup where stores connect to the head office using IPSec over PPPoE links, handled by a FreeBSD 4.3 server. Both IPSec and PPPoE are working fine. However, lately we've been having problems where PPP will disconnect for some reason and reconnect. Since I'm very confident that FreeBSD's PPPoE is rock solid, I'm trying to pin it down on the ISP, which has a track record of making unannounced service outages.
Here's a log snippet of a typical disconnect: Oct 2 13:03:43 belmont ppp[144]: tun0: Phase: deflink: open -> lcp Oct 2 13:03:43 belmont ppp[144]: tun0: IPCP: deflink: LayerDown: 209.167.75.124 Oct 2 13:03:43 belmont ppp[144]: tun0: IPCP: deflink: State change Opened --> Starting Oct 2 13:03:43 belmont ppp[144]: tun0: IPCP: deflink: LayerFinish. Oct 2 13:03:43 belmont ppp[144]: tun0: IPCP: Connect time: 15841 secs: 20512841 octets in, 3999315 octets out Oct 2 13:03:43 belmont ppp[144]: tun0: IPCP: : 25041 packets in, 21506 packetsout Oct 2 13:03:43 belmont ppp[144]: tun0: IPCP: total 1547 bytes/sec, peak 71398 bytes/sec on Tue Oct 2 13:03:43 2001 Oct 2 13:03:43 belmont ppp[144]: tun0: IPCP: deflink: State change Starting --> Initial Oct 2 13:03:43 belmont ppp[144]: tun0: Phase: bundle: Terminate Oct 2 13:03:46 belmont ppp[144]: tun0: Phase: deflink: Disconnected! Oct 2 13:03:46 belmont ppp[144]: tun0: Phase: deflink: lcp -> logout Oct 2 13:03:46 belmont ppp[144]: tun0: Phase: deflink: logout -> hangup Oct 2 13:03:46 belmont ppp[144]: tun0: Phase: deflink: Disconnected! How can I tell who is instigating the disconnect? -- Matt Emmerton To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
