On 17/07/2010, montmarte <[email protected]> wrote:
> Great News at last!. Turns out that I was making a silly mistake but somehow
> went undetected. For the <nwkey> value as part of ifconifig, I was not
> giving a hex value, i.e.,
>
> #ifconfig ath0 192.168.1.3 255.255.0. nwid <nwid> nwkey 1234
>
> whereas I should have been giving
>
> #ifconfig ath0 192.168.1.3 255.255.255.0 nwid <nwid> nwkey 0x1234
>
> then I do /etc/netstart, lo behold! everything starts working, dhclient
> starts working, ping google.com starts working.
Hooray.
> But what is puzzling to me why my error was never detected, should "ifconfig
> ath0 scan" work if I have given the wrong nwkey?.
As far as my wireless knowledge goes a scan looks for SSIDs without
connecting. Hence password not required. Even without knowing your
neighbours WEP key you can see his network is up and running right?
I guess OpenBSD scan is exactly the same. :]
>From ifconfig(8):
scan Show the results of an access point scan. In Host AP mode, this
will dump the list of known nodes without scanning.
> If it had thrown some
> error, then I could have been focusing my time on giving the right
> parameters for ifconfig, rather it made me look all over the system, until I
> stumbled upon the solution by having a N-th look at the man page for
> ifconfig. This problem literally drove me nuts.
Welcome to the club of those who have at least one problem getting
something working. All welcome.
However also welcome to the club where membership is reading them
there pages until you find the answer. Good for you.
Sometimes it's a paper trail but the man pages are great. I think I'm
getting a bit better at it.
As far as ifconfig not doing everything for you, it might be a case of
no-one seeing a deficiency before. Besides, adding every feature comes
at a price.
You could post to tech@ - apologize for your fat fingers and let
people know you're almost as dopey as me (i.e. you have no skills and
can't write a patch to save yourself).
You'll either get told to buy a book on C, shut up and/or go away,
someone might write a patch. What have you got to lose ...
> -m
Make sure you fix up your resolv.conf file. :]
Best wishes.
_______________________________________________
Openbsd-newbies mailing list
[email protected]
http://mailman.theapt.org/listinfo/openbsd-newbies
