Re: KVM Bridge wlan0
Different config similar result
did not email actual ssid, psk. I’m a idiot not a moron.
I do not know that I want to bridge eth0 to wlan0.
I have one working interface on my computer wlan0. I want a virtual machine using KVM to be able to communicate to the internet using wlan0. All documentation I can find indicates that is done with a bridge. All documentation I can find indicates you do this with eth0. I do not use eth0. I have wlan0.
changed /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# manual wifi configuration
# using wpa_pashphrase to generate wpa-psk string
auto wlan0
iface wlan0 inet manual
wpa_ssid XXXXX
wpa-psk xxxxx
pre-up /sbin/iw dev wlan0 set 4addr on
auto br0
iface br0 inet static
address 192.168.1.100
network 192.168.1.0
netmask 255.255.255.0
broadcast 192.168.1.255
gateway 192.168.1.1
dns-nameservers 199.231.188.115
dns-nameservers 128.199.172.116
bridge_ports eth0 wlan0
bridge_stp off
bridge_fd 0
bridge_maxwait 0
good new! I now have br0 with eth0 and wlan0.
bad new! now the laptop no longer has any internet connectivity.
ifconfig
br0 Link encap:Ethernet HWaddr 2c:60:0c:2f:be:18
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth0 Link encap:Ethernet HWaddr 2c:60:0c:2f:be:18
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:93 errors:0 dropped:0 overruns:0 frame:0
TX packets:93 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9015 (8.8 KiB) TX bytes:9015 (8.8 KiB)
wlan0 Link encap:Ethernet HWaddr ac:b5:7d:3d:18:df
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:36 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4068 (3.9 KiB) TX bytes:0 (0.0 B)
ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast master br0 state DOWN mode DEFAULT group default qlen 1000
link/ether 2c:60:0c:2f:be:18 brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master br0 state DOWN mode DORMANT group default qlen 1000
link/ether ac:b5:7d:3d:18:df brd ff:ff:ff:ff:ff:ff
4: br0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 2c:60:0c:2f:be:18 brd ff:ff:ff:ff:ff:ff
ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast master br0 state DOWN group default qlen 1000
link/ether 2c:60:0c:2f:be:18 brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master br0 state DOWN group default qlen 1000
link/ether ac:b5:7d:3d:18:df brd ff:ff:ff:ff:ff:ff
4: br0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 2c:60:0c:2f:be:18 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.100/24 brd 192.168.1.255 scope global br0
valid_lft forever preferred_lft forever
> On Mar 6, 2016, at 12:53 PM, Reco <recoverym4n@gmail.com> wrote:
>
> Hi.
>
> On Sun, 06 Mar 2016 12:33:57 -0500
> timothy.marion@marion.systems wrote:
>
>> I can only find 1 reference to using wlan0 for bridging.
>> https://wiki.debian.org/BridgeNetworkConnections This WEB Site and it
>> talks about using ebtable. Is ebtable the only way to have a bridge for
>> KVM with wlan0 ?
>
> No. ebtables come after the bridge is set up. Consider ebtables a form
> of access control. It's not mandatory to use them by any means.
>
>
>> I refuse to believe I am the only human on earth trying to do KVM on a
>> laptop with wlan0. Somebody must have done this already. I cannot be
>> the first person to want to bridge an wlan0 interface.
>
> Of course you're not the first. So...
>
>
>> wpa-psk <pre-shared-key was here>
>
> First, I suggest you to change your WPA authentication right away, as
> you've just shared your WPA key with all the world.
>
> Second,
>
>
>> auto br0
>> iface br0 inet static
> <some usual interface stanzas>
>> bridge_ports eth0
>
> This part is wrong. You want to bridge some interfaces to wlan0 via
> br0, yet you don't include wlan0 into the bridge.
> The correct way of doing this should be:
>
> bridge_ports eth0 wlan0
>
> Assuming, of course, that you'll never want to have different IPs on
> eth0 and wlan0.
>
>
> Third,
>
>> Mar 06 12:08:43 beeker networking[2344]: Configuring network
>> interfaces...can't add wlan0 to bridge br0: Operation not supported
>
> something strange goes here. You've told interfaces(5) not to add wlan0
> to br0, yet there's someone who tries to do it. Is it the manual
> invocation of "brctl addif"?
>
> "can't add wlan0 to bridge br0: Operation not supported" should be
> easily defeated with good old:
>
> iw dev wlan0 set 4addr on
>
> I.e. edit your /etc/network/interfaces like this:
>
> auto wlan0
> iface wlan0 inet manual
> wpa_ssid XXX
> wpa-psk YYY
> pre-up /sbin/iw dev wlan0 set 4addr on
>
> Reco
>
Reply to: