Atheros Wifi Configuration Error

[Peter_APIIT]

Dear All,

I'm tried to configure Atheros AR 5212 WIFI chipset access point but failed.

The /etc/hostname.ath0 configuration:

inet 172.16.1.2 255.255.255.0 media autoselect mode 11g mediaopt hostap \
nwid "Hacker" wpa wpaprotos wpa2 wpaakms psk \
wpapsk $(wpa-psk "Hacker" "Password")

This configuration results error at below.
Here is the error from dmesg file:

ath0 at pci1 dev1 function 0 "Atheros AR5212" rev 0x01pci_intr_map:bad interrupt pin 255: can't map interrupt

Besides, I'm also tried to configure it from terminal. It produces following error from this configuration.

ifconfig ath0 192.168.1.2 255.255.255.0

ifconfig: SIOCDIFADDR: Device not configured

What wrong with it? Thanks.

[ocicat]

Originally Posted by Peter_APIIT

I'm tried to configure Atheros AR 5212 WIFI chipset access point but failed.

It is customary to post the entire output of dmesg(8) when seeking support. One reason is that information about the version of the operating system will be provided. Wireless drivers, in particular, received frequent changes, so disclosing the version number is important when attempting to find out the root cause.

If I recall correctly, ath(4) has only recently supported configuration as an access point.

I highly recommend you read this thread on smart requests for support.

The /etc/hostname.ath0 configuration:

inet 172.16.1.2 255.255.255.0 media autoselect mode 11g mediaopt hostap \
nwid "Hacker" wpa wpaprotos wpa2 wpaakms psk \
wpapsk $(wpa-psk "Hacker" "Password")

Three comments:

• Is there a reason you are making configuration so complicated? The manpage for ath(4) for OpenBSD 5.7 provides a simple example for host configuration:
  

  inet 192.168.1.1 255.255.255.0 
  mediaopt hostap 
  nwid mynwid 
  wpakey mywpakey

• When first attempting configuration, starting with a simple configuration avoids all kinds of pain.
• What is wpa-psk? This entire line:
  

  wpapsk $(wpa-psk "Hacker" "Password")

  ...is syntactically incorrect.

Here is the error from dmesg file:

If this indeed is the error found in dmesg(8), you may be out of luck with this unknown version of the OS. Manufacturers can insert new overlays into the production process at different points, & not change the version number of the chip. To speculate any further will require more information than has been disclosed thus far.

What wrong with it?

If this configuration comes from a howto found somewhere on the Internet, don't accept it as correct. Was any information provided as to what version of OpenBSD was used for testing? Was it ever correct for any version? Starting with information found in the manpages is always the best place to begin.

[Peter_APIIT]

Thanks ocicat point out that should starts from simple configuration. I had tried the configuration you posted here.

inet 192.168.1.1 255.255.255.0 
mediaopt hostap 
nwid mynwid 
wpakey mywpakey

Perhaps I'm should post the full dmesg here later.