Mike Aldred writes:
> I've just recently got PPPOE working with Solaris, and it works great.  
> However, I've got a problem where the connection stops working,

"Stops working" in what way?

Are there error counts in "netstat -ni" or in "pppstats"?  What about
the non-zero values printed by "kstat sppp\*"?

Can you do "ping -sn" on the remote IP address?  If you do, what do you
see happening to the statistics?

Can you snoop the underlying Ethernet link?  What does that show
before and after the failure?

> Aug 12 18:13:38 storageserver pppd[1960]: [ID 702911 daemon.debug] rcvd [LCP 
> EchoReq id=0x8 magic=0x59621493 69 77 9a 10]
> Aug 12 18:13:38 storageserver pppd[1960]: [ID 702911 daemon.debug] sent [LCP 
> EchoRep id=0x8 magic=0x69779a10 69 77 9a 10]

Is this after a failure or before?  If it's after, then it looks like
there's nothing wrong with PPP itself.  The problem is likely to be
higher up -- something wrong with routing or wrong with the ISP
itself.

> I could write a script that checks if the machine can ping, etc, every 5 
> minutes and if not, restart the pppd process, but there must be a reason why 
> the machine isn't picking up the disconnection?

I don't see a disconnect here, at least at the PPP level.  If the peer
is able to respond to LCP Echo-Request packets, then as far as anyone
can tell, the PPP link is still "up."

Do you have compression enabled?  One suggestion is to simplify first:
disable compression.  Use "noccp novj" in your configuration file.
(ISP bugs in dealing with compression are unfortunately not uncommon.)

Failing all that, posting your configuration files and logs either
here or some accessible site would help a lot in diagnosing possible
problems.  (Though from the symptoms, it doesn't immediately sound
like a PPP problem to me.)

-- 
James Carlson, Solaris Networking              <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to