After several private email exchanges with michael fowler,
I have ISOLATED the configuration options that were putting
all the noise on my ppp line which was causing the
Protocol-Reject messages... (and occasionally corrupting
transmissions to the point of crashing netscape.
The secret is to comment our ALL options in /etc/ppp/options
EXCEPT for those that are NOT specified in /etc/daild.conf.
Apparently pppd gets REAL confused when invoked from diald...
with options that are also in its options file.
In the end the only options I have left in my ppp/options
file are:
asyncmap 00000000
name login_name_on_ISP
remotename ppp0
Everything else is driven by diald...
The line is now quiet when there is no activity on it...
at least according to pppstats -w 1.
This is a RH 6.0 system. I am dialing one ISP on a single modem.
The diald.conf file is basically the configuration suggested in the man page
for a dynamically assigned IP address with the lines added to filter out
netbios messages.
So... I'm happy... so far. Now on to trying ipchains and making this
system a proxy for the windoze boxes on my network... I'll be going
back over the thread on that subject with a fine toothed comb next.
Would the original poster like to summarize his final solution?
Lincoln
Michael Fowler wrote:
>
> On Sun, Feb 06, 2000 at 11:07:49PM -0500, Lincoln A. Baxter wrote:
>
> > connect "/usr/sbin/chat -f /etc/sysconfig/network-scripts/chat-ppp0"
>
> > However, I discovered that I had to comment it out of the /etc/ppp/options
> > file to prevent diald from trying to log in twice.
> >
> > I this because normally ppp was intended to be invoked the the -connect
> > argument on the command line? If so, I guess I understand this, it just
> > took me a while to figure it out.
>
> This is because diald has already dialed up; when pppd is executed, and it
> has a connect line, it tries to connect as well.
>
> > Feb 6 21:52:00 hostname pppd[2793]: Protocol-Reject for unsupported protocol
>0x5072
> [snip...]
> > Feb 6 21:52:01 hostname pppd[2793]: Protocol-Reject for unsupported protocol
>0x5072
> >
> > etc... thousands of these. Does anyone know what protocols: 0x5072 and
> > 0x7263 are? and how to prevent these? I figure I get this text because I
> > had pppd running in debug mode, but I wanted to know what it was
> > rejecting.
>
> There is an entry for this in the PPP FAQ. What it boils down to is that,
> if those are invalid protocol numbers (as they appear to be, from a glance
> at RFC1700 and RFC1661), then pppd on your end is putting garbage on the
> line.
>
> > I also get the following error on diald startup which I do not understand, but
>which
> > seems to be harmless.
> >
> > Feb 6 22:44:54 lbaxter diald[2952]: start sl0: SIOCSIFMETRIC: Operation not
>supported
>
> This can be safely ignored; in Linux 2.2 kernels metrics are largely ignored
> for interfaces.
>
> Michael
> --
> Administrator www.shoebox.net
> Programmer, System Administrator www.gallanttech.com
> --
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
