Today I tried to get connected using linuxconf for setup. Nice programm, but doesn't have TCP/IP in it. To the best of my ability setup PPP, but didn't get any signs of life.
Gave a call to my ISP. The answer was:
1. For Linux they need to setup something on their server
2. They don't support Linux
3. He will email to his boss, and the boss will email me within 48 hours about what can be done.
The lack of TCP/IP was a kind of surprise. I always thought it came from Unix world.
Errr, what do you mean it doesn't have tcp/ip? It's part of the
kernel, there is no way to take tcp/ip OUT of linux: it's not
an option. Furthermore, if your ISP offers PPP, then ppp is ppp is
ppp, has nothing whatsoever to do with Windows or Linux. Of course
you can get connected.
The problem with setting up a ppp connection to an isp is that
the server may reply strange things. Happened to me. What you
do is the following: use control-panel , go to the network thingie,
say you want a brand new ppp (or you want to edit the one you have),
and then be sure to check on DEBUG THE CONNECTION. That way,
whenever you try to connect (your modem does go piii paa paaa, right?)
the full log will be written on /var/log/messages . You will see
what you get from the ISP and what your script was expecting.
In my case, I was expecting "login:" and was getting "UserId:",
and there was also an issue of the script expecting "CONNECT 28800"
from the modem and the modem replying "CONNECT 192600" (ha!! I wish!).
Other option is to connect by hand using cu, taking note of what you
see, and then take it from there.
The script in question is somewhere on /usr/sysconf/network-scripts/chat or something like that.
PPP setup is definitely not ready for prime time. However,
let me assure you that you CAN get connected, and wish you
best of lucks. Or, even better, try again and ask again.
Best,
m |
