User Tools

Site Tools


doc:recipes:dumbap

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
doc:recipes:dumbap [2013/03/25 14:24]
brontide
doc:recipes:dumbap [2015/04/22 17:52] (current)
valentt
Line 1: Line 1:
-====== Dumb AP ======+====== Dumb AP / Access Point Only ======
  
-This document describes how to create an Access Point that's really just that, no routing, no DHCP, no nothing. This AP allows users to connect ​to the AP over wireless or ethernet. ​I needed this setup because access control ​is already in place here through '​static DHCP' ​and I didn't want another access control mechanism.+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 networkThis 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 placeand you'd like to use it.
  
-From a user point of view it works like this:+From a user'​s ​point of viewit works like this:
   * Connect to the AP (in case of wireless WPA2 encrypted, hence a password is needed)   * Connect to the AP (in case of wireless WPA2 encrypted, hence a password is needed)
-  * If the MAC of the users network interface ​matches a MAC in the list, it gets the appropriate IP and the user has network access (possibly not the best way to control network access...)+  * 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...) 
 +  * 
 '​Static DHCP' is not covered here, all we do is creating an AP that provides WPA2 encrypted wireless access and doesn'​t interfere. '​Static DHCP' is not covered here, all we do is creating an AP that provides WPA2 encrypted wireless access and doesn'​t interfere.
  
 +===== Configuration via Web Interface LUCI =====
  
-===== Configuration =====+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"​. (If your main router has IP 192.168.1.1 set 192.168.1.2)\\ 
 +  - Then scroll down and select the checkbox "​Ignore interface: Disable DHCP for this interface."​\\ 
 +  - Click the Save and Apply button.\\ 
 +  - Now connect 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 "​new"​ dumb AP and you are done.\\ 
 + 
 + 
 +===== Configuration ​via command line tools =====
  
 The changes below assume an OpenWrt default configuration,​ the relevant files are: The changes below assume an OpenWrt default configuration,​ the relevant files are:
Line 20: Line 32:
 Edit ''/​etc/​config/​network''​ and change the ''​[[doc:​uci:​network#​interfaces|interface]]''​ section: Edit ''/​etc/​config/​network''​ and change the ''​[[doc:​uci:​network#​interfaces|interface]]''​ section:
  
-=== For switch-less devices, e.g. Alix Board ===+=== 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. On switchless devices, simply bridge all ethernet interfaces together, remove the existing WAN interface - if any.
Line 29: Line 41:
         option proto    '​dhcp' ​       # Change as appropriate''​ |         option proto    '​dhcp' ​       # Change as appropriate''​ |
  
-=== For devices with switch and dedicated WAN, e.g. WNDR3700 ===+=== 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. On devices with a separate WAN interface, bridge the LAN VLAN together with the WAN interface, remove the existing WAN interface - if any.
Line 37: Line 49:
         option ifname ​  '​**eth0.1 eth1**' ​ # Bridges vlan 1 and wan         option ifname ​  '​**eth0.1 eth1**' ​ # Bridges vlan 1 and wan
         option proto    '​dhcp' ​        # Change as appropriat''​ |         option proto    '​dhcp' ​        # Change as appropriat''​ |
 +
 +Switch configuration on WR1043ND (barrier breaker):
 +
 +| ''​config switch_vlan
 +        option device '​switch0'​
 +        option vlan '​1'​
 +        option ports '**0** 1 2 3 4 5t' ​ # 1. add 0 in here
 +
 +#config switch_vlan ​              # 2. comment out or delete the whole vlan 2 section
 +#       ​option device '​switch0'​
 +#       ​option vlan '​2'​
 +#       ​option ports '0 5t'''​ |
  
 === For devices with switch only, e.g. WRT54GL === === For devices with switch only, e.g. WRT54GL ===
Line 43: Line 67:
 remove the existing WAN interface and its related VLAN - if any. remove the existing WAN interface and its related VLAN - if any.
  
-| ''​config switch_vlan ​eth0_0 +| ''​config switch_vlan ​eth0_1 
-        option vlan     '​0'+        option vlan     '​1'
         option ports    '**0 1 2 3 4 5t**' # Might vary depending on the device         option ports    '**0 1 2 3 4 5t**' # Might vary depending on the device
  
 config interface lan config interface lan
         option type     '​bridge'​         option type     '​bridge'​
-        option ifname ​  '​**eth0.0**' ​      # Might vary depending on the device+        option ifname ​  '​**eth0.1**' ​     
         option proto    '​dhcp' ​        # Change as appropriate''​ |         option proto    '​dhcp' ​        # Change as appropriate''​ |
  
Line 102: Line 126:
  option ifname '​@wan'​  option ifname '​@wan'​
  option reqprefix no</​code>​  option reqprefix no</​code>​
 +
 +===== 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 /​etc/​rc.local
 +<​code>​echo "​0"​ > /​sys/​devices/​virtual/​net/​br-lan/​bridge/​multicast_snooping</​code>​
 +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. ​
  
  
doc/recipes/dumbap.1364217857.txt.bz2 · Last modified: 2013/03/25 14:24 by brontide