Firstly my appologies for having sent out a HTML email making it so huge.

As for my querries:

I am launching pppd as follows
----------------------------------
/usr/sbin/pppd /dev/modem mtu 4096 mru 296 115200 noipdefault netmask 255.255.0.0 
persist asyncmap 20A0000 defaultroute
user xxxxx debug connect /etc/ppp/scripts/dialer
----------------------------------
I believe pppd is correctly figuring out that 115200 is the connection speed and not 
the MTU atleast the logs aren't
showing a MTU of 115200. Ofcourse if you go by the man it should be the second 
parameter but if pppd doesn't mind it
why should I :). Also the MTU value can't just be set to any value by the client. I 
once specified a MRU of 8192 and
Netscape started downloading in multiples of 8192 so I am sure I would have noticed if 
it got set to 115200.

Now for asyncmap the man pages say that if I specify a asyncmap then those control 
characters can't be sent safely over
the serial line - so how am I supposed to figure out what is safe and what isn't ?? I 
did notice in the log that my ISP
had sent a asyncmap 0x0 - does that mean I can set asyncmap 0x0 on my end and not 
escape any characters ??? I am
assuming asyncpap is something which can cause problem on the dial in server end of 
the connection.

netmask : hmm will drop it I didn't have any specific reason to use it anyway.

modules: No I do have the ppp-deflate and bsd-comp modules in the right place.
mithun@valium:~ > ls -l /lib/modules/2.3.3/net/
total 167
-rw-r--r--   1 root     root         9844 Aug 20 01:30 8390.o
-rw-r--r--   1 root     root         6992 Jul 23 21:51 ash
-rw-r--r--   1 root     root         6152 Oct  4 17:09 bsd_comp.o
-rw-r--r--   1 root     root         2616 Oct  4 17:09 dummy.o
-rw-r--r--   1 root     root         4876 Oct  4 17:09 ethertap.o
-rw-r--r--   1 root     root         6992 Aug 20 01:30 ne2k-pci.o
-rw-r--r--   1 root     root        14012 Oct  4 17:09 plip.o
-rw-r--r--   1 root     root        30672 Oct  4 17:09 ppp.o
-rw-r--r--   1 root     root        42096 Oct  4 17:09 ppp_deflate.o
-rw-r--r--   1 root     root         7464 Oct  4 17:09 slhc.o
-rw-r--r--   1 root     root        13152 Oct  4 17:09 slip.o
-rw-r--r--   1 root     root        16108 Oct 27 15:22 winbond.o

You might have noted the log reported that the kernel had loaded the ppp-deflate 
compression module. Also I have tried
doing a insmod on bsd-comp (ppp-deflate was already loaded) and then dial out with no 
change in the compression.

pcomp and accomp are basic stuff being supported by slhc.o why would they get rejected 
?? I haven't given the nopcomp
and noaccomp option to pppd and there doesn't seem to be any way of telling pppd to 
use it so I am assuming it defaults
to yes.

magic number: Hmm if I understand it correctly I believe in a looped back condition 
everything gets echoed back to the
ppp daemon. No while talking to the ISP I see them using the same magic number from 
both sides so how is it going to
detect a looped back condition using the magic number ??

Dec 11 09:41:45 valium pppd[1001]: rcvd [IPCP ConfReq id=0x3 <compress VJ 0f 01> <addr 
202.56.230.44>]
Now what does that "compress VJ 0f 01" thing mean I assumed the ISP is requesting Van 
Jacobson style TCP/IP  header
compression but maybe I am wrong.

Dec 11 09:41:45 valium pppd[1001]: rcvd [CCP ConfReq id=0x4 < 12 06 00 00 00 01> < 11 
05 00 01 03> <bsd v1 12>
<predictor 1>]
What does the "bsd v1 12" mean isn't it supported by bsd-comp.o ?? What about 
predictor 1 - ppp source code has a lot
of reference to that but a search on Deja news makes me believe that it isn't 
supported as all the answers seem to say
that we should disable that option.

Yah I am using a simple Hayes modem (it's not a winmodem for sure !!) over a Telco 
line nothing fancy hardware wise.

Finally thanks to Cliff for for his answers it cleared away some of the clouds :).



Mithun


-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]

Reply via email to