Robert-Jan Kuijvenhoven:
> The problem is that dselect fails to connect. Dselect shows the following
> message:
>
> Connecting to ftp.debian.org
> Failed to connect
The ftp program normally doesn't dial the modem for you, because it doesn't
know whether you aren't just intending to use the ethernet, or even just
connect locally. (Which is usually not done with ftp, but sometimes is with
other things.)
You *can* set up your network so that whenever any program tries to contact
a remote computer it'll dial your ISP, if you want, but first you should
set it up so it works manually using the pon command.
So if I am correct, de pon command should establish a connection? Well, it does
not connect. Some lights on the modem flash (DTR, RTS, RxD, TxD), but not the
session light, which usually indicates that there is a connection.
> If I try the pon command, some of the lights of my modem flash, but when
> dselect is trying to connect, the modemlights don't flash. My modem is a
> cable modem, which can be configured just like a normal 28k8 modem.
After you do pon, can you ping your ISP's computer? Like this:
ping machine.isp.com
No, unable to locate host, but that's probably because there is no
connection.
If so, try pinging ftp.debian.org
If neither of these says anything, try the command `ifconfig' which will
tell you about all the network interfaces - it should list a loopback, any
ethernet cards you have configured, and the ppp link. `ifconfig -a' will
also list any interfaces that are currently down.
There are no ethernet cards in my computer.
Ifconfig -a gives the following result:
Lo Link encap:Local Loopback
Inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metrics:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Collisions:0
ppp0 Link encap:Point-to-Point Protocol
inet addr:0.0.0.0 P-t-P:0.0.0.0 Mask:0.0.0.0
POINTOPOINT MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Collisions:0
Memory:1b0f038-1b0fc04
The ppp0 part will only show, if I give the ifconfig -a command, immediately
after a pon.
Once the ppp link is UP and RUNNING, the `route' command will tell you how
the kernel thinks it ought to route packets. It should probably have a
none-of-the-above entry at the end that points to the ppp0 Iface.
Oh yeah, does /var/log/ppp.log or /var/log/syslog contain anything
interesting?
ppp.log:
pppd 2.3.5 started by root, uid0
abort on (BUSY)
abort on (NO CARRIER)
abort on (VIOCE)
abort on (NO DAILTONE)
abort on (NO ANSWER)
send (ATZ^M)
expect (OK)
^M
NO CARRIER
-- Failed
Failed (NO CARRIER)
Connect script failed
exit.
These log items are also in syslog, but other than that syslog looks ok.
HTH
Jiri
--
<[EMAIL PROTECTED]>
We'll know the future has arrived when every mailer transparently
quotes lines that begin with "From ", but no-one remembers why.
