Ethernet Bridging - Client DHCP issue

Good Afternoon,
We are having a strange issue taht i am sure others have run into before.
Currently we have a WLC 5508 with 2 1552 Outdoor Mesh APs running code 7.4.100.0.
We one configured as RAP and one as MAP. This is essentially setup just as a backhaul (trunk link). We ahve the RAP setup as Normal and the MAP setup for Trunk. We have configured to pass all VLANs we need (pruning). The mesh link works as expected the only issue is when we try to connect a client to a access port (VLAN 18) on a switch the MAP side (ethernet bridged). We are unable to get a IP address assigned.
However. We can statically configure an address in that network and Unicast traffic works just fine. It appears the broadcast traffic is not making it across the Mesh link.
Thoughts?

With mesh, you do not need to enable ethernet bridging at all. All the traffic should tunnel back to the WLC as if the mesh ap was a local mode ap. Make sure that if you are using AP Groups that the WLAN to vlan mappings are correct. The other thing is that you should be on v7.4.121.0 and also make sure you have uploaded the latest FUS 1.9.0.0 onto the WLC for stability. I have mesh networks on both v7.4.121.0 and v7.6.120.0, working just fine.
Scott

Similar Messages

Client DHCP issues with 4400 WLC

Authentication to ACS working okay.
Clients are unable to obtain an IP from DHCP.
DHCP server is configured on a dynamic interface but is on a different subnet located in a branch office. DHCP scope is running on a 4500 switch in the branch.
Is it preferable to have DHCP running on the internal WLC or a DHCP server close to the WLC rather than at the remote location?
TIA

Usually you don't want to have a dhcp server on a remote site, but it also should work as long as wired users are able to obtain an IP from the remote dhcp server. Preferred, like I said is to have a local dhcp, but if that doesn't work for you, then configuring the wlc to bbe a dhcp isn't a bad think either. Some like to have more control over the dhcp.

AEBS and AExpress N ethernet bridge disconnects when I sleep MBP??

Hi all this is my first post but im a long time mac user having grown up in a mac house.
anyways im an it guy by profession and ive been working at this issue to no avail so I figured I might come on there and see if any of you have experienced this issue
the issue I get is that when I close/sleep my MBP it disconnects the Airport Express ethernet bridge clients
NETWORK Info
I run a small business from my home thus I have FiOS (yay 20/20) with a block of 13 static ips that i distribute via DHCP and MAC reservation to allow remote access to my network as well as keep things consistent.
I currently run cat6 from my FiOS ONT to my Airport Extreme Base Station, which i use on a strict N only in 5ghz range as my area is flooded with b/g networks but no n networks (yay again).
I recently acquired an N Airport Express to provide a wireless to ethernet bridge thus extending my network to my entertainment center (ps3 xbox etc)
(extra info: im using n here because i found that b/g limits my internet connection speeds to 7-9 mbps where as my connection is capable of 20. On my n speed network I can get my full bandwidth wirelessly, yes I know there is obviously some bandwidth and throughput loss by going wireless but not as much as a b/g network was giving me)
NETWORK SETTINGS
On my n network I distribute a range of IP addresses from my static block. I have tried a few different dhcp lease times which definitely improved my initial problem which seemed that it would log me out when the key rotated every 20 min. Currently ive bumped that up to 1 day (i know not as secure id like to set it back to 20min but it seems that when it rotates that it logs me out) and haven't had that specific issue revolving around key rotation again. ive tried the WDS, Extend a network and join a network options with no real difference in behavior when I shut my laptop and for example my GF is playing rock-band online she gets disconnected also worth noting that it seems there is an intermittent DNS issue on the express ie cant find time server even though at that time ethernet clients are able to connect and get dns response
Below is my log from my express base station when the disconnect occurs
Feb 05 06:23:29 Severity:5 Clock synchronized to network time server time.apple.com (adjusted +0 seconds).
Feb 05 07:23:29 Severity:5 Clock synchronized to network time server time.apple.com (adjusted +0 seconds).
Feb 05 08:23:29 Severity:5 Clock synchronized to network time server time.apple.com (adjusted +0 seconds).
Feb 05 09:23:30 Severity:5 Clock synchronized to network time server time.apple.com (adjusted -1 seconds).
Feb 05 09:28:36 Severity:5 Joined BSS 00:1e:52:78:bc:48
Feb 05 09:28:36 Severity:5 Installed unicast CCMP key for authenticator ******:bc:48
Feb 05 10:24:05 Severity:3 No Address for NTP server time.apple.com.
Feb 05 11:24:35 Severity:3 No Address for NTP server time.apple.com.
Feb 05 12:25:05 Severity:3 No Address for NTP server time.apple.com.
Feb 05 13:25:35 Severity:3 No Address for NTP server time.apple.com.
Feb 05 14:26:05 Severity:3 No Address for NTP server time.apple.com.
Feb 05 15:26:35 Severity:3 No Address for NTP server time.apple.com.
Feb 05 15:44:34 Severity:5 Disconnected from network.
Feb 05 15:44:42 Severity:5 Joined BSS **********bc:48
Feb 05 15:44:42 Severity:5 Installed unicast CCMP key for authenticator ********bc:48
Feb 05 15:53:26 Severity:5 Connection accepted from [************:6baf%bridge0]:51073.
Feb 05 15:53:28 Severity:5 Connection accepted from [************:6baf%bridge0]:51075.
Feb 05 15:53:28 Severity:5 Connection accepted from [************6baf%bridge0]:51076.
Feb 05 16:09:13 Severity:5 Clock synchronized to network time server time.nist.gov (adjusted +0 seconds).
and my log from my AEBS
Feb 05 09:09:08 Severity:5 Clock synchronized to network time server time.nist.gov (adjusted +0 seconds).
Feb 05 09:28:37 Severity:5 Associated with station ******:91:07
Feb 05 09:28:37 Severity:5 Installed unicast CCMP key for supplicant **********:91:07
Feb 05 10:09:09 Severity:5 Clock synchronized to network time server time.nist.gov (adjusted +0 seconds).
Feb 05 11:09:10 Severity:5 Clock synchronized to network time server time.nist.gov (adjusted -1 seconds).
Feb 05 12:09:10 Severity:5 Clock synchronized to network time server time.nist.gov (adjusted +0 seconds).
Feb 05 13:09:11 Severity:5 Clock synchronized to network time server time.nist.gov (adjusted -1 seconds).
Feb 05 14:09:11 Severity:5 Clock synchronized to network time server time.nist.gov (adjusted +0 seconds).
Feb 05 14:15:28 Severity:5 Associated with station ******:6b:af
Feb 05 14:15:28 Severity:5 Installed unicast CCMP key for supplicant ******6b:af
Feb 05 15:09:13 Severity:5 Clock synchronized to network time server time.nist.gov (adjusted -2 seconds).
Feb 05 15:44:32 Severity:5 Disassociated with station ******6b:af
Feb 05 15:44:35 Severity:5 Rotated CCMP group key.
Feb 05 15:44:35 Severity:5 Deauthenticating with station ******cc:e5 (reserved 2).
Feb 05 15:44:35 Severity:5 Disassociated with station ******:cc:e5
Feb 05 15:44:35 Severity:5 Disassociated with station ******91:07
Feb 05 15:44:36 Severity:5 Rotated CCMP group key.
Feb 05 15:44:43 Severity:5 Associated with station ******:cc:e5
Feb 05 15:44:43 Severity:5 Installed unicast CCMP key for supplicant ******cc:e5
Feb 05 15:44:44 Severity:5 Associated with station ******91:07
Feb 05 15:44:44 Severity:5 Installed unicast CCMP key for supplicant ******91:07
Feb 05 15:53:01 Severity:5 Associated with station ******6b:af
Feb 05 15:53:01 Severity:5 Installed unicast CCMP key for supplicant ******:6b:af
Feb 05 15:53:15 Severity:5 Connection accepted from [******:6baf%bridge0]:51048.
Feb 05 15:53:16 Severity:5 Connection accepted from [******6baf%bridge0]:51049.
Feb 05 15:53:16 Severity:5 Connection accepted from [******:6baf%bridge0]:51050.
Feb 05 16:09:13 Severity:5 Clock synchronized to network time server time.nist.gov (adjusted +0 seconds).
THANKS FOR YOUR INPUT AND SUGGESTIONS

i decided to also add my log from the mbp (dont think it matters but its an early 2008 model mbp)
as you can see i put my computer to sleep at the exact same time that the airport express lost connection iI
2/5/09 3:44:31 PM kernel hibernate image path: /var/vm/sleepimage
2/5/09 3:44:31 PM kernel sizeof(IOHibernateImageHeader) == 512
2/5/09 3:44:31 PM kernel Opened file /var/vm/sleepimage, size 4294967296, partition base 0xc805000, maxio 400000
2/5/09 3:44:31 PM kernel hibernate image major 14, minor 2, blocksize 512, pollers 4
2/5/09 3:44:31 PM kernel hibernateallocpages flags 00000000, gobbling 0 pages
2/5/09 3:44:32 PM kernel /drv/ MacModule.cpp:261 powerStateWillChangeTo: flags=4 stateNumber=2
2/5/09 3:44:32 PM configd[36] AppleTalk shutdown
2/5/09 3:52:59 PM kernel /drv/ MacModule.cpp:266 powerStateWillChangeTo: found flag=kIOPMSleepCapability (4)
2/5/09 3:44:32 PM configd[36] AppleTalk shutdown complete
2/5/09 3:52:59 PM kernel AirPort: Link Down on en1
2/5/09 3:52:59 PM aosnotifyd[278] Stream:streamCallback - an error occurred on CFReadStream: Operation could not be completed. Socket is not connected
2/5/09 3:52:59 PM kernel /drv/ MacModule.cpp:261 powerStateDidChangeTo: flags=4 stateNumber=2
2/5/09 3:52:59 PM kernel /drv/ MacModule.cpp:266 powerStateDidChangeTo: found flag=kIOPMSleepCapability (4)
2/5/09 3:52:58 PM configd[36] setting hostname to "Comp.local"
2/5/09 3:44:34 PM kernel System SafeSleep
2/5/09 3:52:59 PM kernel hibernatepage_listsetall start
2/5/09 3:52:59 PM kernel hibernatepage_listsetall time: 180 ms
2/5/09 3:52:59 PM kernel pages 635428, wire 220619, act 232958, inact 31, zf 59, throt 1114, could discard act 55989 inact 111080 purgeable 13578
2/5/09 3:52:59 PM kernel hibernatepage_listsetall found pageCount 454781
2/5/09 3:52:59 PM kernel IOHibernatePollerOpen, mlget_interruptsenabled 0
2/5/09 3:52:59 PM kernel IOHibernatePollerOpen(0)
2/5/09 3:52:59 PM kernel writing 454552 pages
2/5/09 3:52:59 PM kernel image1Size 636423168
2/5/09 3:52:59 PM kernel all time: 21548 ms, comp time: 2872 ms, deco time: 0 ms,
2/5/09 3:52:59 PM kernel image 1120299008, uncompressed 1861844992 (454552), compressed 1116586684 (59%), sum1 5d386928, sum2 eeca85bd
2/5/09 3:52:59 PM kernel hibernatewriteimage done(0)
2/5/09 3:52:59 PM kernel sleep
2/5/09 3:52:59 PM kernel Wake reason = EC LID0
2/5/09 3:52:59 PM kernel System Wake

Mesh Ethernet Bridging with VLAN Tagging Issue

Hi all.
I'm a little stuck with a 4400 7.0.220.0 + RAP 1550 + MAP 1260 Ethernet bridging issue. I'm using the VLAN tagging functionality and I'm finding that periodically a VLAN that I've tagged on the MAP will deregister from the backhaul and stop passing traffic. If I go into the Mesh tab on the MAP, select the wired interface, remove the VLAN from the list of tagged VLAN IDs and then add it right back to the list, its starts passing traffic again.
Has anyone else seen this? I can't find any relevant bugs.
Justin

Hi Saravanan,
It is one RAP and three MAPs. After a TAC call and 30 hours of monitoring, my VLANs have remained registered. I think the issue was mismatched VLANs to bridge groups an it looks like the mesh bridge may be stable for now. Here is what I was seeing on the RAP and MAPs when the VLANs were deregistering unexpectedly. Notice how VLANs 2 and 10 are mapped to opposite bridge groups on the RAP and MAP:
After I removed all the VLAN IDs from the Trunk configuration on the MAPs (through each AP's Mesh tab -- Ethernet Bridging config) and then rebuilt the VLAN IDs, I ran the same commands and now see this:
My very unscientific theory here is that the mismatching was causing consistency checks to fail, so the RAP was just tearing down the registrations after getting bogus or non- responses from the MAPs during the periodic VLAN registration maintenance checks (debug mesh ethernet registration).
If I have continued issues, I'll post back with updates.
Thanks for the response!
Justin

Outdoor Mesh AP Ethernet Bridging Problem

Hi All,
I've setup 6 X 1522 MESH APs.
Setup:
There is 1 RAP and the rest are MAPs. All APs have already successfully registered with the WLC (4402-50), with the RAP being the hub and all other MAPs a single hop away. APs are all in VLAN 10 (same vlan as the AP manager) and the WLC management interface is in VLAN 9. Bth VLANs are routable to each other. All APs are configured with Ethernet Bridging checked and all are configured with the same bridge group name. The switchports (Fa0/8) for each switch connected to each AP is configured to be trunk mode with native Vlan of 10. All switches are also configure with other VLANs such as VL20 - 30 besides the mentioned VL9 & 10.
Problem:We tried to bridge VLAN 20 across the wireless bridge by plugging a notebook(A) to a switchport (Fa0/1: sw mode access & sw ac vl 20) belonging to a switch connected to MAP1; and another notebook(B) also plugged in to a VL 20 access port whose switch is connected to the RAP. From notebook A, we were able to ping all relevant IP addresses (notebook B, WLC management IP, VL 20, VL30 ip addresses of equipment somewhere else in the network behind the RAP). This means the wireless bridge is already working as VL20 is already bridge across th MAP and RAP. However, when we tried to do anything else, such as ftp, IPERF, some other TCP dependent application, it doesn;t work. we setup a FTP server on notebook B and used notebook A to retrieve a file. ftp client in notebook A was able to perform login, list directory. But when a file is being pulled, it stopped after it downloaded exactly 1024byte of information. FTP will timeout after a while with only 1024byte transferred. However, using tftp, we were able to complete transferring the entire file. It seems that the wireless bridge or the switches which the hosts were connected to allows tftp (UDP) to go through but restricted big packets/blocks of TCP information to go through (since only file transfer or any other application involving larger data exchange fails, but logging in and telneting applications still works).
Very puzzled as we had previously configured wireless bridging before on the same model of APs and it was working.
Can any experts here offer any advise to our problem?
BTW, the WLC is on the latest version of the MESH firmware as of today. All APs gets their IP address dynamically from a router in VLAN 10 configured with the correct DHCP pool and option 43 parameters. DHCP should be working well as our APs are all registered with the correct range of IP addresses and all APs are pingable from anywhere in the network. LinkSNR between the RAP and the MAPs are very good ranging from 30-38 hence it should not be an issue of poor signal or interference or noise.
Thank you
Alvin

I've personally not configured the MESH gear to form a bridge, so I can't provide any "real world" expertise. Here is short document on how to set it up, so maybe something within it will catch your eye:
http://www.cisco.com/en/US/products/ps6366/products_configuration_example09186a00808e9c1b.shtml
Good Luck!

Setting up an older AE to extend an AEn network as a Ethernet bridge

I know that this question has been asked a million times, and I've followed everyone's instructions and no matter what I do, AEn is still amber and no network gets to the AE.
Here is current setup:
Airport Utility: 5.5.1
AEn:
Firmware version: 7.4.2
Airport ID: XX:XX:XX:XX:XX:66
2.4 ghz ID: XX:XX:XX:XX:XX:65
Wireless mode: Participate in a WDS network
Wireless network name: Pastel
Allow this network to be extended: unchecked
Radio mode: 802.11a - 802.11b/g
Radio channel selection: manual 149/4
Wireless security WPA/WPA2 personal
WDS mode: WDS main
Allow wireless clients: Checked
WDS remotes: XX:XX:XX:XX:XX:B8 (the x's are just added for you guys)
DHCP and NAT enabled
AE to be used as Ethernet bridge (I originally wanted it to extend wireless too, but I can do without that, and disabling wireless clients makes debugging easier):
Firmware version: 5.7
Airport ID: XX:XX:XX:XX:XX:B8
Wireless mode: Participate in a WDS network
Wireless network name: Pastel
Radio mode: 802.11b/g
Radio channel : 4
Wireless security WPA/WPA2 personal
WDS mode: WDS remote
Allow wireless clients: unchecked
WDS main: I've tested both XX:XX:XX:XX:XX:66
and XX:XX:XX:XX:XX:65
IP address set in Bridge Mode
Anything unmentioned is left as default.
Airports are next to each other, like right beside each other, but the AEn reports WDS error that no other airports have been detected. I have tried temporarily attaching the two together with an ethernet to no avail. I have internet no problem coming from the AEn, but plugging with Ethernet into the AE, while the utility shows green, I do not properly get assigned a DHCP address, and have no network connectivity.
I hope I've posted enough information, please let me know if you need more and anything I can do to help the situation.

Thanks for the really prompt input Bob, really a spectacular forum.
I've actually already followed the guide to no avail. That said, I have 'resolved' my issue. Unfortunately it won't help anyone else who has this issue because I simply swapped the two devices and everything worked. (Its not an issue of typo as the settings were literally copied and pasted out of notepad). Which is too bad because I wanted to have the Ethernet ports at my hub, but thats life. Mysterious or what? If that means anything to you guys, I'll give and real resolutions a whirl to see what happens.
This is actually the first time I've had difficulty with WDS, and my past experiences were with $30 SMC routers, so I am a bit surprised given the good experience I've had with airports otherwise.

Can't get ethernet bridge to connect to network

Hi
I am trying to connect my old iMac G3 (10.2) to my airport express network with an Aeropad Mini (an ethernet bridge powered by USB hub on my mac - made by Macsense).
The network is seen successfully by an iMac G5, an Intel Macbook and a PC. The connection occasionally works but more often than not it does not see my airport express - instead it connects to a self-assigned IP. Sometimes it connects then drops off halfway through. Other times it just will not connect at all.
There are no drivers and you set it up via your browser. I can connect to the status and set-up page (192.168.1.50), after entering all the Aeropad info manually, and most times it can see my Airport Express (via the Site Survey on the set-up pages). but sometimes it does not even get that far. I reset the aeropad and restart the mac many times, and sometimes it works but mostly it doesn't.
I'm using channel 11 and it's WAP-encrypted.
Things I've tried:
updating the firmware from the macsense website
checking it's on client mode
manually entering the DNS address of my router - 10.0.1.1.
Trashing the internetconfig preferences from the library
making sure that ethernet is at the top of my network port configurations
Plugging it into a powered USB hub
Trying it on my MacBook (running Leopard).
Still can't connect - just a self-assigned IP - even on on the new macbook.
Any help would be appreciated as I really can't get this to work and it's beginning to take over my life!. I thought it was working after I entered the DNS address but it just went down again the next day.
Thanks.
Message was edited by: Joanna Leapman

This is probably repeating the steps which you have taken already, but I thought I'd put them in one place just in case.
Problem:
If you're able to see other wireless networks but not your own. (And it works with AppleTV version 1.x)
It can be any of the following:
1. No wireless signal/out of range (check your multicast setting and put this as low as possible, check the range with other wireless devices/moving your appletv closer)
2. The wireless SSID is set to invisible/private (use "Other" on AppleTV and enter the SSID manually.)
3. The AppleTV doesn't support the channel used. (Tune the wireless to use a lower channel such as those under 10.)
4. The AppleTV is not supporting the security of your encryption.
Troubleshooting:
1. First try setting up a basic wireless network with no security, no frills such as a high multicast rate or high channel number and as a basic wireless b or g network. Position the AppleTV next to the basestation and then attempt to make the appletv connect to it. (Do not use an AdHoc network with your mac, as the AppleTV doesn't see these.) At this stage you're just trying to see if the AppleTV is even able to connect to your hardware. If this doesn't work there is possibly a larger problem at hand.
2. If this works, then move the devices to their desired locations. (This checks that it's not a range/interference issue.)
3. If this is still working, then the problem lays in a configuration setting. Firstly enable a security protocol, avoid WEP. Keep adding settings, keeping changes from the default to a minimum.
If you can't get past step 1, then it could be an issue with your wifi base station. Try getting the AppleTV to connect to a different wireless basestation (perhaps borrow one from a friend or a neighbour's unsecured network.)

Request: Provide Ethernet Bridging to NON-WDS Networks!!!

I realize that the topic I am adding here has been discussed quite a few times and also that many comments were made on the issue at least as often. What I am trying to understand is this:
Why did the initial design of the Airport Express turn off or not provide Ethernet bridging in client mode?
My brother gave me the AE as a gift over a year ago and just recently I got a wireless router and dsl modem (in one unit) and was able to install the AE for the following usage (which I consider reasonable and 100% compliant to what was written on the box):
- stream airtunes to the stereo in the living room (ok)
- get my playstation2 online using the ethernet port (no way)
Now that I have gone through hours of internet searching regarding WDS, I see that Apple has not intended the AE for this usage as it is only possible using Airport units. Don't get me wrong, but I am not going to go out and buy another base station in the form of any other Airport unit (especially after reading the other threads regarding their reliability!) just to get the funtionality of an Ethernet bridge.
Bridging requires little to no additional intelligence in the unit other than mirroring the network traffic it is hearing on the wireless side. And that is obviously available since the WDS configuration offers that. I am aware of technical details (I built up the internals of a wireless ethernet bridge in a Hiperlan/2 network over three years ago at a research facility) and want to know why this is not done by default?? The AE is heating my living room as it is and I consider this a reasonable request for a new firmware edition - those who don't use ethernet bridging wouldn't notice a difference and the AE would finally fulfil what is promised on the box.
Thanks for your time and perhaps persuasion in handling this issue - I hope my AE lasts long enough to experience this firmware edition if it ever gets out there.
iMac (2000) Mac OS X (10.2.x) Also a PC from 2004 (XP)

This is a user-to-user support forum.
To provide feedback to Apple use the forms on this page.
http://www.apple.com/feedback/

Wierd DHCP Issue

Hello All,
I facing a very wierd DHCP issue and would like to know your thoughts on it.
I have my wired clients on vlan 1 and wireless cleints(eap-peap) on VLAN 2.
We are facing an issue where multiple wired clients who were on access port vlan 1 are receiving IP address from wireless subnet(vlan2) -their DHCP server was the WLC virtual gateway IP address(1.1.1.1). This is causing an outage to few wired clients.
The WLC trunk does not have vlan 1 allowed on its ports and all APs are in local mode and all on access vlan.
I'm not entirely sure whats causing this, but only way I think this is possible is that 'A Client' laptop has his network connections bridged - his wired nic on VLAN 1 and wireless NIC on vlan 2, acting like a WGB, which is causing new wired clients(vlan1) DHCP broadcast request forwared through the bidge mode laptop to AP--> WLC. Do you think this is possible??
Havent been able to identify which client is causing this issue yet.
Has anyone faced a similar issue and anyway to block this through WLC/ACS policy?
Thanks
Jino

Hi,
Might we consider to make use of network monitor to take a look at the traffics for the 1.1.1.1 address?
How to use Network Monitor to capture network traffic
Download link here:
Microsoft Network Monitor 3.4
Best regards
Michael Shao
TechNet Community Support

Want to use linksys wrt300n as a ethernet bridge while the router is a time capsule.

The time capsule is connect to my modem and my wrt300 is downstairs. What I want to do I use my time capsule a my router and the wrt300 as my ethernet bridge. How do I set my wrt recieve the single from my time capsule. The wrt300. Is running dd-wrt firmware. The reason I want to do this is that I have a slingbox and it needs to be connected by Ethernet. By using the wrt as a Ethernet bridge it should work. I just need to know how.

All sounds good.. tend to use the older dd-wrt firmware to do this.. 2.4 linux kernel is far more successful than later 2.6 versions of dd-wrt.
You must manually setup wireless.. plainly only 2.4ghz is going to work.
So jump into the airport utility manual setup.. and go to the wireless page.
Depending on how old your TC is, setup a wireless name.. no spaces no special characters.. very short also is just as useful as very long. tc24 will do nicely.. Change the name of the 5ghz if it is later model to something also similarly simple.. tc5 might be nice. Call the TC a nice name again no spaces.. which it will have by default.. no special characters pure alphanumeric. TC is nice simple name.. Hard to forget really.
Set manual channels for the 2.4ghz.. this is utterly important.. repeater or bridge does not work with auto bouncing all around the place. Choose a suitable channel out of 1, 6, 11.
5ghz won't matter so you can leave that on auto if you want.
Lastly security..
Let me suggest to start leave security off. Get it setup so you know it works then come back and test the security levels.
I am not sure what to select here.. you want wpa but the dd-wrt says not wpa+wpa2..and apple do not offer straight wpa as the bridge cannot resolve which to use.. you might need to use wpa2.. but that doesn't work on some routers with repeater.. or bridge.. you are going to have a bit of trial and error here.
Make the password something nice.. you guessed it pure alphanumeric.. no spaces, no special characters.
be creative and simple.. tc24passkeynot5 .. of course use what you like.. I am giving examples to make it easier. Update the TC.
Now just do the bridge setup on the WRT300.. there are two kinds of bridge.. client bridge and wireless bridge.. there is also repeater. Client bridge has no routing .. that is what you want. But it does other things which may make you go back. Please note bridges are strange beasts.. this is going to hide clients behind the Linksys MAC address.. and it can lead to issues.
Anyway read the setup tutorial. http://www.dd-wrt.com/wiki/index.php/Client_Bridged
You will find earlier one if you use the index.. this is also useful to read. And is more extensive.
http://www.dd-wrt.com/wiki/index.php/Wireless_Bridge
There are several scattered around and I can point you to others.
When you are finished you will often need to reboot both boxes to get the bridge to establish.
Once you are done. See how it goes..
I tend to advise people that wireless bridges are flakey and will do down at the moment you want them to work. You can get EOP adapters which tend to be more reliable and use the WRT300n in wan bypass as a switch and WAP.. This is much more reliable.

Mini can't connect to the internet via ethernet bridge

I installed a Netgear WGPS606 (It's a print server and wireless ethernet bridge) on my home wireless network. Here's the Configuration: DSL connected through a Linksys BEFSR41 DSL/Cable router with 4 port switch. My Graphite Airport base station connects to one of the ports on the switch, and it serves the wireless computers on the network. The WGPS606 is connected wirelessly to the Airport Base station. I have a MacMini connected to one of the ethernet ports on the WGPS606. The Mini successfully gets its IP address from the DHCP server on the Airport. (Interestingly, the Airport's DHCP server is configured to provide addresses for airport clients, not ethernet clients, but it does provide an IP address for the Mini -- I assume because the mini is connected through the wireless bridge.) I can see and connect to the Mini via the local network, but the Mac Mini cannot connect to the internet.
Any clues?
Mark

Never mind. I gave up on the Netgear print server and bought a second AirPort Express and set up a WDS network. Everything works like a charm. That's the last time I waste nearly a day of my time to save $30 bucks on a piece of hardware.

Airport Express as "Ethernet-Bridge" for old iMac - how to configure WPA?

Hi,
I have a very old iMac G4, which up to now was connected to my network via a Netgear wireless bridge. As I switched my router to a Fritzbox, which supports N-Draft I wanted all network clients to use N-Draft, so I bought the new AX.
It works ok as an Ethernet bridge when configuring the wireless part to "connect to a wireless network", "allow ethernet clients" and no encryption.
I am now online with that configuration.
But when I activate either WEP, WAP, WAP&WAP2 encryption on my Fritzbox router and then in the Airport Express it won't get an IP-address via DHCP anymore. It can connect to the wireless network, but via the ethernet connection it does not assign ip-address anymore.
I already tried assigning the IP-address manually. The light on the AX is green, but DNS does not resolve, although I also entered the DNS server of my provider manually.
Any idea? Is it perhaps just not possible the use the ethernet port if the wireless connection is encryted?
Regards,
Jörg

Hi again,
I can answer my question now: my router (Fritzbox) and the Airport Express can only communicate with ONE kind of encrytion - only via WAP2.
WEP does not work, WAP does not work, WAP/WAP2 does not work.
But at least now I have a complete N-Draft Network with good encrytion. It only cost me 4 evenings of long trial & error configurations.
Hope I can at least help others,
Jörg

6500 DHCP ISSUE

Hello All,
I am having an issue do DHCP from the 6500, and was hoping someone cant help. So, I tried to setup DHCP from the FWSM to the clients and this worked fine with giving out the IP, however the gateway for devices on the inside is supposed to be the 6500, not the FWSM, which is why the clinets wouldn't get out to the internet. Do I need to set up DHCP relay on the FWSM or does anyone know the way I can setup DHCP on the 6500 to give out IP's to the clients. Again just to reiterate, when I setup DHCP on the FWSM the clinets get the IP's but do not get out to the internet and when I setup DHCP on the 6500 the clients do not get an IP. Also I know tghis is a dhcp issue becasue when I assign a static address on the network the clients get out fine. Thanks in advance for the help!
6500 Config
ip dhcp pool TEST
   network 1.1.1.0 255.255.255.0
   default-router 1.1.1.1
   dns-server x.x.x.x y.y.y.y
FWSM Config
FWSM/TEST# show run
interface Vlan3
nameif outside9
bridge-group 1
security-level 0
interface Vlan203
nameif inside9
bridge-group 1
security-level 100
interface BVI1
ip address 1.1.1.4 255.255.255.0
passwd 2KFQnbNIdI.2KYOU encrypted
access-list INSIDE1_IN extended permit ip any any
global (outside1) 1 x.x.x.x
nat (inside1) 1 1.1.1.0 255.255.255.0
access-group INSIDE1_IN in interface inside1
route outside1 0.0.0.0 0.0.0.0 1.1.1.1 1
FWSM/TEST#

Hello Alain,
Thanks for your quick response. I attached a Diagram of the layout. Just to let you know this is an FWSM with many virtual contexts and most including this one that are Transparent. I understand that I need an access-list on both ends to specifiy so the FWSM opens it, I am just having issue because the FWSM sees this as unsual traffic and the access-list needs to be on-point to work. Thank you for the response and I'll look forward to hearing back from you.

Dual RAP Mesh Network vs PTP Wireless Ethernet Bridging to provide link redundancy

Currently looking at a few options to optimize a current point-to-point wireless LAN-to-LAN connectivity shot for a wired customer site for better redundancy (hardware diversity and/or logical path diversity). Currently the customer is fed via an older solution, using two Cisco 1522 APs with Cisco Aironet 14-dBi Path Antennas (AIR-ANT5114P-N) for a 5-GHz PTP wireless ethernet bridge (under 3km), in which one 1552AP hangs off a L3/L2 Distro switch and the customer's 1522AP hangs off a 3750X switch, which has another access switch hanging off it via a fiber run of about 2km, which is exposed in parts and can't be re-run again due some limitations.The customer doesn't utilize any wireless services. Due to their location, we can't connect them to our wired distro infrastructure directly via fiber.
Looking at setting up two wireless shots (instead of just one currently used); 5-GHz point-to-point bridges using upgraded gear: Cisco 1552EU APs with Cisco Aironet 14-dBi Path Antennas (AIR-ANT5114P2M-N) or straight Exalt r5005 solution. The PTP shot will hang off two seperate distro switches for redundancy purposes, pointing toward the customer site at two seperate locations, spaced apart by approximately 1 to 1.5 km, so that they aren't at the mercy of being isolated on one side if they have another fiber cut which connects their two main access switches together. If need be, we can hang two main APs on one distro facing two APs at the customer site, since this would create some redundancy, just not the same level as above.
The below is what I'm really unsure on.
Possibly looking at setting up a mesh network using Cisco 1552E APs with 2.4 GHz Omni-directional antennas (either a 2.4/5GHz Terrawave MIMO Omnidirectional antenna or Cisco AIR-ANT2547V-N antennas, which ever is best) with two RAPs, one RAP hanging off one distro and the other RAP hanging off another distro for hardware diversity, both under the same bridge group name and both RAPs hanging off the same WLAN management SVI subnet on the distros. The customer site will have two 1552E MAPs located at two seperate sites, as pointed out above. I don't think a third AP would be needed, since they don't use wireless services. Since there would be only two RAPs, not three, would it be best two set-up this with both RAPs on the same channel to minimize convergence time should the mesh transfer from one RAP to the other RAP, as long as both RAPs are spaced apart under ???? distance to avoid interference/other issues? Looking at some documenation, it appears you can have a MESH network, as long as your MAPs and RAPs fall within a 2 mile range area, preferably closer to a 1 mile range area (for better bandwidth & reliability). This solution has been brought up as possible dual-homed solution in theory, by virtue of having two more more MESH APs fall within the range listed above, to the RAPs. From a layer 3 perspective, I'm not sure what the most optimal idea to run with in this scenario set-up would be. Possibly set-up two seperate user SVI VLANs (for their data services), one placed on each access switches these MAPs will hang off at the customer site, & using the same management SVI subnets as the RAPs for the wireless managment side (for accessing the APs). From my understanding, the user data SVI doesn't matter from the perspective of when the mesh transfers from one RAP to another, it should be transparent to them. The distro switches will just have the management SVIs placed on them for the RAPs, the user SVIs will be placed local on the access switches only. And all APs will hang off access ports set to the management VLAN ID.
In my opinion, the PTP 5-GHz, dual distro homed solution makes the most since for wired client access, but since the latter option was brought up, it has to be weighed - plus I'm curious if it can work.

The Exalt r5005 works great for redundancy PTP links. You have to use the sync cable between the two co-located bridges and also set the polarization on the bridges. You can then use routing or spanning tree to decide traffic path. With mesh, you will have to make sure you set the parent or else the maps will keep switching perhaps.

Labview 2011 always disconnecting over wireless Ethernet bridge!

Hello, we recently upgraded from labview 2009 to labview 2011. We use a Labview cRio-9014 and FPGA backplane 9114. For connecting the cRio to our laptop we use Digi XPress Ethernet Bridge: Multipoint 900MHz industrial wireless part# XEB09. This program worked over our wireless link running labview 2009 with the old cRio software.
After upgrading the desktop, upgrading the cRio's software and recompiling the FPGA code we tested our setup via a wired ethernet connection and ran it all day with no problems. However once we switched to using our wireless ethernet bridges the cRio disconnects always 2-3 minutes after starting. It also does not allow us to reconnect without powercycling the cRio. The radio modems show a solid connect and no problems the whole time. Now I've searched through known issues and all over the forums without finding anyone having a similar issue so I hope someone can chime in and let me know if something else in LV2011 changed or what.
My current hypothesis is that labview 2011 uses UDP packets for status/keep-alive and our radio modems are not guaranteed to recieve all UDP packets. Please correct me since this is only a guess and I don't know what's going on under the hood on the cRio side.
P.S. I've captured the packet data using WireShark on the laptops side from deployment until disconnection but can't find any obvious problems. It's a fairly large file so let me know if it's needed and I'll try to find a way to upload it.
Hopefully someone can help.
Best Regards,
Sam Bingham
Great Lakes WATER Institute

Our host OS is WIn7-64Bit, and XP-32bit but they all display the same behavior.
cRIO hardware: cRio-9014 and FPGA backplane 9114
Our system is has 4 modules installed NI-9205, NI-9401, NI-9401, NI-9870, although we are only using the serial ports on NI-9870.
I looked for the NI TimeSync to remove but it isn't listed in our installation
Contents of current installation:
CompactRIO Support 4.0.0
DataSocket for LabVIEW Real-Time 4.9.0
HTTP Client 1.2.0
HTTP Client with SSL Support 1.2.0
I/O Variable Remote Configuration Web Service 1.0
LabVIEW 2011 Adaptive Filter Toolkit 11.0.0
LabVIEW PID and Fuzzy Logic Toolkit 11.0.0
LabVIEW Real-Time 11.0
Language Support for LabVIEW RT 1.0.0.4
NI Application Web Server 2.0
NI System Configuration 5.0.0
NI System Configuration Network Support 5.0.0
NI Web-based Configuration and Monitoring 2.0.0
NI-RIO 4.0.0
NI-Serial RT 3.8.0
NI-VISA 5.1
NI-VISA ENET Passport 5.1
NI-VISA ENET-ASRL Passport 5.1
NI-VISA Remote Passport 5.1
NI-VISA Server 5.1
NI-VISA USB Passport 5.1
Network Streams 1.1
Network Variable Engine 1.8.0
Remote Panel Server for LabVIEW RT 4.0.0
Run-Time Engine for Web Services 4.0.0
SSL Support for LabVIEW RT 4.0.0
System State Publisher 2.0.0
Variable Client Support for LabVIEW RT 1.8.0

Ethernet Bridging - Client DHCP issue

Similar Messages

Maybe you are looking for