[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
playground:playground [2017/08/01 19:01 (UTC)] – slacker | playground:playground [2018/05/01 13:22 (UTC)] – atelszewski | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | + | ||
- | **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 " | + | |
- | 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" | + | |
- | + | ||
- | + | ||
- | ====== 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 " | + | |
- | + | ||
- | ====== 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, | + | |
- | 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.networkmanager or other 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:// | + | |
- | 3. edit / | + | |
- | 4. set / | + | |
- | chmod +x / | + | |
- | 5. add a line:\\ | + | |
- | / | + | |
- | into / | + | |
- | + | ||
- | That's all. Reboot and you have a working WiFi - eth bridge, also called WiFi extender or WiFi Internet share.\\ | + | |
- | + | ||
- | ***** read instructions for compilation, | + | |
- | + | ||
- | ====== DHCP enabled variant ====== | + | |
- | + | ||
- | Look below for a solution in a source link. | + | |
- | + | ||
- | ====== Source ====== | + | |
- | + | ||
- | [[https:// | + | |
- | + | ||
- | + |