#407: bridged mode wont work
---------------------------------+------------------------------------------
Reporter: anonymous | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: other | Version: trunk
Resolution: | Keywords:
Patch_attached: 0 |
---------------------------------+------------------------------------------
Changes (by mrenzmann):
* version: => trunk
Old description:
> {{{
> I have the latest svn release for madwifi-ng and a Dlink DWL-530AG.
> The ath0 it autocreated works fine and was able to connect to my AP.
>
> However, I want to use this ath0 interface in bridged mode, but it
> doesn't seem to work.
>
> This is what i see in the logs:
>
> bridge-ath0: enabling the bridge
> bridge-ath0: can't bridge with ath0, bad header length 88
> bridge-ath0: interface ath0 is not a valid Ethernet interface
> bridge-ath0: can't bridge with ath0, bad header length 88
>
> I'm trying the bridge with VMware Workstation. I ran the vmware-config.pl
> and tried to use ath0 in bridged mode.
>
> thanks.
> }}}
New description:
I have the latest svn release for madwifi-ng and a Dlink DWL-530AG.
The ath0 it autocreated works fine and was able to connect to my AP.
However, I want to use this ath0 interface in bridged mode, but it doesn't
seem to work.
This is what i see in the logs:
{{{
bridge-ath0: enabling the bridge
bridge-ath0: can't bridge with ath0, bad header length 88
bridge-ath0: interface ath0 is not a valid Ethernet interface
bridge-ath0: can't bridge with ath0, bad header length 88
}}}
I'm trying the bridge with VMware Workstation. I ran the vmware-config.pl
and tried to use ath0 in bridged mode.
thanks.
Comment:
What do you mean with "I'm trying the bridge with VMware Workstation"? You
try to use it inside a VMWare bridge, and the message you see actually
comes from VMware?
--
Ticket URL: <http://madwifi.org/ticket/407>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
