On Mon, 2009-07-13 at 14:23 -0400, Dan Williams wrote: > On Sat, 2009-07-11 at 15:16 +0200, Ali Servet Donmez wrote: > > 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? > > It's likely that either WEP isn't being set up correctly by the driver > on the source machine (using another laptop and running 'iwlist > <devname> scan' will show pretty quickly what's going on), or that > you're not using the right WEP password/key on the other machine. > > What *exact* option are you choosing from the menu when setting the WEP > key for the adhoc shared network? Are you choosing "WEP 128-bit > passphrase" or "WEP 64/128-bit Key"? Windows XP by default doesn't > recognize passphrases (only vendor utils like D-Link, Linksys, Belkin > do), and Mac OS X doesn't recognize passphrases either because Apple > uses a different "password" scheme that's incompatible with everything > else. > > I'd suggest entering the *full* 26-character "Hex" key into > NetworkManager, which is likely guaranteed to work everywhere. Apple > calls this key the "Compatible Network Password", and typing it into the > Windows Zero Config network password dialog should work as well. > > The "13 digit ASCII" passphrase you talk of probably won't work very > well cross-platform. Yeah, you're right! The problem was that I wanted to use passphrase approach, but apparently that didn't work well. 23 character Hex key works, and now OS X machine is connected with WEP. Someday I could also try WPA2 Personal/Enterprise too, but I don't care at the moment. Thanks a lot, again! Btw, don't you think NetworkManager should be a little bit more descriptive about all these? I don't think that any average user could get this work out of the box? Regards, -- Ali Servet Donmez <asd pittle org>
Attachment:
signature.asc
Description: This is a digitally signed message part