Hi Eduard!

On Wed 02 Nov 2005 00:03 +0100, Luca Capello wrote:
> On Tue 01 Nov 2005 23:33 +0100, Eduard Bloch wrote:
>> So consider doing all the steps where it fails manually and run it
>> trough strace if neccessary. Your kernel may also be broken,
>> somehow.
>
> I'm sorry I cannot try a stock Debian kernel, as I need the ipw2100
> which isn't (yet) in any Debian kernel. If needed, I can provide my
> .config.

I wanted to figure out the problem, so I dug a bit...

I forgot to mention that I used a manually compiled (make-kpkg) 2.6.13
kernel, so I tried with Debian stock kernels:

- 2.6.13-1-686 + latest ieee80211 (m-a) + latest ipw2100 (m-a) works
  as expected, vpnc doesn't give any error and I'm on the VPN network
  (because I have access to scientific papers through the University
  network)

- 2.6.14-1-686 (no external modules, see bug #338775) works as
  expected (same as above)

I thought about a problem in my .config, but strangely a manually
compiled 2.6.14 with the same .config as the 2.6.13 works without any
problem. And the same happens for a 2.6.15-rc1.

So, as I still had an old version of the ieee80211 + ipw2100 drivers
on the 2.6.13 (old, but younger that the one included in the 2.6.14
kernel), I tried manually recompiling the 2.6.13 with the latest
ieee80211 and ipw2100. And now all it works :-D

In the meantime I upgraded every new package hit unstable (I upgrade
every morning), but I'm sure the problem still persisted before the
2.6.13 recompilation (I double checked, with two different ADSL
accesses).

I guess the problem wasn't on the vpnc side, but on the ieee80211
and/or ipw2100, but I cannot debug it anymore (and, sincerely, I don't
have a lot of time to do it).

My suggestion is to close the bug as unreproducible or not-a-bug.

Thx, bye,
Gismo / Luca

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=338775

Attachment: pgpvKA8sBcR5R.pgp
Description: PGP signature

Reply via email to