[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 12:53 (UTC)] – slacker | playground:playground [2021/07/31 23:23 (UTC)] – carriunix | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | + | ||
- | **The reason for this HOWTO: word bridge is misleadig** | + | |
- | + | ||
- | 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** | + | |
- | + | ||
- | - 1. IP forwarding must be enabled at Linux kernel compilation\\ | + | |
- | - 2. | + |