Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
playground:playground [2017/08/01 18:52 (UTC)]
slacker
playground:playground [2018/12/19 19:03 (UTC)]
chrisabela
Line 1: Line 1:
-====== ​SandPit for Wifi to eth <​del>​bridge</​del>​ routing====== +====== ​PlayGround ​======
- +
-**The reason for this HOWTO: word __bridge__ is misleading** +
- +
-For a network bridge we assume a device that transfer unmodified network packets from one network connection to the other. +
-One can create a bridge device (virtual) and add members to it. This works only for a members of a type wired - eth network cards. Network Bridge "​connects"​ members on level 3  of OSI model. That means communication on TCP/IP level.\\  +
-When you want to add a WiFi device to the bridge, you hit to a barrier: WiFi devices communicate on a level 2 of OSI model. +
-So you can find many manuals on the internet, how to circumvent this (in a form of putting WiFi card to 4addr mode). This simply DO NOT WORK!\\ +
-WiFi network card (member of bridge) authenticate and connects to AP, but TCP/IP packets do not travel over connection.\\  +
-So searching for "wifi eth bridge"​ do not return a usefull solution. The culprit is word "​bridge"​. +
- +
- +
-====== General solution ====== +
- +
-A working solution is "Proxy ARP Routing"​ +
-You simply enable IP forwarding and then for every device connected to eth side of a "​bridge"​ you have to add a routing line to routing table. This can be automated by program parprouted - Proxy ARP routing daemon.  +
- +
-====== Solution for Slackware, step-by-step ====== +
- +
- +
-This solution is for static IP addresses. See below for A use of DHCP.\\ +
-**Assuptions**:​\\ +
-We want to interconnect one WiFi and one eth network card - devices wlan0 and eth0.\\ +
-Prepare Slackware box so, to be able to comunicate over WiFi adapter (Networkmanager,​ rc.inet1 ...), eth adapter is idle.\\ +
-I had set up WPA2 AES verification with Networkmanager to get useable wpa_supplicant.conf later used with rc.inet1.\\ +
-Disable all bootable network configurations (rc.xxx files for network setup are not executable) and set rc.inet1 executable.\\ +
- +
-1. IP forwarding must be enabled at Linux kernel compilation\\ +
-2. download & compile & install [[http://​www.hazard.maks.net/​parprouted/​parprouted-0.7.tar.gz]]\\ +
-3. edit /​etc/​rc.d/​rc.inet1.conf so to enable wlan0 and eth0, set them static IP numbers ​ and set wlan0 to lowest index and connect to AP\\ +
-4. set /​etc/​rc.d/​rc.ip_forward executable:​\\ +
-       chmod +x /​etc/​rc.d/​rc.ip_forward +
-5. add a line:\\ +
-      /​usr/​local/​sbin/​parprouted wlan0 eth0  +
-        into /​etc/​rc.d/​rc.local and make this file executable +
- +
-That's all. Reboot and you have a working WiFi - eth bridge, also called WiFi extender or WiFi Internet share. +
- +
-====== DHCP enabled variant ====== +
- +
-Look below for a solution in a source link. +
- +
-====== Source ====== +
- +
-[[https://​wiki.debian.org/​BridgeNetworkConnectionsProxyArp]] +
- +
- +

In Other Languages
QR Code
QR Code playground:playground (generated for current page)