SCIENTIFIC-LINUX-USERS Archives

October 2015

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Sat, 31 Oct 2015 11:19:54 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (45 lines)
On Thu, Oct 29, 2015 at 12:11 PM, Vladimir Mosgalin
<[log in to unmask]> wrote:
> On 2015.10.29 at 03:24:37 -0400, Tom H wrote next:
>>
>> You cannot bridge a wireless NIC:
>>
>> http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge#It_doesn.27t_work_with_my_Wireless_card.21
>>
>> It's been disabled in the kernel's bridging code since 2.6.34 (AFAIR).
>
> Umm this is on SL7.1 which uses kernel 3.10
>
> $ brctl show
> bridge name bridge id STP enabled interfaces
> bridge0 8000.002590c73bd6 no eth0
> wlan0
> $ cat /etc/sl-release
> Scientific Linux release 7.1 (Nitrogen)
>
> I created bridge0 with NM and changed local ethernet to be its slave,
> after that hostapd bridged it with wlan0 with the following config
> interface=wlan0
> bridge=bridge0
>
> The wireless NIC was the random one that I got in package with some
> other motherboard, I didn't mess with firmware or anything like that
>
> $ lspci | grep Wireless
> 01:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
>
> Somehow I doubt that I managed to fall into 1% of users who has special
> card with special firmware. The documents you linked must not be telling
> the whole story. Or just outdated, as it was written in the 2009.

I'd say that you fall into the special 0%! LOL

More seriously, hostapd is a third (ebtables, proxy-arp) way to solve
the problem.

From linux-4.2.5/net/bridge/br_if.c

        /* No bridging devices that dislike that (e.g. wireless) */
        if (dev->priv_flags & IFF_DONT_BRIDGE)
                return -EOPNOTSUPP;

ATOM RSS1 RSS2