Cannot ping devices across wireless bridge

I have Aironet 1310's connected to each other and HP Procurve 2626's on the LAN side. Two VLANs, one for data and one for voice.
I cannot ping devices in the other building, but some I can. Sometimes I can ping others I wasn't able to ping before.
Very frustrating, what's the deal?
Please assist ASAP.
Thanks,
Ed

This might be a problem with the link. Run the carrier busy test to check for the interference on this channel . Try to change the channel.

Similar Messages

Sending specific Vlan across wireless bridge

Hello All,
I would like to know how I can send a specific VLAN across a wireless bridge. Currently, we have a building across the street from our main office that's connected via a wireless bridge (no physical cabling). One of the switches in building 1 has a port in VLAN 206 (10.20.6.0/24) which connects to the wireless bridge (10.20.6.3) on that building. The wireless bridge in building 2 is 10.20.6.4 and connects to a router on the same subnet. So both bridges, the switch in building 1, and the router in building 2 are all on the same subnet. I need to send VLAN 60 across this wireless bridge so that the workstations in building 2 can go out to the Internet. As a side note, VLAN 60 is unrouted and is it's own subnet which has it's own firewall and web filter. My thought on this is that if I can get the wireless bridges to send VLAN 60 to building 2, then all I would need to do is add the workstations to that VLAN on the switch in that building and all should be well. I'm just not sure what I need to configure on the bridges and how building 2 should be configured seeing that the 2nd bridge connects to a router instead of a switch. Any tips, suggestions, and help would be great!
Thanks,
Terence

assume that i have two bridges Br-root , and Br-nonroot and i want to send traffic from multiple vlans across the wireless link, all you need to have is infrastructure-ssid on the native vlan. Then define the required subinterfaces on both radio and ethernet of root and non-root.
Example: ( vlan 1 , 2 , and three )
Root(config)#dot11 ssid test
                 #authentication open
                 #vlan 1
                 #infrastructure-ssid
                #exit
Root(config)#interface dot11radio 0
                 #ssid test
                 #station-role root bridge
                 #no shut
                #exit
Root(config)#interface dot11rdio0.1
                 #encapsulation dot1q 1 native
                #bridge-group 1
               #exit
Root(config)#interface dot11rdio0.2
                 #encapsulation dot1q 2
                #bridge-group 2
               #exit
Root(config)#interface dot11rdio0.3
                 #encapsulation dot1q 3
                #bridge-group 3
               #exit
Root(config)#interface fa0.1
                 #encapsulation dot1q 1 native
                #bridge-group 1
               #exit
Root(config)#interface fa0.2
                 #encapsulation dot1q 2
                #bridge-group 2
               #exit
Root(config)#interface fa0.3
                 #encapsulation dot1q 3
                #bridge-group 3
               #exit
for the non-root , same config but the station-role should be non-root
Enjoy

Voice vlan priority across wireless bridge network

Hello,
If you have a separate voice vlan across a wireless bridged network, how could you configure qos to put the entire voice vlan in priority over the data vlan ?
Thanks.

Hi Antonis,
Have a look at these docs. Hopefully they will help get you started;
Cisco Aironet 1300 Series Outdoor Access Point/Bridge Software Configuration Guide, 12.3(4) JA
Chapter 14 - Configuring QoS
This chapter describes how to configure quality of service (QoS) on your access point/bridge. With this feature, you can provide preferential treatment to certain traffic at the expense of others. Without QoS, the access point/bridge offers best-effort service to each packet, regardless of the packet contents or size. It sends the packets without any assurance of reliability, delay bounds, or throughput.
From this doc;
http://www.cisco.com/en/US/products/ps5861/products_configuration_guide_chapter09186a00804158a6.html
Giving Priority to Voice Traffic
This section demonstrates how you can apply a QoS policy to your wireless network's voice VLAN to give priority to wireless phone traffic.
In this example, the network administrator creates a policy named voice_policy that applies voice class of service to traffic from Spectralink phones (protocol 119 packets). The user applies the voice_policy to the incoming and outgoing radio ports and to the outgoing Ethernet port for VLAN 77.
Use the Apply Policies to Interface/VLANs drop-down menus to apply policies to the access point Ethernet and radio ports. If VLANs are configured on the access point, drop-down menus for each VLANs' virtual ports appear in this section. If VLANs are not configured on the access point, drop-down menus for each interface appear.
From this doc;
http://www.cisco.com/en/US/products/ps5861/products_configuration_guide_chapter09186a00804158a6.html#wp1047736
Hope this helps!
Rob
Please remember to rate helpful posts.......

Cisco 1941 Router-on-a-Stick w/ 11VLANs trunked to a Cisco 2960: Can Ping a device in another VLAN, that device cannot ping back

Cisco 1941 Router-on-a-Stick w/ 11VLANs trunked to a Cisco 2960: From the Switch I can Ping a device in another VLAN, that device cannot ping back. Some devices can ping devices in other VLANs and the device in the other VLAN can successfully return the Ping. Have a look at the attached diagram.
Router Config:
show run
Building configuration...
Current configuration : 7224 bytes
! Last configuration change at 09:05:48 EDT Wed Aug 6 2014
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname ROUTER
boot-start-marker
boot-end-marker
no aaa new-model
clock timezone EDT -8 0
ip cef
ip name-server 8.8.8.8
no ipv6 cef
multilink bundle-name authenticated
license udi pid CISCO1941/K9
object-group network Net_Obj_Group1
description This network group allows all 10.0.0.0 and Email Forwarder server through to the Plt PCs
205.191.0.0 255.255.0.0
10.0.0.0 255.0.0.0
object-group network Net_Obj_Group2
description This Network Group includes the Host IPs allowed through the Plant Router
host 10.194.28.23
host 10.194.28.25
host 10.194.28.26
host 10.194.28.27
host 10.194.28.28
host 10.194.28.29
host 10.194.28.37
host 10.194.28.39
host 10.194.28.40
host 10.194.28.70
host 10.194.28.130
host 10.194.28.131
host 10.194.28.132
host 10.194.28.133
host 10.194.28.134
host 10.194.28.135
host 10.194.28.136
host 10.194.28.137
host 10.194.28.138
host 10.194.28.139
host 10.194.28.140
host 10.194.28.141
interface Embedded-Service-Engine0/0
no ip address
shutdown
interface GigabitEthernet0/0
description Port Ge0/0 to IT Enterprise network Switch GE1/0/38
ip address 10.194.28.111 255.255.255.0
ip access-group 105 in
ip access-group 106 out
ip nat outside
ip virtual-reassembly in
shutdown
duplex full
speed auto
no mop enabled
interface GigabitEthernet0/1
description Port to Plant PCN-K/L24 Sw1 Port 0/24
no ip address
duplex auto
speed auto
no mop enabled
interface GigabitEthernet0/1.102
description Port to VLAN 102
encapsulation dot1Q 102
ip address 192.168.102.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.104
description Port to VLAN 104
encapsulation dot1Q 104
ip address 192.168.104.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.105
description Port to VLAN 105
encapsulation dot1Q 105
ip address 192.168.105.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.106
description Port to VLAN 106
encapsulation dot1Q 106
ip address 192.168.106.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.107
description Port to VLAN 107
encapsulation dot1Q 107
ip address 192.168.107.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.111
description Port to VLAN 111
encapsulation dot1Q 111
ip address 192.168.111.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.117
description Port to VLAN 117
encapsulation dot1Q 117
ip address 192.168.117.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.121
description Port to VLAN 121
encapsulation dot1Q 121
ip address 192.168.121.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.125
description Port to VLAN 125
encapsulation dot1Q 125
ip address 192.168.125.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.150
description Port to to VLAN 150
encapsulation dot1Q 150
ip address 192.168.150.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.999
description Port to VLAN 999
encapsulation dot1Q 999
ip address 192.168.0.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
ip forward-protocol nd
ip http server
no ip http secure-server
ip nat inside source static 192.168.102.201 10.194.28.23
ip nat inside source static 192.168.121.201 10.194.28.25
ip nat inside source static 192.168.106.251 10.194.28.26
ip nat inside source static 192.168.107.245 10.194.28.27
ip nat inside source static 192.168.102.251 10.194.28.28
ip nat inside source static 192.168.150.201 10.194.28.29
ip nat inside source static 192.168.107.179 10.194.28.37
ip nat inside source static 192.168.111.201 10.194.28.39
ip nat inside source static 192.168.105.201 10.194.28.40
ip nat inside source static 192.168.106.21 10.194.28.70
ip nat inside source static 192.168.107.146 10.194.28.130
ip nat inside source static 192.168.107.156 10.194.28.131
ip nat inside source static 192.168.107.161 10.194.28.132
ip nat inside source static 192.168.107.181 10.194.28.133
ip nat inside source static 192.168.107.191 10.194.28.134
ip nat inside source static 192.168.106.202 10.194.28.135
ip nat inside source static 192.168.106.212 10.194.28.136
ip nat inside source static 192.168.117.190 10.194.28.137
ip nat inside source static 192.168.117.100 10.194.28.138
ip nat inside source static 192.168.106.242 10.194.28.139
ip nat inside source static 192.168.125.100 10.194.28.140
ip nat inside source static 192.168.125.99 10.194.28.141
ip nat outside source static 10.194.28.23 10.194.28.23
ip nat outside source static 10.194.28.25 10.194.28.25
ip nat outside source static 10.194.28.26 10.194.28.26
ip nat outside source static 10.194.28.27 10.194.28.27
ip nat outside source static 10.194.28.28 10.194.28.28
ip nat outside source static 10.194.28.29 10.194.28.29
ip nat outside source static 10.194.28.37 10.194.28.37
ip nat outside source static 10.194.28.39 10.194.28.39
ip nat outside source static 10.194.28.40 10.194.28.40
ip nat outside source static 10.194.28.70 10.194.28.70
ip nat outside source static 10.194.28.130 10.194.28.130
ip nat outside source static 10.194.28.131 10.194.28.131
ip nat outside source static 10.194.28.132 10.194.28.132
ip nat outside source static 10.194.28.133 10.194.28.133
ip nat outside source static 10.194.28.134 10.194.28.134
ip nat outside source static 10.194.28.135 10.194.28.135
ip nat outside source static 10.194.28.136 10.194.28.136
ip nat outside source static 10.194.28.137 10.194.28.137
ip nat outside source static 10.194.28.138 10.194.28.138
ip nat outside source static 10.194.28.139 10.194.28.139
ip nat outside source static 10.194.28.140 10.194.28.140
ip nat outside source static 10.194.28.141 10.194.28.141
ip route 0.0.0.0 0.0.0.0 10.194.28.1
access-list 105 permit ip object-group Net_Obj_Group1 object-group Net_Obj_Group2
access-list 106 permit ip object-group Net_Obj_Group2 object-group Net_Obj_Group1
dialer-list 1 protocol ip permit
control-plane
banner login ^CC
Login banner for Plant Router #01^C
banner motd ^CC
MOTD Banner for Plant Router^C
line con 0
password XXXXXXXXX
logging synchronous
login
line aux 0
line 2
no activation-character
no exec
transport preferred none
transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
stopbits 1
line vty 0 4
password XXXXXXXXX
logging synchronous
login
transport input all
scheduler allocate 20000 1000
ntp server 10.199.100.92
end
Switch Config:
sh ru
Building configuration...
Current configuration : 6513 bytes
version 12.2
no service pad
service timestamps debug uptime
service timestamps log datetime localtime show-timezone
service password-encryption
hostname K24Sw01
boot-start-marker
boot-end-marker
no aaa new-model
clock timezone EDT -5
clock summer-time EDT recurring
udld aggressive
crypto pki trustpoint TP-self-signed-593746944
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-593746944
revocation-check none
rsakeypair TP-self-signed-593746944
4B58BCE9 44
quit
spanning-tree mode pvst
spanning-tree extend system-id
vlan internal allocation policy ascending
interface FastEthernet0
no ip address
interface GigabitEthernet0/1
description Trunk port for vlans 105, 111, 125 and 999 from K24Sw01 port Ge0/1 to P22Sw01 port Ge0/24
switchport trunk allowed vlan 105,111,125,999
switchport mode trunk
interface GigabitEthernet0/2
description Trunk port for vlans 150 and 999 from K24Sw01 port Ge0/2 to N25Sw01 port Ge0/26
switchport trunk allowed vlan 150,999
switchport mode trunk
interface GigabitEthernet0/3
description Trunk port for vlans 102, 104, 106, 107, 117 and 999 from K24Sw01 port Ge0/3 to K28Sw01 port Ge0/26
switchport trunk allowed vlan 102,104,106,107,117,999
switchport mode trunk
interface GigabitEthernet0/4
description Trunk port for vlans 102, 106, 107 and 999 from K24Sw01 port Ge0/4 to H23Sw01 port Ge0/26
switchport trunk allowed vlan 102,106,107,999
switchport mode trunk
interface GigabitEthernet0/5
description Trunk port for vlans 121, 125 and 999 from K24Sw01 port Ge0/5 to M21Sw01 port Ge0/24
switchport trunk allowed vlan 121,125,999
switchport mode trunk
interface GigabitEthernet0/6
description OPEN
spanning-tree portfast
interface GigabitEthernet0/7
description OPEN
spanning-tree portfast
interface GigabitEthernet0/8
description OPEN
spanning-tree portfast
interface GigabitEthernet0/9
description OPEN
spanning-tree portfast
interface GigabitEthernet0/10
description VLan 102 access port
switchport access vlan 102
spanning-tree portfast
interface GigabitEthernet0/11
description - VLan 104 access port
switchport access vlan 104
spanning-tree portfast
interface GigabitEthernet0/12
description - VLan 105 access port
switchport access vlan 105
spanning-tree portfast
interface GigabitEthernet0/13
description - VLan 106 access port
switchport access vlan 106
spanning-tree portfast
interface GigabitEthernet0/14
description - VLan 107 access port
switchport access vlan 107
spanning-tree portfast
interface GigabitEthernet0/15
description - VLan 111 access port
switchport access vlan 111
spanning-tree portfast
interface GigabitEthernet0/16
description - VLan 117 access port
switchport access vlan 117
spanning-tree portfast
interface GigabitEthernet0/17
description - VLan 121 access port
switchport access vlan 121
spanning-tree portfast
interface GigabitEthernet0/18
description - VLan 125 access port
switchport access vlan 125
spanning-tree portfast
interface GigabitEthernet0/19
description - VLan 150 access port
switchport access vlan 150
spanning-tree portfast
interface GigabitEthernet0/20
description - VLan 999 access port
switchport access vlan 999
spanning-tree portfast
interface GigabitEthernet0/21
description OPEN
spanning-tree portfast
interface GigabitEthernet0/22
description OPEN
spanning-tree portfast
interface GigabitEthernet0/23
description OPEN
spanning-tree portfast
interface GigabitEthernet0/24
description From ROUTER Gw ge0/1
switchport trunk allowed vlan 102,104-107,111,117,121,125,150,999
switchport mode trunk
interface GigabitEthernet0/25
interface GigabitEthernet0/26
interface Vlan1
no ip address
no ip route-cache
shutdown
interface Vlan102
ip address 192.168.102.253 255.255.255.0
interface Vlan104
no ip address
no ip route-cache
interface Vlan105
no ip address
no ip route-cache
interface Vlan106
no ip address
no ip route-cache
interface Vlan107
no ip address
no ip route-cache
interface Vlan111
no ip address
no ip route-cache
interface Vlan117
no ip address
no ip route-cache
interface Vlan121
no ip address
no ip route-cache
interface Vlan125
no ip address
no ip route-cache
interface Vlan150
no ip address
no ip route-cache
interface Vlan999
no ip address
no ip route-cache
ip default-gateway 192.168.102.1
ip http server
ip http secure-server
snmp-server engineID local 00000009020000019634C2C0
snmp-server community public RO
snmp-server location
snmp-server contact
banner motd ^CCC ADMIN USE ONLY! ^C
line con 0
session-timeout 10
password xxxxxx
logging synchronous
login
stopbits 1
line vty 0 4
session-timeout 10
password xxxxxxx
login
line vty 5 15
session-timeout 10
password xxxxxxxx
login
ntp server 10.199.100.92
end
K24Sw01#

HI Mark,
Here is the my config:
Create sub-interfaces, set 802.1Q trunking protocol and ip address on each sub-interface
Router(config)#interface f0/0
Router(config-if)#no shutdown
(Note: The main interface f0/0 doesn’t need an IP address but it must be turned on)
Router(config)#interface f0/0.10
Router(config-subif)#encapsulation dot1q 10
Router(config-subif)#ip address 192.168.10.1 255.255.255.0
Router(config-subif)#interface f0/0.20
Router(config-subif)#encapsulation dot11 20
Router(config-subif)#ip address 192.168.20.1 255.255.255.0
(Note: In the “encapsulation dot1q 10″ command, 10 is the VLAN ID this interface operates in)
Configure VLAN
Switch(config)#vlan 10
Switch(config-vlan)#name SALES
Switch(config-vlan)#vlan 20
Switch(config-vlan)#name TECH
Set ports to access mode & assign ports to VLAN
Switch(config)#interface range fa0/1
Switch(config-if)#no shutdown
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 15
Switch(config-if)#interface range fa0/3
Switch(config-if)#no shutdown
Switch(config-if)#switchport mode access
Switch(config-if)# switchport access vlan 20
Switch(config-if)#interface range fa0/5
Switch(config-if)#no shutdown
Switch(config-if)#switchport mode trunk
1. Please check all your port are up.
2. Check the config once again.
3. Make sure the swicth and router connection port configured as trunk and it should be up.
This config is working for me,
Regards
Dont forget to rate helpful posts.

My airport utility says it cannot find any airport wireless devices, even though I am accessing the net via my wifi. What's up with this?

My airport utility says it cannot find any airport wireless devices, even though I am accessing the net via my wifi. What's up with this? Also, I cannot connect to my Photosmart b209a printer, though a different computer - same Macbook Pro can. I tried redownloading the software, but in the setup I get a "device not reachable" message: "However to continue configuring the device in network, your Mac must have access to the device. So please make sure that your Mac has access to the Network ..." I've checked my network on the system preferences and it's properly connected. I'm on the net as I do this. Tis very frustrating, and any assistance woud be appreciated.

Airport Utility is for administration of genuine Apple Base Stations. If you have a different Brand, Airport Utility can do nothing for you.
I think they're using ethernet.
To connect a Printer via Ethernet, no password is needed.
We already tried the password for the internet and that did not work...
If a password is required to connect to the Internet, then WiFi is likley being used, and that WiFi password is the one needed for the Printer connect wirelessly as well.
What make&model Printer? Is it indeed a Wireless Printer? Most connect via USB, but that would force it to use a specific computer to assist in printing.

Wireless guest users cannot ping if ACL is applied

Hi friends,
This is the first time I am trying my hands on wireless gears. I have 2500 WLC and 1142 AP (which I converted from Standalone to LAP).
I have a layer 3 POE switch where i am using port 1 for the WLC which is a trunk port.
Port 2 is for the AP using access vlan 111
Port 3 is trunk port going to a router where i am running dhcp server for the VLANs which are as follow:
VLAN 110 -Corp Wireless (10.1.110.0/24)
VLAN 111 - AP-Mgmt (10.1.111.0/24)
VLAN 999 - Guest (10.1.101.0/24)
I wanted to block the traffic from the Guest VLAN 999 but when i apply the ACL on the Guest Interface created on the WLC, I dont see any pings going across and neither I see any hit counts on the deny statement as if the ACL is never applied.
Can some one guide me to the right direction if i am missing anything??
Thanks,
Mohit

rdvorak wrote:Put the ACL on the WLAN not on the interface.
But applying the ACL to the interface will affect all WLANs that utilize that interface!!!
Rating useful replies is more useful than saying "Thank you"

Wireless Bridge error with AIR-BR1310G-E-K9,cannot associate: No response

Hi Guys,
I have to do a wireless bridge with 2 AIR-BR1310G-E-K9. I configure 1 AP root bridge and 1 AP non-root bridge, with the same SSID.
But on the AP non-root bridge, the interface dot11 radio don't change it state to up and give this error: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associate: No Response.
I don't why it doesn't work. Even if i try a configuration which it already work on a site, it doesn't work to.
So I ask to me if there is a problem with internal antenna?
If I configure the 2 AP to access point role with 2 different ssid, I can see the 2 ssid but with a weak signal.
This AP can work without external antennas?
Thanks for your help

Hi Jerome,
The 1310 definitely can work with the internal antenna but... is the AP mounted somewhere? Some mounting options imply an external antenna as they position the internal antenna toward the wall...

Wireless host cannot ping wired host

I have a Linksys wireless router with two desktop PC's attached. When I connect my lap top (wireless) I cannot ping the desktop PC's. However, the desktop PC's can pint the wireless PC........ Can anyone help?

Actually - I thought I had - just tried it again and I can ping without the firewall running. Is there a particular port I can open, I hate to shut down the firewall. Whole reason for this project is to get my Microsoft networking to work. When it did not work, I reverted to ping testing, then found this issue.

G1K-4 pt-pt ethernet circuit - cannot ping across ...

We are running in to a problem getting traffic through an ethernet link over SONET (ONS 15454). We cannot ping. We are using the G1K-4 cards and the WS-G5484 GBIC's. We are not able to ping across. We thought that maybe it is a problem with the GBIC not being a 15454-GBIC-SX. If that's not the issue, do you have other insite?

Just seen frank.rene's post in http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Networking%20Solutions&topic=Optical%20Networking&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1ddab83e confirming they have used the WS-G5484s without problem.

Cannot ping two devices through remote access-SSH

one of our gold partner called me and advised that he cannot ping or SSh to two of the 4948 switch.however if he logged to the core switch the 6500 he can sub telnet to the 4900.but he cannot telnet directly through SSH to the 4900.i have checked the config for SSH on both device and this is configure correctly.can any one help and tell me why we cant ping or SSH to these two devices directly rather than telneting to the core device it self before telneting to the 4900s.This is very urgent

Hi
Just to clarify. This is how i understand what you have set up
You have a management vlan for the switches. The layer 3 SVI for this vlan is on your core switch.
The other switches you have all have IP addresses for management from the same management vlan.
Each switch should have a default gateway set and this default gateway should be the Layer 3 SVI on your core switch. (If you are running a pair of core switches you may well be using HSRP so your switches default gateway would be the virtual IP.
The vlan that your switch layer 3 management is in, is this the same vlan as the management vlan ie.
what vlan interface is the default gateway in ?
if you cannot ping the default gateway from the switch this sounds like you have your vlans messed up.
Could you provide configs of the 4948, the core switch and another switch that works
Jon

Trunking across a wireless bridge

Hello,
I have two 1240's and they are bridged together, is there anyway to trunk across their link? I wasn't sure if there was a way to set them up to do trunking.
Thanks,

Use this Wireless, LAN (WLAN) Configuration Examples and TechNotes. For wireless bridge trunk configuration purpose.
http://www.cisco.com/en/US/tech/tk722/tk809/tech_configuration_examples_list.html

Arp across wireless link

We have a client device connected to a BR1310 the bridge is wgb mode and auths to an AP1200 using leap, the client can not be accessed across the wireless link.
We can ping the client device from the bridge but not from any device across the wireless link. The address of the client appears in the arp table of any device that tries to ping, but there is no reply. The address and gateway are correct on the client.
Devices have been changed out and an address change was made, but this did not work.
Here are two points of interest regarding this issue. If arp caching is enabled the device will respond for a minute or two then stop responding again. If arp caching is then disabled the client will respond again for a minute or two.
We are running VTP, the radios and client are on vlan1 I do not know if this would make a difference.
Any thoughts regarding this would be appreciated.

Hello, The problem was with the IOS, I found a few versions that had these same issues.
The following information is what I forwarded to TAC.
1200-31 AP - 1310 BR
123-4.JA and 123-4.JA2 = yes
123-4.JAx and 123-7.JAx = no
123-7.JAx and 123-7.JAx = no
123-8.JEB1 and 123-8.JEA2 = yes
123-8.JEB1 and 124-3g.JA1 = yes
I tested the following versions of IOS in the following configuration. BR1310 conigured as WGB
connecting to either AP1200 or AP1231 authentication method LEAP.
The Bridge was serving only a single client connection. The result from versions that failed was
failure to pass traffic to or from the client connected to the 1310-WGB. If ARP cache is enabled on
WGB traffic will pass to and from the client for 20 to 45 seconds then fail. If ARP cache is then
disabled traffic will again pass to and from the the client for 20 to 45 seconds then fail.
The client can always be accessed from the directly connected WGB.
On the versions that worked the client is always accessible from all networks.
I have too much going on to explore the reason why some of these IOS versions did not work, but the latest release worked on both AP and Bridge. All is good.

WAP200E wireless bridge not passing data

Just setup two WAP200E's, the bridge is "Connected" as I look Status > System Performance in both WAP's. However, I cannot get to the LAN from one network to the next. Cannot even ping the WAP's from either side.
I already have two WAP200E's on this network, that have been working well for month (164 day uptime), and they are configured with a wireless bridge between them, both networks on the same LAN (same 192.168.2.x network on either side). The bridge names are different, different from the main WiFi in the building, too (if it makes a difference), and the static IPs the WAPs have don't appear to have any conflicts on the network.
This is actually three buildings, one is the main one with a Cisco SR520 for a router, and a Cisco SF 200-24P switch. So two WAP200E's go into this switch now, and I see them both fine when going into the management interface. Then each of the other buildings has one WAP200E, and a small Netgear 8 port PoE gigabit switch at each building to power the WAP.
The Netgear switches aren't managed, and I've made sure any features like STP, VLANs, etc. are turned off. And the Cisco SF 200 switch is set at auto and all the defaults mostly, particularly for the ports. I tried doing a SmartPort for this latest WAP200E and that didn't change anything, tried disabling STP for it too, and no change. The PoE port for the working WAP200E is identical in config to the PoE port for the new WAP200E, and both show forwarding, all VLANs admitted (none are enabled, no VLAN tagging, etc.).
So now I am wondering if I can have two WAP200E's into one switch? Or two bridges on the same LAN subnet? Or is there something else I am missing or should configure?

I just resolved this after reading through the community posts on people not pinging across a wireless bridge. After reading one of them it was suggested to try another channel. Seemed odd since I would see success in and packets and bytes being sent and received in the WAPs.
I ended up changing the SSID name to some a little different an changed the channel from 3 to 10 in both units. Worked instantly and has been rock solid now.
Sent from Cisco Technical Support iPhone App

Cisco C6500 CSM - Real server cannot ping its VIP.

I've been running into an issue with Cisco CSM for a number of years, but always found a way around it. Im attempting to get to the bottom of this to find out once and for all, if this is infact a limitation of the device, or a config issue/work around is possible.
Here is my situation. My CSM's are configured in bridging mode. Traffic works great, traffic bridges across vlans correctly. Everything works and have many instances of smilar configurations running in production. Every once and a while, a client requests that a "real" server (ie LWCMW-021)
cannot ping its VIP address (10.95.88.68). I am assuming this is related to the NAT Server, but not 100% sure. Clients have requested this functionality for some type of application based purpose, but Im unaware if CSM in bridging mode can provide this or not.
Any suggestions?
real LWCMW-021
address 10.95.88.59
inservice
real LWCMW-022
address 10.95.88.60
inservice
serverfarm LWCMW-80
nat server
no nat client
real name LWCMW-021 80
inservice
real name LWCMW-022 80
inservice
probe HTTP-80 (defined elsewhere)
vserver LWCMW-80
virtual 10.95.88.68 tcp WWW
vlan 120
serverfarm LWCMW-80
persistent rebalance
inservice

Sorry for giving false hope. It is only possible in ACE module. In case of CSM I believe we can only use workaround.
In case of ACE we can bind the Virtual IP to mutliple vlan. In that case we see a ARP entry like this.
10.10.10.111    e0.5f.b9.a1.72.2b vlan345   VSERVER    LOCAL     _         up
10.10.10.111    e0.5f.b9.a1.72.2b vlan346   VSERVER    LOCAL     _         up
As Virtual IP is not bound to a particular vlan in case of CSM it does not work here, but I can say for sure it is expected behavior.
The logic would be that the server tries to resolve the ARP for Virtual IP and it does not get a response.
In my case virtual ip is 10.10.10.111 before applying policy on ACE you can see that it is exhibiting the same behaviour.
Time     | Vmware_b4:72:11                       | 10.0.0.0                              | 10.10.10.4                            |
|         |                   | Broadcast         |                   | 224.0.0.1         |                   | 224.0.0.22        |
|0.000    |         Who has 10.10.10.11           |                   |                   |                   |                   |ARP: Who has 10.10.10.111? Tell 10.10.10.11
|         |(0)      ------------------> (0)      |                   |                   |                   |          |
|0.999    |         Who has 10.10.10.11           |                   |                   |                   |                   |ARP: Who has 10.10.10.111? Tell 10.10.10.11
|         |(0)      ------------------> (0)      |                   |                   |                   |                   |
|         |                   |                   |                   |                   |(0)      ------------------> (0)      |
|1.998    |         Who has 10.10.10.11           |                   |                   |                   |                   |ARP: Who has 10.10.10.111? Tell 10.10.10.11
|         |(0)      ------------------> (0)      |                   |                   |                   |                   |
|3.014    |         Who has 10.10.10.11           |                   |                   |                   |                   |ARP: Who has 10.10.10.111? Tell 10.10.10.11
|         |(0)      ------------------> (0)      |                   |                   |                   |                   |
|4.014    |         Who has 10.10.10.11           |                   |                   |                   |                   |ARP: Who has 10.10.10.111? Tell 10.10.10.11
|         |(0)      ------------------> (0)      |                   |                   |                   |                   |
Hope that helps.

Setting up a netgear n300 as wireless bridge/access point with airport extremee

I just replaced my netgear wireless router with the airport to allow our many devices on the network without knocking each other off and also increase the speed. But would like to use the netgear as a wireless bridge or access point so that I can still connect my NTFS formatted hard drive to be shared on the network. Any suggestions would be appreciated. I can not seem to find my netgear router with 192.168.1.1 as that comes up with another device. I have tried doing this with a windows laptop in another room but can not seem to make it work. I am now hooked up directly to the airport thinking i need to do it that way and still no luck. Please help.

As long as you intend to do this over ethernet it will work.. you cannot easily wireless repeat or bridge to an apple router.. you would need specific hardware to do it.
What is the exact model of netgear you have?
The setup method depends on the functionality of the router.. but lets assume it does not have a bridge or WAP mode.
You use WAN bypass.
1. Setup the Netgear with IP address in the correct IP range for the rest of the network.. it is hard to talk generalities so lets say the apple is main router and your network is now 10.0.1.x .. then set the Netgear to 10.0.1.250 (apple uses IP 2-200 by default) you can use any value you like outside the DHCP range. Up to the limit which is 254 as long as you keep track of all static IP devices. Apply this setting and power cycle the router.. and you might need to power cycle the computer as well to pick up the new IP.
2. Turn off the DHCP server in the Netgear. You may lose connection to the netgear now.. do not worry about it.. (this can be combined with one.. if you firstly turn off dhcp before you change the IP.. but whatever is possible.. at some point you will need to change around and if you forget what IP .. you will be in a mess.. so write it on a label and stick on the base of the router.. also without dhcp you will either need to reset router to factory using reset button or use static ip on the computer. )
3. Plug ethernet from LAN of the main router to LAN of the Netgear. Reboot the whole network is often necessary.
4. In your computer plugged somewhere in the network.. open browser and go to the address you set.. 10.0.1.250 in my example.
5. You can then setup the Netgear to do whatever you like.. DIsk access is fine.. wireless is fine.. it just cannot be a router.
Many many reboots if you get lost. Hit reset and start over.

Cannot ping devices across wireless bridge

Similar Messages

Maybe you are looking for