The Tuesday 2005-01-18 at 12:37 +0100, Per Jessen wrote:
Carlos E. R. wrote:
I could perhaps try compiling the pppd from SuSE 8.2 and put it in 9.1, if that is doable.
I would go for the latest pppd instead - 2.4.3 - from http://ppp.samba.org. But don't do it right now.
Depends on the version SuSE 9.2 uses. If it is that one, it will probably fail. Hamel? What pppd version does 9.2 use?
As to the configuration, I upgraded from 8.2 to 9.1, so most of the configuration is the same, and with 8.2 it worked. What configuration file(s) are you thinking of?
The pppd conf would be critical here. /etc/ppp/options.* /etc/ppp/peers/*
I'll check. 7.3 has now: debug noauth crtscts lock modem asyncmap 0 nodetach lcp-echo-interval 30 lcp-echo-failure 4 lcp-max-configure 60 lcp-restart 2 idle 600 noipx 9.1 has: noipdefault debug kdebug 1 noauth crtscts lock modem asyncmap 0 nodetach lcp-echo-interval 30 lcp-echo-failure 4 lcp-max-configure 60 lcp-restart 2 idle 600 noipx file /etc/ppp/filters Both are the default files that come with its respective SuSE versions, except for the debug tokens. The filters file refered above contains one active line: active-filter 'outbound and not icmp[0] == 3 and not tcp[13] & 4 != 0' Then, in 9.1 the file peers/wvdia applies: plugin passwordfd.so noauth name wvdial debug novjccomp noccp novj
I use wvdial to control the connection, called from a console.
Uh, I don't know wvdial - when I used pppd dial-up I always used diald for dial-on-demand.
[...] yes, I see strings like this printed in the xterm console where I call wvdial:
--> Using interface ppp0 --> pppd: ovider --> pppd: ovider --> pppd: ovider --> Authentication (CHAP) started
It should be possible to call pppd directly - "pppd /dev/ttySx". That will use the following config files: /etc/ppp/options, ~/.ppprc and /etc/ppp/options.ttySx
Unless you do "pppd call xxxxx" which will make it use /etc/ppp/peers/xxxxxx.
There is something not quite right - maybe in the script - I don't know if wvdial generates a connect script or something? I'd like to try calling pppd directly from the command-line - that is about as basic as it gets.
It is just a chat equivalent, with "intelligence". wvdial calls pppd with the following options: 6440 pts/5 Ss 0:00 \_ bash 8723 pts/5 S+ 0:00 | \_ /bin/sh /home/cer/bin/mywvdial steleline 8728 pts/5 S+ 0:00 | \_ /usr/bin/wvdial steleline 8729 pts/5 S 0:00 | \_ /usr/sbin/pppd 115200 modem crtscts defaultroute usehostname -detach user LOGINNAME noipdefault call wvdial idle 85 logfd 6 I used chat and pppd years ago, I forgot how to use it. But I don't think that is the problem.
I see the errors:
Jan 17 01:17:16 nimrodel pppd[9421]: rcvd [LCP EchoRep id=0xe magic=0xd28f2d2b] Jan 17 01:17:18 nimrodel pppd[9421]: rcvd [Compressed data] 00 09 82 14 ee 4b c0 85 ... Jan 17 01:17:18 nimrodel pppd[9421]: sent [CCP ResetReq id=0x9] Jan 17 01:17:18 nimrodel pppd[9421]: rcvd [CCP ResetAck id=0x9]
OK, it seems something IS obviously wrong with the compression. Could be on your side, could be on your providers side. So back to "noccp" and "novj".
Right, done.
An average of 2.04 KB/s. In the SuSE 7.3 I can get 5 or 6. And the log is:
There was a lot of text here - I'm getting a little lost.
I can imagine - I'm used to reading logs ;-)
Have we now established that with compression disabled (due to errors) in 9.1, you get 1-2kbyte/s , but with compression enabled in 7.3/8.2, you get 5-6kbyte/s ?
The speeds with compression enabled/disabled seem to be roughly the same (tests below) on each computer. The 9.1 gets from 1.5 to 3 depending on the day or who knows what, and the 7.3 (and 8.2 before updating that machine) seems to get over 5 KB/s, and can maintain it over long downloads - with some exceptions, of course, providers are not perfect.
Well... More ideas? Do you think I could use the old pppd daemon, recompiling it? The kernel has changed, but I could try, if you think it is possible. :-?
I don't think it's really necessary, but if you do upgrade, I would go for the latest 2.4.3.
I'll have a look.
Sorry, like I said, I got a little lost in all of this: On the system where you get the good speed (7.3? 8.2?) what happens if you disable compression? (or is compression also disabled there?) Do you see any VJ errors on that system? What speed do you get with and without compression?
Let's see - this run with compression on the 7.3 machine, 5.22 KB/s during a 100 Kbyte download - and there are no errors in the log: cer@nimrodel:~> date ; time wget --timeout=90 --waitretry=10 "ftp://ftp.rediris.es/sites2/ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/sharutils-4.2c-710.10.i586.rpm" Tue Jan 18 19:22:05 CET 2005 --19:22:05-- ftp://ftp.rediris.es/sites2/ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/sharutils-4.2c-710.10.i586.rpm => `sharutils-4.2c-710.10.i586.rpm.3' Resolving ftp.rediris.es... 130.206.1.5 Connecting to ftp.rediris.es[130.206.1.5]:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /sites2/ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586 ... done. ==> PASV ... done. ==> RETR sharutils-4.2c-710.10.i586.rpm ... done. [ <=> ] 11,584 9.18K/s [ <=> ] 23,168 6.90K/s [ <=> ] 36,200 5.81K/s [ <=> ] 52,128 5.48K/s [ <=> ] 68,056 5.32K/s [ <=> ] 81,088 4.27K/s [ <=> ] 101,360 5.45K/s [ <=> ] 106,115 5.45K/s 19:22:28 (5.22 KB/s) - `sharutils-4.2c-710.10.i586.rpm.3' saved [106115] I had disabled compression for that run, but I see in the log that it ignored me. Let's try again [...] yes, got it, had to use /etc/ppp/options. Average speed for the same download was 5.13 KB/s, roughly the same. [ <=> ] 7,240 6.16K/s [ <=> ] 20,272 4.70K/s [ <=> ] 40,544 4.80K/s [ <=> ] 57,920 5.32K/s [ <=> ] 73,848 5.31K/s [ <=> ] 89,776 5.17K/s [ <=> ] 102,808 5.13K/s [ <=> ] 106,115 5.13K/s 19:36:06 (5.13 KB/s) - `sharutils-4.2c-710.10.i586.rpm.4' saved [106115] Compression at the tcp/ip layer or ppp layer I don't think can affect much on a good modem, because they do compression in hardware: 1st run CONNECT 50666/ARQ/V90/LAPM/V42BIS 2nd run CONNECT 50666/ARQ/V90/LAPM/V42BIS -- Cheers, Carlos Robinson