Bridge wlan0 to eth0: Difference between revisions
No edit summary |
m (added Networking category, minor formatting) |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{TOC right}} | {{TOC right}} | ||
= Introduction = | |||
== Introduction == | |||
This wiki describes methods to bridge a wired and wireless interface to enable network communication between hosts reachable via either interface. This allows one or more wired hosts to share the wireless interface on the bridge host. | This wiki describes methods to bridge a wired and wireless interface to enable network communication between hosts reachable via either interface. This allows one or more wired hosts to share the wireless interface on the bridge host. | ||
| Line 7: | Line 9: | ||
I am only going to document the proxy ARP method as that's what I'm currently using. Please feel free to add additional methods and remove this section of the introduction. | I am only going to document the proxy ARP method as that's what I'm currently using. Please feel free to add additional methods and remove this section of the introduction. | ||
= Method 1: Proxy ARP = | == Method 1: Proxy ARP == | ||
These steps result in a working solution where hosts on the wired side and hosts on the wireless side are all in the same ip network. There are no frills added, such as dhcp or automatic route entries for the wired hosts. Each wired host needs to have a manually configured IP address and an entry manually added to the bridge host's routing table. | These steps result in a working solution where hosts on the wired side and hosts on the wireless side are all in the same ip network. There are no frills added, such as dhcp or automatic route entries for the wired hosts. Each wired host needs to have a manually configured IP address and an entry manually added to the bridge host's routing table. | ||
Note: For your wired hosts, use IP addresses in the same IP range as the rest of your network but outside of the scope used by a local DHCP server, if applicable. You may need to reduce your DHCP scope to free up IP addresses for | Note: For your wired hosts, use IP addresses in the same IP range as the rest of your network but outside of the scope used by a local DHCP server, if applicable. You may need to reduce your DHCP scope to free up IP addresses for this purpose. | ||
Configure the network interfaces on your bridge host: | Configure the network interfaces on your bridge host: | ||
| Line 31: | Line 34: | ||
Notice that the wireless interface (wlan0) uses dhcp from the home network as usual and that an IP address is not used at all on the wired interface (eth0). | Notice that the wireless interface (wlan0) uses dhcp from the home network as usual and that an IP address is not used at all on the wired interface (eth0). | ||
Enable and create a local start-up script to add route entries | Enable and create a local start-up script to add route entries at boot: | ||
{{Cmd| # rc-update add local default | {{Cmd| # rc-update add local default | ||
| Line 38: | Line 41: | ||
}} | }} | ||
Add route statements for each | Add route statements for each host on the wired side of the bridge: | ||
{{Cat|/etc/local.d/RouteAdd.start| | {{Cat|/etc/local.d/RouteAdd.start| | ||
| Line 55: | Line 58: | ||
}} | }} | ||
{{Cmd|# reboot | {{Cmd|# reboot}} | ||
}} | |||
[[Category:Networking]] | |||
Latest revision as of 14:19, 18 April 2023
Introduction
This wiki describes methods to bridge a wired and wireless interface to enable network communication between hosts reachable via either interface. This allows one or more wired hosts to share the wireless interface on the bridge host.
In my use case, I have a desk with a wired switch with multiple hosts connected. All wired devices on this switch can access my home wifi network via the bridge host's wireless interface.
I am only going to document the proxy ARP method as that's what I'm currently using. Please feel free to add additional methods and remove this section of the introduction.
Method 1: Proxy ARP
These steps result in a working solution where hosts on the wired side and hosts on the wireless side are all in the same ip network. There are no frills added, such as dhcp or automatic route entries for the wired hosts. Each wired host needs to have a manually configured IP address and an entry manually added to the bridge host's routing table.
Note: For your wired hosts, use IP addresses in the same IP range as the rest of your network but outside of the scope used by a local DHCP server, if applicable. You may need to reduce your DHCP scope to free up IP addresses for this purpose.
Configure the network interfaces on your bridge host:
Contents of /etc/network/interfaces
Notice that the wireless interface (wlan0) uses dhcp from the home network as usual and that an IP address is not used at all on the wired interface (eth0).
Enable and create a local start-up script to add route entries at boot:
# rc-update add local default # touch /etc/local.d/RouteAdd.start # chmod +x /etc/local.d/RouteAdd.start
Add route statements for each host on the wired side of the bridge:
Contents of /etc/local.d/RouteAdd.start
Enable proxy arp:
Contents of /etc/sysctl.d/local.conf
# reboot