hoastapd + bridge #2

[Tom Sharples]

Timo, the following may (or may not) be helpful to your situation:

> I'm new to WDS features of hostap and I'd like to know if is possible to
> a machine with hostap act simultaneous as:
> 1) client for another ap (managed mode)
> 2) master for another machine (master mode)


Current version supports this only if you are using two cards in the same 
host (and please also note that managed mode does not allow link-layer 
bridge functionality).
>
> Is this the case with ad-hoc mode as well? That might explain why I
> was having problems with ARP replies...

Yes, link-layer bridge works only in Master mode or when using WDS links 
('Repeater' mode in Host AP driver). ARP replies can (of course) be sent 
with the station's own address as the source address, but not with other 
addresses.

> Gah. Will bridging work for Managed-mode clients at all in the future?


No, IEEE 802.11 does not support this (ACK is sent to the source address of 
the unicast packets and only FromDS frames, i.e., the packets from AP, and 
WDS frames can sent these frames for other than own frames).

-- 
Jouni Malinen   Tom SharplesPresidentQorvus Systems, 
Inc.www.qorvus.net360.243.7371         ----- Original Message ----- 
From: "Timo Pannes" <timo.pannes at gmx.net>
To: <hostap at shmoo.com>
Sent: Tuesday, October 11, 2005 4:06 PM
Subject: **SPAM: hoastapd + bridge #2


> Hi again,
>
> unfortunately there was no answer to my previous question about bridging 
> with
> hostapd, so I will try again :)
>
> I want to set up an AP with hostapd and madwifi driver. Interface ath0 is
> connected to bridge br2, together with tap2. I've already inserted a line
> "bridge=br2" in my hostapd.conf, as suggested in another posting...
>
> When I start hostapd, everything seems to be OK:
>
>
> /home/flux/hostapd-0.4.5# ifconfig br2 192.168.254.10
> /home/flux/hostapd-0.4.5# ./hostapd /etc/hostapd/hostapd.conf
> Configuration file: /etc/hostapd/hostapd.conf
> Using interface ath0 with hwaddr 00:0f:3d:86:a1:ff and ssid 
> 'wellenreiter2'
> br2: port 2(ath0) entering learning state
> Flushing old station entries
> Deauthenticate all stations
> l2_packet_receive - recvfrom: Network is down
> br2: topology change detected, propagating
> br2: port 2(ath0) entering forwarding state
> ath0: creating bss 00:0f:3d:86:a1:ff
>
>
> But when a station wants to connect (using WPA) the following errors 
> occur:
>
>
> ioctl[IEEE80211_IOCTL_DELKEY]: No such file or directory
> ioctl[IEEE80211_IOCTL_SETMLME]: No such file or directory
> ath0: STA 00:04:e2:b3:5f:3a IEEE 802.11: deauthenticated due to local 
> deauth
> request
> ath0: STA 00:04:e2:b3:5f:3a IEEE 802.11: deassociated
> ath0: STA 00:04:e2:b3:5f:3a IEEE 802.11: associated
>   frame too short for this IEEE 802.1X packet
>   frame too short for this IEEE 802.1X packet
>   frame too short for this IEEE 802.1X packet
>   frame too short for this IEEE 802.1X packet
>   frame too short for this IEEE 802.1X packet
>   frame too short for this IEEE 802.1X packet
> ioctl[IEEE80211_IOCTL_DELKEY]: No such file or directory
> ioctl[IEEE80211_IOCTL_SETMLME]: No such file or directory
> ath0: STA 00:04:e2:b3:5f:3a IEEE 802.11: deauthenticated due to local 
> deauth
> request
> ath0: STA 00:04:e2:b3:5f:3a IEEE 802.11: deassociated
> ath0: STA 00:04:e2:b3:5f:3a IEEE 802.11: associated
>   frame too short for this IEEE 802.1X packet
>   frame too short for this IEEE 802.1X packet
>   frame too short for this IEEE 802.1X packet
>   frame too short for this IEEE 802.1X packet
>   frame too short for this IEEE 802.1X packet
>   frame too short for this IEEE 802.1X packet
> ioctl[IEEE80211_IOCTL_DELKEY]: No such file or directory
> ioctl[IEEE80211_IOCTL_SETMLME]: No such file or directory
> ath0: STA 00:04:e2:b3:5f:3a IEEE 802.11: deauthenticated due to local 
> deauth
> request
> .....
> ...
> ..
>
>
> Please help!
>
>
>
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap