[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Vanilla kernel >=2.4.28 incompatibility with ADSL modem Dlink DSL-G300+



  Hello,
I found a problem having to to with the plain vanilla 2.4.28 and 2.4.29 kernels when I try to use a Dlink DSL-300G+ ethernet ADSL modem on a SS5 machine. If you think I should send this email to some kernel-specific mailing list please let me know which one.

The domain "route-add.net" is running on a Sun SparcStation 5 machine, equipped with a Micro-SPARCII, 85 MHz processor. This machine has beeing running the domain (web, smtp, ssh, imap, telnet, gopher, finger, auth/ident, dns) for a year. The machine has two "le" (10 base T) ethernet ports, one is connected to the ADSL modem, the other to the LAN.
  The OS is Debian stable (Woody, 3.0).
The kernel is a plain vanilla one, downloaded from ftp.it.kernel.org/pub/linux/kernel/v2.4 with no patches applied to it.

The problem: after updating to kernel 2.4.28, the ADSL connection would never outlive the fifteenth minute. Even though the modem still sensed the ADSL carrier and could be reached into its web-based internal control panel over the same ethernet connection that served the data exchanged with the ISP, after fifteen minutes it could first reach the ISP gateway the connection failed and no packets could be neither sent nor received with any host outside the LAN. The connection would be available again after a period varying from a few minutes to several hours, three quarters of an hour on the average. A script that was let running from Jannuary 18th to February 3rd (data from Jannuary 29th was lost) produced the following data:

http://route-add.net/ping-noping.txt ("riuscito" = success, "fallito" = failed)
http://route-add.net/ping-noping_18012005-28012005.txt
http://route-add.net/ping-noping_07012005-17012005.txt ("persa" = lost [connection], "tornata" = [coonection is] back)

I tried changing the wiring, I swapped the ethernet ports the LAN and ADSL modem where connected to, I swapped the modem with an identical one from a colleague of mine, I upgraded to kernel 2.4.29 all to no avail. On December 29th, as I was suggested to do by the ISP technician I phoned, I tried connecting the modem to a Ultra10 machine running Solaris9, and it worked. Now the SS5 is back online with the old, 2.4.27 kernel from December, and the problem has not manifested again these past two and a half hours.

  What the hell can it be?  How can it be tested?
Any suggestion will be very appreciated.

--
Alessandro Selli
Tel: 340.839.73.05
http://alessandro.route-add.net



Reply to: