My problem is succinctly described on :

I have a Netgear MA311 PCI card installed and properly recognized on my
desktop machine. The box does not say so, but I have found links on the web which state that it can be used as an access point.

I compiled hostap-0.0.4 (using make pci ) and also the hostapd daemon (my /etc/hostapd.conf is at the end of this
email).
I am trying to set up this card as an Access Point.

My client is a properly configured and working Netgear MA401 PCMCIA card in my notebook.

I get the following messages on console on the DHCP server :

( I have obfuscated my client MAC address as cl:cl:cl:cl:cl:cl and Access Point MAC address as ap:ap:ap:ap:ap:ap for security purposes. The essid is also obfuscated as something.)

[root@sggs root]# hostapd /etc/hostapd.conf
Configuration file: /etc/hostapd.conf
Opening raw packet socket for ifindex 16
Using interface wlan0ap with hwaddr ap:ap:ap:ap:ap:ap and ssid 'something'
Default WEP key - hexdump(len=13): e5 54 ef 72 0a 7f 1e 90 8f 09 d7 aa 44
Flushing old station entries
Deauthenticate all stations
Received 26 bytes management frame
MGMT
MGMT: BSSID=09:b3:b2:36:ca:37 not our address
Received 30 bytes management frame
MGMT
mgmt::auth
authentication: STA=cl:cl:cl:cl:cl:cl auth_alg=0 auth_transaction=1
status_code=0 wep=0
authentication reply: STA=cl:cl:cl:cl:cl:cl auth_alg=0 auth_transaction=2
resp=0
Received 30 bytes management frame
MGMT (TX callback) ACK
mgmt::auth cb
wlan0: STA cl:cl:cl:cl:cl:cl IEEE 802.11: authenticated
Received 44 bytes management frame
MGMT
mgmt::assoc_req
association request: STA=cl:cl:cl:cl:cl:cl capab_info=0x01 listen_interval=1
old AID 1
Received 36 bytes management frame
MGMT (TX callback) ACK
mgmt::assoc_resp cb
wlan0: STA cl:cl:cl:cl:cl:cl IEEE 802.11: associated (aid 1)

/etc/hostapd.conf :

interface=wlan0
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
debug=2
dump_file=/tmp/hostapd.dump
daemonize=1
ssid=something
macaddr_acl=1
accept_mac_file=/etc/hostapd.accept
deny_mac_file=/etc/hostapd.deny
auth_algs=3
minimal_eap=0
eap_message=hello
wep_key_len_broadcast=13
eapol_key_index_workaround=0
own_ip_addr=127.0.0.1

/etc/hostapd.deny is empty, /etc/hostapd.accept contains cl:cl:cl:cl:cl:cl.

Excerpts from my /sbin/ifconfig (on the access point) :

wlan0 Link encap:Ethernet HWaddr ap:ap:ap:ap:ap:ap
inet addr:10.0.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:238 errors:0 dropped:53 overruns:0 frame:0
TX packets:14 errors:2 dropped:1 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:724 (724.0 b)
Interrupt:11 Memory:d08d2000-d08d3000

wlan0ap Link encap:UNSPEC HWaddr
ap-ap-ap-ap-ap-ap-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:2290 Metric:1
RX packets:156 errors:0 dropped:0 overruns:0 frame:0
TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:8672 (8.4 Kb) TX bytes:1612 (1.5 Kb)
Interrupt:11 Memory:d08d2000-d08d3000

On the client, my wireless link monitor shows a signal strength of about 89 % and /sbin/iwconfig indicates the correct MAC address (I hope its not my neighbour's access point but the essid is "something" on both client and server and that gives me some confidence !) in the Access Point o/p. That means that it is picking up the signal from my desktop. But I can't seem to use ssh or anything like that.

What could be wrong ? A misconfiguration of the DHCP server ? (I am using two different subnets - one (192.168.0.1/24) for the crossover cable and the other (10.0.0.1/24) for the wireless).)

One ancillary question - when I use WEP, what extra stuff do I need to do for the client ?

I still cannot get a dhcp lease on the client. Please look the above over and let me know if everything is alright from the wireless standpoint.

My /etc/dhcpd.conf :

default-lease-time 28800;
max-lease-time 86400;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;

# Optional Stuff (add/use if you have it)
# Activate by removing the '#'.
option domain-name-servers 198.110.19.8,198.108.1.42,141.213.6.1;
option www-server 207.75.181.2,141.213.6.5,141.213.6.1;
ddns-update-style ad-hoc;

subnet 192.168.0.0 netmask 255.255.255.0
{
range 192.168.0.3 192.168.0.10;
}

subnet 10.0.0.0 netmask 255.255.255.0
{
range 10.0.0.3 10.0.0.10;
}
host clientwireless
{
hardware ethernet cl:cl:cl:cl:cl:cl;
fixed-address 10.0.0.2;
}

(there is another entry for the wired ethernet connection (called
clientwired), but that is not pertinent as its IP address is 192.168.0.2
(works perfectly).

Any ideas where I am going wrong ?

Thanks,

MS

i don't know if you fixed this problem (old post), but were you able to get everything working? i have some of the same hardware and i use hostap, so maybe i could help.

if you did get it working, let me answer your question with a question: how does one go about setting up the wireless encryption using hostap?

i figured i'd ask before i tried it, as i don't have a lot of time to fiddle with my encryption.

cheers,
y-p