Dante, For a noisy line, decreasing your MTU (maximal transfer Unit) with/etc/ppp/options may help. MarvS On 4/13/07, Dante ZePasta <dixuaf7@xxxxxxxx> wrote:> Interesting thought; the problem is that my ability to> connect is totally independent of whether I enable or> disable stupid mode in wvdial.conf.>> Here's one of my vague theories: I live up in a> canyon, and our telephone lines tend to be fairly> "dirty;" up until recently, most of the Windows> computers in my house couldn't connect at speeds any> higher than 26 Kb/s. As a result of all this, it> usually takes most of my computers several> "negotiation cycles" to successfully connect to my ISP> (several consecutive iterations of what sounds to be> the seem screechy communication string). All this> negotiation can take quite a long time - up to a full> minute, or more sometimes.> Based largely on the audial pattern I'm getting from> my linux laptop's modem, it seems like the PPP daemon> times out if a connection isn't made after a given> period of time; as I mentioned earlier, wvdial says> "No Carrier," and promptly starts redialing - even as> my ISP's server continues to try to finish the first> negotiation.>> I should mention that my other machines do> occasionally manage to make a connection after only> one iteration of the "handshake" - and though I> haven't really tested it, it seems that the rate at> which they do this is roughly equivalent to the rate> at which my linux box is connecting at all. (1-2> successes per 10 attempts).>> So I'm wondering if there's some setting that> specifies how long the PPP daemon should wait for a> connection before declaring "No Carrier" - and if> there is, if there's also some way to change that> setting.>>> - Dante>>>> --- Jacques Goldberg <Jacques.Goldberg@xxxxxxx> a> écrit :> >> > Could it be that you have a Stupid Mode line in> > /etc/wvdial.conf ?> > If your ISP immediately starts the login procedure,> > itprompts for the> > Username and waits for you to answer while Stupid> > Mode was introduced> > for those very few ISP's which wait for your side to> > start the login> > procedure.> > This would create a mess.> >> > Jacques> >> > Dante ZePasta wrote:> > > Good news - I've managed to get online, and am> > writing> > > this from my> > > linux box. Bad news: I can only seem to do it> > once> > > every ten tries.> > >> > > Sure enough, the DNS problem disappeared when I> > > disabled my other> > > network interfaces - but I'm still running into> > the> > > first two problems I> > > mentioned earlier:> > >> > >>> Sometimes (50% of the time, say) the> > negotiations> > > appear to time> > >>> out before the ppp daemon recognizes the> > carrier;> > >>> sometimes it recognizes the carrier but then> > seems> > > to> > >>> get stuck (mybug1alt) until manually terminated.> >> > >> > > But here's something interesting: where I used to> > get> > > infinite copies> > > of the line "pppd: sword" (see mybugalt.txt below)> > > when the daemon "got> > > stuck", now I'm getting infinite copies of the> > line> > > "pppd: Username."> > > Here's an example:> > > --> WvDial: Internet dialer version 1.54.0> > > --> Cannot get information for serial port.> > > --> Initializing modem.> > > --> Sending: ATZ> > > ATZ> > > OK> > > --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2> > > ATQ0 V1 E1 S0=0 &C1 &D2> > > OK> > > --> Modem initialized.> > > --> Idle Seconds = 300, disabling automatic> > reconnect.> > > --> Sending: ATDT13102068311> > > --> Waiting for carrier.> > > ATDT13102068311> > > CONNECT 34667> > > --> Carrier detected. Starting PPP immediately.> > > --> Starting pppd at Thu Apr 12 17:03:15 2007> > > --> pid of pppd: 7141> > > --> pppd: Username> > > --> Using interface ppp0> > > --> pppd: Username> > > --> pppd: Username> > > --> pppd: Username> > > --> pppd: Username> > > --> pppd: Username> > > --> pppd: Username> > > //... (about 25 more here)> > > --> pppd: Username> > > --> pppd: Username> > > --> pppd: Username> > > --> pppd: Username> > > --> pppd: Username> > > --> pppd: Username> > > --> pppd: Username> > > // Got fed up...> > > Caught signal #2! Attempting to exit> > gracefully...> > > --> Terminating on signal 15> > > --> pppd: Username> > > --> Terminate Request (Message: "User request" )> > > --> pppd: Username> > > --> Terminate Request (Message: "User request" )> > > --> pppd: Username> > > --> pppd: Username> > > --> pppd: Username> > > --> pppd: Username> > > --> Disconnecting at Thu Apr 12 17:03:53 2007> > >> > > I'm delighted to have been able to get on at all;> > now> > > I'm just> > > wondering if anyone has any idea how to make my> > > connection attempts any more> > > reliable.> > >> > > Oh - and Jacques, I created mybug3.txt as you> > asked,> > > but as the DNS> > > problem is now solved I'm not sure it would still> > be> > > useful. If it would,> > > I'll send it along.> > >> > > Finally, one last weird thing: in the terminal> > window> > > in which I loaded> > > the SmartLink driver, the symlink target keeps on> > > randomly jumping> > > around, like so:> > >> > > SmartLink Soft Modem: version 2.9.11 Feb 15 2007> > > 23:08:19> > > symbolic link `/dev/ttySL0' -> `/dev/pts/2'> > created.> > > modem `hw:0,6' created. TTY is `/dev/pts/2'> > > Use `/dev/ttySL0' as modem device, Ctrl+C for> > > termination.> > > symbolic link `/dev/ttySL0' -> `/dev/pts/5'> > created.> > > symbolic link `/dev/ttySL0' -> `/dev/pts/6'> > created.> > > symbolic link `/dev/ttySL0' -> `/dev/pts/2'> > created.> > > symbolic link `/dev/ttySL0' -> `/dev/pts/2'> > created.> > > symbolic link `/dev/ttySL0' -> `/dev/pts/6'> > created.> > > symbolic link `/dev/ttySL0' -> `/dev/pts/2'> > created.> > > symbolic link `/dev/ttySL0' -> `/dev/pts/5'> > created.> > > symbolic link `/dev/ttySL0' -> `/dev/pts/2'> > created.> > > symbolic link `/dev/ttySL0' -> `/dev/pts/2'> > created.> > > symbolic link `/dev/ttySL0' -> `/dev/pts/6'> > created.> > > symbolic link `/dev/ttySL0' -> `/dev/pts/2'> > created.> > > symbolic link `/dev/ttySL0' -> `/dev/pts/6'> > created.> > >> > > Not sure if this is important, but I thought I'd> > > mention it.> > >> > > Thanks again> > > - Dante> > >> > >> > > Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> a> > écrit> > > : Dante,> > >> > > RE: I inserted the "Detect Carrier = 0" line into> > > should be> > > Carrier Check = 0> > >> > > Before trying a dialout, do an> > > # ifconfig> > > If there are any COMM blocks shown except loopback> > > (lo), such as eth0,> > > do> > > # ifconfig eth0 down> > > or usages of DNS for other COMM channels will be> > > attempted and this> > > will not work.> > > Check with> > > # ifconfig> > > before dialing. It may be necessary to use the> > > Control Center to> > > shutdown other COMM channels.> > >> > > Also with /etc/ppp/options , a line may be> > needed:> > > usepeerdns> > >> > > MarvS> > >> > > On 4/12/07, Jacques Goldberg wrote:> > >> Dante,> > >> Are you using an other kind of connection> > (Ethernet,> > > ADSL, IrDA,..)> > > at> > >> the same time?> > >> You can see this by typing> > >> /sbin/ifconfig> > >> which should not contain blocks such as eth0> > >> If there is such a block, use /sbin/ifconfig eth0> > > down to get rid ot> > > it.> >> === message truncated ===>>>>
