Hi Vouno, > thanks for your answer. > I'd like to have some more details. > > > >> The only way i found to reestabilish the connection is the reboot of the > >>computer. > > > >Hi Vouno, try applying the following patch to pppd's pppoatm.c: > > > I think this is a patch to apply to recompile the kernel so to "tell" to > pppoatm to use every device it is able to find.
no, there is no need to recompile the kernel. It is a patch to pppd: you need to recompile pppd. > Is it possible there isn't a way to tell to module pppoatm to look for > another device without recompile everything ? There is: if you use 0.8.35 (for example) in your pppd options file, then it will try to connect using atm device 0 (check out /proc/net/atm/devices). If you use 1.8.35 then it will try to connect using atm device 1. There is no need to modify pppd or the kernel to get this to work. However, if you want to say: "use any available device" then the syntax is *.8.35, which is supported by the kernel (more or less), but needs a tiny change to pppd: the patch I sent. You may wonder why I am talking about different atm devices here - after all, isn't there just one device, your modem? Yes there is, but I think you'll find that when the modem gets disconnected and reconnected, that it has reconnected as atm device 1, not atm device 0 anymore. If you have 8.35 in your options file, then pppd interprets this as 0.8.35 and will only connect via atm device 0. > I'm not able to read the code in pppoatm.c but somewhere there should be a > "pointer" to the device. > Maybe in /proc i could change something via script to give pppoatm the right > references. > What do you think about it ? Sorry, there is currently no way to do this. However, you could read /proc/net/atm/devices, work out which atm device the modem has connected as, and then pass the right x.8.35 (or whatever) option to pppd. > I'm actually using pppd 2.4.3 on kernel 2.6.8. If this is the only way to > solve the problem than i'll use it, but before i'll look more infos on this. > > Another strange thing is the disconnection and reconnection of the usb port. Yeah. Some usb chipsets are buggy (eg: VIA, maybe better nowadays); some have problems with the amount of current the original speedtouch modems draw. Also, a gazillion USB bugs have been fixed in the 2.6 kernels which haven't been backported to 2.4, so try a 2.6 kernel. > Googling around i found other references to this behavior, but all with old > kernels (2.4.x e 2.6.1). > > Last question. Where did you find this patch ? I couldn't find refs anywhere. It was easy for me to find because I wrote it :) There was a big discussion on the linux-atm mailing list some time ago, but I can't find it in the archive for some reason. Ciao, Duncan. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
