Mike Aldred writes:
> $ pfexec snoop -d e1000g1
> Using device e1000g1 (promiscuous mode)
> 124.169.109.153 -> 203.0.178.191 DNS C download951.avast.com. Internet Addr ?
> 124.169.109.153 -> 203.215.29.191 DNS C download951.avast.com. Internet Addr ?
> 124.169.109.153 -> 66.54.123.184 UDP D=53719 S=25683 LEN=71
> 124.169.109.153 -> 77.251.157.185 UDP D=13983 S=25683 LEN=71
> 124.169.109.153 -> 203.0.178.191 DNS C safebrowsing.clients.google.com.
> Internet AAAA ?
> 124.169.109.153 -> 203.0.178.191 DNS C 153.109.169.124.in-addr.arpa. Internet
> PTR ?
> 124.169.109.153 -> 203.215.29.191 DNS C gadgets.live.com. Internet Addr ?
> 124.169.109.153 -> 203.0.178.191 DNS C www.slashdot.org. Internet Addr ?
> 124.169.109.153 -> 203.0.178.191 DNS C gadgets.live.com. Internet Addr ?
> 124.169.109.153 -> 203.215.29.191 DNS C gadgets.live.com. Internet Addr ?
> 124.169.109.153 -> 203.0.178.191 DNS C 191.178.0.203.in-addr.arpa. Internet
> PTR ?
> 124.169.109.153 -> 203.0.178.191 DNS C ocsp.verisign.com. Internet Addr ?
> 124.169.109.153 -> 203.0.178.191 DNS C gadgets.live.com. Internet Addr ?
> 124.169.109.153 -> 203.215.29.191 DNS C gadgets.live.com. Internet Addr ?
I take it that those are just PPPoE packets sent by you, with nothing
returning. (Using either -V or dumping raw to a file with -o and
using something more powerful such as wireshark to view would show a
little more detail.)
> It's like the ISP decides not to send me anymore packets. If I kill pppd and
> restart the link comes up fine. I'm not really too worried about the
> connection loss, it's just that I need the connection to be started
> automatically when it happens.
I've lost context here.
Do you have lcp-echo-failure and lcp-echo-interval set? If not then
add this to your pppd configuration:
lcp-echo-failure 4
lcp-echo-interval 3
That will at least get pppd to die off if the peer is completely
non-responsive ... "persist" should then get it to restart. That
works only if the problem is PPP itself, and not at a higher level
(such the peer suddenly decide that it doesn't want to forward IP
packets any more).
If you do have those options set, and the snoop trace you show was
just too short-lived to see an echo attempt, then it sounds like your
ISP is just plain broken. The best answer would be to convince them
to fix the service that you're paying for (;-}), or abandon them for
one that does care.
The next best answer might be to hack around it. You could have
/etc/ppp/ip-up start a background script that does periodic
invocations of "ping $IPREMOTE 3", and sends SIGHUP to pppd when it
sees an error. (No, not a great idea, but I'm having trouble coming
up with any others that can deal with malicious peer behavior.)
Just as a check: for dealing with most ISPs, you want to be as simple
as possible in the options you request. I suggest including "novj"
and "noccp" if you don't already have them.
--
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]
