11-25-2011 04:37 AM - edited 03-07-2019 03:36 AM
We have dlink dir320 router and cisco 877W.
The goal is to make a 877W to work as a wireless client of dlink dir320 and brigde the LAN&WLAN so than the LAN clients of 877W could take DHCP from Dlink 320 directly.
Here's the config of 877w:
!
bridge irb
!
dot11 ssid DLINK_SSID
authentication open
authentication key-management wpa
infrastructure-ssid
wpa-psk ascii 7 WPAKEY
!
interface Dot11Radio0
no ip address
!
encryption mode ciphers aes-ccm tkip
!
ssid DLINK_SSID
!
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0 54.0
station-role non-root
!
bridge-group 1
bridge-group 1 spanning-disabled
!
interface Vlan 1
no ip address
bridge-group 1
bridge-group 1 spanning-disabled
!
interface BVI 1
no ip address
!
interface FastEthernet 3
spanning-tree portfast
!
bridge 1 protocol ieee
bridge 1 route ip
In this configuration, we have dot11radio0 line protocol UP, and there's an assiciation with DLINK router at show dot11 associations. We can also see the MAC address of 877w's dot11radio0 interface in DLINK wireless clients page (but without IP address, of course).
When we try to request DHCP from the host on the 877w's FastEthernet 3 interface we get no response, but more likely our requests are being dropped somewhere, because the wireshark shows normal network activity within DLINK's network (both wired&wireless) : ARP requests, etc. If we manually enter static IP&Gateway on this host, no traffic (even icmp) goes anywhere, but still receiving L2 traffic from DLI|NK.
sh spanning-tree show all the bridge 1 ports as forwarding. What are we missing?
P.S.
As a workaround, we get the IP address on the dot11radio0 via DHCP from the DLINK, create the different network within FastEthernet 3 Vlan and configure NAT. That is an accepted, but not desirable solution.
Thanks in advance.
Solved! Go to Solution.
11-28-2011 12:06 AM
The method you describe in the workaround is called universal client for the 871. See
https://supportforums.cisco.com/thread/329549
This link has the following:
Layer-3 routing is supported over the radio interface. However, there is no support for L2-bridging. The user cannot configure a dot11radio interface with a bridge-group when in universal client mode.
11-28-2011 12:06 AM
The method you describe in the workaround is called universal client for the 871. See
https://supportforums.cisco.com/thread/329549
This link has the following:
Layer-3 routing is supported over the radio interface. However, there is no support for L2-bridging. The user cannot configure a dot11radio interface with a bridge-group when in universal client mode.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide