Hi Vladimir,

The physical 802.11 WNIC is IP configured by DHCP from the ISP. Does 
this require DHCP "trickery" to transfer this information
to the virtual 802.3 NIC under VirtualBox that is supplied to the MS Win 
guest?

Yasha Karant

On 10/30/2015 08:27 AM, Vladimir Mosgalin wrote:
> Hi Yasha Karant!
>
>   On 2015.10.29 at 13:28:21 -0700, Yasha Karant wrote next:
>
>> You seem to display a bridge between an 802.3 (eth) and an 802.11 (wnic).
> Right.
>
> Note that I only did that for purposes of software AP. This is router
> which provides both wired and wireless network connectivity, which are
> bridged for network uniformity (no routing, broadcast and multicast
> passing, no dhcp forwarding trickery and so on).
>
> I can show you configuration but it doesn't mean that it would work for
> you with wireless NIC not in AP mode. That said, if THIS way won't work
> for you, it doesn't mean it's impossible at all: try Open vSwitch! It is
> much more agile compared to standard linux bridging, especially in areas
> related to bridging between multiple interfaces created on the fly,
> VLANs and such, making it very useful on virtualization hosts.
>
>> In any event, a copy (typescript, screenshots, etc.) of the actual commands
>> you used, any needed configuration files, and a copy of any outputs produced
>> during the activation/configuration greatly would be appreciated.
> I set up bridge in NM with nmtui. You can find guides on setting it up
> with NM GUI / nmcli combo, e.g.
> https://www.happyassassin.net/2014/07/23/bridged-networking-for-libvirt-with-networkmanager-2014-fedora-21/
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Network_Bridging_Using_the_NetworkManager_Command_Line_Tool_nmcli.html
>
> NM creates bridge0 and adds eth0 to it, sets up IPs and such after that.
> Wireless device wlan0 is set up much later, and hostapd adds wlan0 to
> that bridge after it finishes configuring wireless lan. It's impossible
> to add uncofigured wlan0 device to bridge.
>
> Either way, the resulting configuration files look like
>
> $ cat /etc/sysconfig/network-scripts/ifcfg-bridge0
> DEVICE=bridge0
> STP=no
> TYPE=Bridge
> BOOTPROTO=none
> DNS1=127.0.0.1
> DOMAIN=asgard
> DEFROUTE=no
> IPV4_FAILURE_FATAL=no
> IPV6INIT=yes
> IPV6_AUTOCONF=no
> IPV6ADDR=<removed>
> IPV6_DEFROUTE=no
> IPV6_FAILURE_FATAL=no
> NAME=bridge0
> UUID=c10629d4-3fc8-4987-98d2-b82799419e49
> ONBOOT=yes
> IPADDR=192.168.2.1
> PREFIX=24
>
> $ cat /etc/sysconfig/network-scripts/ifcfg-bridge0_eth0
> TYPE=Ethernet
> NAME=bridge0_eth0
> UUID=a3810633-5171-4946-9e60-f3a09bd7f4e7
> DEVICE=eth0
> ONBOOT=yes
> BRIDGE=c10629d4-3fc8-4987-98d2-b82799419e49
>
>
> I won't publish the whole hostapd.conf file, related lines are
>
> interface=wlan0
> bridge=bridge0
>
>
> As for the log file, here are the lines related to eth0/wlan0/bridge0
> initialization:
> http://pastebin.com/zVjfcqBj
>