Hallo Leonard,
First of all, thannks for replying. It seems it has been partially
solved, but I'm not too sure because after reboot the adsl-led stays
amber and pppd call speedtch says that the network is temporarily
unavailable. I haven't been rebooting again, but it works with wxp. It
could very well be that there was indeed a connection problem, because
wintendo didn't want to connect immediately as usual.
Hallo Irene,
Since I was having downstream problems with the user space driver and
the alcaudsl.sys firmware, I installed the latest Debian speedtouch
packet and built in the kerneldriver (2.4.22).
I have no experience with the kernel driver yet, but since nobody else
jumps in I thought I might give you at least some answers.
I'm using the firmware file from
http://speedtouch.sourceforge.net/index.php?/download.en.html now.
I have been using the KQD6P2.eni with the user mode driver for quite a
while now (http://download.ethomson.com/download/KQD6_R204.zip).
I've tried that one too
Ping gives messages like unknown host, also when I use an IP
address.
Really? Or just time outs in the latter case? By the way, can you ping
both ends of the point to point connection? Have you tried traceroute and
seen how far a trace gets?
Yes I did, I didn't get anything.
I shut down the firewall, but no way. I put the modem_run options
-m -f -s in the script, that didn't work either. Could it be that I should
remove netfiltering modules from the kernel?
If all chains are set to ACCEPT you should be ok. No need to remove the
netfiltering modules.
Iptables -L -n gives IP-addresses with only zero's.
Don't forget the -v option, which shows to which interface the rules
apply. The zero's are just IP catch alls, its the destination
(ACCEPT/DROP) that matters.
I believe something like that was the problem. The destination did not
match what I got from cybertools (net checking thingy for windoze). I
checked every file having anything to do with the connection and
firewalls, and to be /really/ sure I removed most of the firewalling
stuff from the kernel. I checked and reset everything again with
debconf, and voila! Suddenly I was online at 40 kbps! Obviously I had it
all configured wrong, although I still don't understand how I was even
able to connect before.
Btw, it doesn't seem to be possible to go back to my original
configuration, it just doesn't work anymore somehow. And I would still
have the crappy downstream: it used to be around 15 kbps instead of the 42 I
get sometimes with Wintendo, which I'm forcibly using now.
The user mode driver gives me a 40KB/s ftp download speed (same modem as
you, same line specs, but using the KQD6P2.eni firmware).
Although I don't feel I can pinpoint the problem you are having I hope
this is of some use. Maybe somebody with experience with the kernel mode
driver can jump in...
I suppose the KQD6P2.eni should work now as well, but I really don't
feel like changing around again since that caused me trouble getting the
thing back to work again after all. For the first time, I have been able
to even connect with the kernel mode driver and since the Debian-readme
in the speedtouch packet claims that one is preferred, I suspect it is
a good idea to stick to that. I noticed that if you follow the
instructions in the readme and read the howto in the packet carefully,
it should all work. There is also a Debian Sarge howto on sourceforge,
but the stuff that it says about installing the right hotplug script in
/etc/hotplug/usb/speedtch
you should ignore.
Thanks for the response anyway, I'm going to reboot and try again.
Bye, Irene
Alright, got the thing going finally. In the script provided by the
Debian package (/etc/hotplug/usb/speedtouch) I removed the modem_run
options I put there earlier. Now it runs great with no options there.
It might be useful for somebody else to know as well, perhaps, so I
figured I should post how the problem was solved after all.
Bye, Irene
Liste de diffusion modem ALCATEL SpeedTouch USB
Pour se désinscrire : mailto:[EMAIL PROTECTED]
