Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| docs:user-guide:wifi:dumbap [2018/03/03 16:37] – ↷ Links adapted because of a move operation bobafetthotmail | docs:guide-user:network:wifi:dumbap [2024/06/24 11:04] (current) – Moved bluewavenet | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| - | + | ||
| - | This document describes how to create an Access Point (AP) only. This AP allows users to connect over wireless or ethernet to the AP and an existing network. This means the AP is not routing, it provides no DHCP, and no other functions. This setup is needed when your network already has a router, access control and dhcp in place, and you'd like to use it. | + | |
| - | + | ||
| - | From a user's point of view, it works like this: | + | |
| - | * Connect to the AP (in case of wireless WPA2 encrypted, hence a password is needed) | + | |
| - | * If the user's MAC matches a MAC in the list, it gets an appropriate IP and the user gets network access (possibly not the best way to control network access...) | + | |
| - | + | ||
| - | ' | + | |
| - | + | ||
| - | //Note: This recipe results in a bridged LAN that will work fine for home and small networks. It is similar to the "Bridged AP" | + | |
| - | + | ||
| - | ===== Configuration via Web Interface LUCI ===== | + | |
| - | + | ||
| - | Of course you can achieve this with using the web interface: | + | |
| - | Once you have configured your wireless network with LUCI you can start configuring your dumb AP.\\ | + | |
| - | - Go to Network -> Interfaces and select the Lan interface.\\ | + | |
| - | - Set an IP next to your main router on the field "IPv4 address" | + | |
| - | - Then scroll down and select the checkbox " | + | |
| - | - In the top menu go to System, then Startup, disable Firewall in the list of startup scripts.\\ | + | |
| - | - Click the Save and Apply button. Hard-Restart your router if you're not able to connect anymore.\\ | + | |
| - | - Now connect to the new IP you have just specified(192.168.1.2) and check if the settings for the Lan interface are the same you set before.\\ | + | |
| - | - Now connect your main router to one of the switch ports of your " | + | |
| - | + | ||
| - | + | ||
| - | ===== Configuration via command line tools ===== | + | |
| - | + | ||
| - | The changes below assume an OpenWrt default configuration, | + | |
| - | + | ||
| - | * [[docs: | + | |
| - | * [[docs: | + | |
| - | + | ||
| - | ==== Step 1: Modify the Network ==== | + | |
| - | + | ||
| - | Edit ''/ | + | |
| - | + | ||
| - | === For switch-less devices, e.g. Alix Board, wr1043nd v2 === | + | |
| - | + | ||
| - | On switchless devices, simply bridge all ethernet interfaces together, remove the existing WAN interface - if any. | + | |
| - | + | ||
| - | < | + | |
| - | config interface lan | + | |
| - | option type ' | + | |
| - | option ifname | + | |
| - | option proto ' | + | |
| - | </ | + | |
| - | + | ||
| - | === For devices with switch and dedicated WAN, e.g. WNDR3700, WR1043ND v1, WR741ND v2.4 === | + | |
| - | + | ||
| - | On devices with a separate WAN interface, bridge the LAN VLAN together with the WAN interface, remove the existing WAN interface - if any. | + | |
| - | + | ||
| - | < | + | |
| - | config interface lan | + | |
| - | option type ' | + | |
| - | option ifname | + | |
| - | option proto ' | + | |
| - | </ | + | |
| - | + | ||
| - | Switch configuration on WR1043ND (barrier breaker): | + | |
| - | + | ||
| - | < | + | |
| - | config switch_vlan | + | |
| - | option device ' | + | |
| - | option vlan ' | + | |
| - | option ports '0 1 2 3 4 5t' | + | |
| - | + | ||
| - | #config switch_vlan | + | |
| - | # | + | |
| - | # | + | |
| - | # | + | |
| - | </ | + | |
| - | + | ||
| - | === For devices with switch only, e.g. WRT54GL === | + | |
| - | + | ||
| - | On devices where WAN and LAN are separated by switch config, reconfigure the LAN VLAN to cover all ports, | + | |
| - | remove the existing WAN interface and its related VLAN - if any. | + | |
| - | + | ||
| - | < | + | |
| - | config switch_vlan eth0_1 | + | |
| - | option vlan ' | + | |
| - | option ports '0 1 2 3 4 5t' # Might vary depending on the device | + | |
| - | + | ||
| - | config interface lan | + | |
| - | option type ' | + | |
| - | option ifname | + | |
| - | option proto ' | + | |
| - | </ | + | |
| - | + | ||
| - | ==== Step 2: Change the existing wireless network ==== | + | |
| - | + | ||
| - | Edit ''/ | + | |
| - | + | ||
| - | < | + | |
| - | config ' | + | |
| - | option type ' | + | |
| - | option channel ' | + | |
| - | option macaddr ' | + | |
| - | option htmode | + | |
| - | list ht_capab | + | |
| - | list ht_capab | + | |
| - | list ht_capab | + | |
| - | list ht_capab | + | |
| - | list ht_capab | + | |
| - | + | ||
| - | config ' | + | |
| - | option device | + | |
| - | option network ' | + | |
| - | option mode ' | + | |
| - | option ssid ' | + | |
| - | option encryption ' | + | |
| - | option key ' | + | |
| - | </ | + | |
| - | + | ||
| - | + | ||
| - | ==== Step 3: Disable DHCP Server ==== | + | |
| - | + | ||
| - | If you still need dnsmasq running for something else (e.g. TFTP server) you can do: | + | |
| - | < | + | |
| - | uci commit dhcp | + | |
| - | / | + | |
| - | + | ||
| - | ==== Step 4: Disable Firewall ==== | + | |
| - | + | ||
| - | < | + | |
| - | / | + | |
| - | + | ||
| - | ===== Apply changes ===== | + | |
| - | + | ||
| - | Reloading the network config should be enough, it should automatically restart if necessary. | + | |
| - | + | ||
| - | < | + | |
| - | + | ||
| - | ===== IPv6 ===== | + | |
| - | + | ||
| - | If you would like your AP to receive IPv6 as a host only and not for routing you have to tell dhcp6c not to request prefix deligation. | + | |
| - | If you want to still be able to use ipv6 on the Router itself change the wan6 to lan6 and @wan to @lan | + | |
| - | + | ||
| - | < | + | |
| - | option proto ' | + | |
| - | option ifname ' | + | |
| - | option reqprefix no</ | + | |
| - | + | ||
| - | ===== Multicast Forwarding ===== | + | |
| - | Multicast forwarding is necessary for DLNA and UPnP clients to work properly. For example PS3, xbox, TVs and stereos use DLNA to detect, communicate with and stream audio/video over the network. Since multicasting is turned off (multicast snooping is turned on) by default in newer OpenWrt releases, it must be activated. This would forward any multicast packets to all ports allowing your TV to find your DLNA capable NAS with movies. In large networks, this could cause some overhead which may not be desirable. | + | |
| - | + | ||
| - | Add this into / | + | |
| - | < | + | |
| - | Replace **br-lan** with your actual bridge interface, sometimes also called **br0**. | + | |
| - | + | ||
| - | This will forward all multicast packets to all ports on your bridge, making igmpproxy or udpxy proxies unnecessary. | + | |
| + | This document has now moved. Please see: | ||
| + | [[: | ||