Here on Win/Iexplorer: Linux denies Access to the Net?

JZL240I-U · 07-03-2004, 09:12 AM

Well, yes, I'm here on Win and IExplorer. But what can I do?

Facts: When I start Kinternet on my SuSE 9.0pro I can hear the modem dialling, getting connection for a short time (?) and before anything is displayed the connection dies on me. I did a

Code:

ps -A | grep ppp

resultuing in

Code:

smpppd (Suse-Meta-pppd)
smpppd-ifcfg (Suse-Meta-pppd config???)
pppd

during the procedure, but no process actually dies when the modem shuts down. Huh? Works with windows, though

, so I have to give that some credit for a little relief.

Now, what could be the cause? I had a little trouble with privoxy lately (see here ) but I deinstalled it and I don't use any proxies anymore for the moment.

Anybody any ideas / experiences / help -- please?

ping_wing · 07-04-2004, 12:50 PM

what modem you have?

I havent used modem for long time, but i remember from my experiences that some modems wanted reset before every dialing.

I mean sending reset code, it was ATZ if im correct.

hope this helps little

cheers,
http://www.axeltabs.com/

__
axel

JZL240I-U · 07-05-2004, 02:50 AM

It is a US-Robotics 56k Messenger Professional and it gets its reset (I think its two strings actually, first the ATZ (?) then a longer one for initializing). I did not change anything in the protocols etc. the only changes concerned privoxy and those I cancelled. I don't understand this behaviour. If it persists I'll have to reinstall like under Windows...

JZL240I-U · 07-06-2004, 04:28 AM

Well, well, well.

And it wasn't the fault of Linux at all after all. For those who are interested I'll post some more information on the symptoms, so that you can easier diagnose this sort of problems, should they arise on your machines:

I dug in the logs after searching with "locate .log". No luck. Then I happened upon the directory /var/log which holds /var/log/localmessages (SuSE 9.0pro, dunno whether the others have it too). It holds the modem log. When all is healthy it looks like:

Code:

SuSE Meta pppd (smpppd-ifcfg), Version 1.06 on linux.
Status is: disconnected
trying to connect to smpppd
connect to smpppd
Status is: disconnected
Status is: connecting
pppd[0]: Plugin passwordfd.so loaded.
pppd[0]: --> WvDial: Internet dialer version 1.42
pppd[0]: --> Initializing modem.
pppd[0]: --> Sending: ATZ
pppd[0]: ATZ
pppd[0]: OK
pppd[0]: --> Sending: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
pppd[0]: OK
pppd[0]: --> Sending: ATM1
pppd[0]: ATM1
pppd[0]: OK
pppd[0]: --> Modem initialized.
pppd[0]: --> Sending: ATDT019231770
pppd[0]: --> Waiting for carrier.
pppd[0]: ATDT019231770
pppd[0]: CONNECT 45333/ARQ/V90/LAPM/V42BIS
pppd[0]: --> Carrier detected.  Waiting for prompt.
pppd[0]: ~[7f]}#@!}!!} }8}"}&} }*} } }#}$@#}%}&$X} N}'}"}(}"3Q~
pppd[0]: --> PPP negotiation detected.
pppd[0]: Serial connection established.
pppd[0]: Using interface ppp0
pppd[0]: Connect: ppp0 <--> /dev/ttyS0
pppd[0]: local  IP address xxx.yyy.zzz.aaa
pppd[0]: remote IP address bbb.ccc.ddd.eee
pppd[0]: primary   DNS address fff.ggg.hhh.iii
pppd[0]: secondary DNS address jjj.kkk.lll.mmm
pppd[0]: Script /etc/ppp/ip-up finished (pid 2652), status = 0x0
Status is: connected
Status is: disconnecting
pppd[0]: Terminating on signal 15.
Status is: disconnecting
pppd[0]: Script /etc/ppp/ip-down finished (pid 2750), status = 0x0
Status is: disconnected
pppd[0]: Connection terminated.
pppd[0]: Connect time 2.1 minutes.
pppd[0]: Sent 116910 bytes, received 380321 bytes.
pppd[0]: Hangup (SIGHUP)
pppd[0] died: pppd received a signal (exit code 5)

Now it ran:

Code:

...
pppd 2.4.1 started by root, UID 0
Serial connection established
Using Interface ppp0
Connect ppp0 <--> /dev/ttyS0
Serial line is looped back
Connection terminated
Exit
...

It may also have a line like

Code:

Removed stale lock

From an earlier attempt to dial in.

The line Serial line is looped back shows the culprit. It is very well explained
here. In brief, the server you want to connect to "reflects" your packets of bits and bytes back to your modem and ppp0 feels it "gets hoaxed" and thus shuts down.

Thus the error was caused by the provider. In my case they ever so quietly changed phone number, user name and password (I use Internet by call) though to cause the "reflections" something must still live at the old target or else I would have got timeouts. I won't go so far as to think that this had something to do with my using Linux and the provider being ... MSN

.

JZL240I-U · 07-16-2004, 03:06 AM

Urgh. No, it was not solved. I don't know what really happened then, but in the meantime I had to rebuild my entire system ... and the problem started again even with the new username and password.

The true solution:

I had to "dumb down" the modem, since it was not running in "stupid mode" (honestly! that's what they call it

). That just means changing the parameter in the modem configuration file like

Code:

stupid mode yes

I did it with Yast -> Internet -> Modem -> change (selected modem) -> next -> check in the tick box -> stupid mode on -> Finish...

Ah, well I guess I ran in stupid mode instead of the modem. I won't forget this one

.

Komakino · 07-16-2004, 04:54 PM

So to dial to MSN you need to be stupid?

How appropriate

JZL240I-U · 07-19-2004, 01:29 AM

At first glance you could be right. But ...
µsoft is accrueing losses from that service here, so I thought I might use it