I do the opposite of what most people think when connecting Ethernet and a wireless interface. I have one box without a wireless card, and I want to provide Internet access through the box next to it, which has both a wireless card and an Ethernet card. The wireless card accesses the Internet through a wireless router that serves as a dhcp server on the private network 192.168.0. *. The router's dhcp server is configured to never assign any static IP address below.
I have configured the bridge in / etc / network / interfaces and no problems arise when I raise br0. The problem is that after raising the bridge, no computer can access the Internet. Here are the details of my configuration:
/ etc / network / interfaces:
allow-hotplug eth0
iface eth0 inet static
address 192.168.0.15
netmask 255.255.255.0
broadcast 192.168.0.255
auto wlan0
iface wlan0 inet dhcp
pre-up iwconfig wlan0 channel 4 key <my-key> essid <my-essid> mode Managed
iface br0 inet static
gateway 192.168.0.1
address 192.168.0.10
netmask 255.255.0.0
broadcast 192.168.0.255
network 192.168.0.0
bridge_ports wlan0 eth0
pre-up iwconfig wlan0 channel 4 key <my-key> essid <my-essid> mode Managed
A wireless connection works great when used separately, and routing looks like this:
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 wlan0
default localhost 0.0.0.0 UG 0 0 0 wlan0
When I raise br0, the routing table is identical with the exception that Iface is br0 for each record, and it takes a significant amount of time to return a record by default.
Another difference I noticed is when I list the interfaces using ifconfig, wlan0 no longer shows the IP address after calling br0.
(192.168.0.1), -:
"Destination Host Unreachable" br0 IP: 192.168.0.10.
?
,
Jivan Amara