On Tue, 2009-04-28 at 12:01 -0400, Dan Williams wrote: > On Sun, 2009-04-26 at 15:02 +0200, Ali Servet Donmez wrote: > > On Wed, 2009-04-08 at 15:21 -0400, Dan Williams wrote: > > [...] > > > > > /var/log/daemon.log or /var/log/NetworkManager.log would be useful. > > > > Dan, sorry for waaay too late reply. Below I'll paste all logging info > > that I could capture: > > So this looks like the problem > > Apr 26 14:46:20 leilam dnsmasq[6434]: failed to bind listening socket for 10.42.43.1: Address already in use > Apr 26 14:46:20 leilam dnsmasq[6434]: FAILED to start up > > I wonder if there's still a dnsmasq running bound to that address? Oh, when I checked if there's a dnsmasq process running, I've found this: /usr/sbin/dnsmasq -u dnsmasq -r /var/run/dnsmasq/resolv.conf ... so: sudo /etc/init.d/dnsmasq stop ... killed that one. After that, I seem to be able to share my connection in ***secureless mode only***. Now, first successfully connected client will have this configuration: IPv4 Configuration: DHCP IPv4 Address: 10.42.43.10 Subnet Mask: 255.255.255.0 Router: 10.42.43.1 ... while in "WEP 128-bit Passphrase" secured mode --I've picked a 13 digit ASCII passphrase--, so called connected, client will have this configuration instead: IPv4 Configuration: DHCP IPv4 Address: 169.254.114.137 (No idea what this is...) Subnet Mask: 255.255.0.0 (Uh oh...) Router: ***No router found*** (Ouch!) ... as you can image, obviously, in WEP secured mode client isn't really connected. What do you think now the problem is? How could I provide you further info. for this one? > Then at some point, your ipw2200 card goes off into the weeds: > > Apr 26 14:47:04 leilam kernel: [ 776.689496] ipw2200: Failed to send > SYSTEM_CONFIG: Already sending a command. > > what kernel version and what ipw2200 firmware version? kernel version: 2.6.27-14-generic ipw200-fw version: 3.1 Thanks a million so far Dan! [...] Regards, -- Ali Servet Donmez <asd pittle org>
Attachment:
signature.asc
Description: This is a digitally signed message part