WDS and Roaming with 1130AG APs

Hi there,
I was wondering if someone could provide me with some insight into a configuration scenario i'm facing:
Our office is situated in an old building and as such , wireless range is an issue as the walls are very thick and we have a mixture of clients from Laptops to android devices to iPhones that require access.
we have 2 goals (first 2 are more important)
1. to be able to roam anywhere in the building and pickup the wireless (fast roaming isn't really that necessary as voice isn't utilised)
2. to have only 1 SSID for corporate access - Corp VLAN
3. to have an SSID for guests to access - Guest VLAN
The VLANs aren't an issue, i have an 1130AG setup which already has 2 SSIDs which does what i need.
My main concern is around roaming, and i've read a lot about WDS, but this needs an external radius server, i've seen the articles that describe how to set up an AP as WDS and then add Infrastructure APs
I've also seen that you can simply configure each AP exactly the same, but with different channells.
I have 4 1130AGs at my disposal.
What would you guys suggest is my best solution?
Any help would be gratefully received.

To get the best roaming, you need to make sure you have enough coverage. That usually means a good site survey was performed to specify how many access points and the locations of the access point. Without this piece, there is no guarantee of roaming.
As far as WDS, you can setup an autonomous ap as a WDS server that is either dedicated as a WDS or is a WDS server and also serves clients.
Sent from Cisco Technical Support iPhone App

Similar Messages

WAP2000 fails WDS and roaming

Hi,
I'm wondering if anyone on this forum has successfully used WAP2000 access points.
I'm particularly disappointed with these device:
Hardware Version:
1.0
Software Version:
2.0.0.5
I set two of them up with exactly the same wifi security settings, same channel and WDS, one of which is a repeater (MAC addresses correctly set).
Whenever I turn the repeater station on, the wireless supplicant not only doesn't extend it's coverage but if it's within the AP's outer range then it LOSES its connection with the AP. It's as if the wrieless repeater "jammed" the connection. I tried just about every possible setup and came to the conclusion that WDS does not work with my WAP2000 devices.
I don't even "require" WDS to work if at least a decent roaming could be done. So I setup 2 WAP2000 as 2 APs with exactly the same wifi security settings and different, non-overlapping channels (same SSID). Roaming *should* be fairly quick but it lasts between 30 and 50 seconds!
I replaced both WAP2000 APs with older WAP54G APs (same settings) and roaming is "fast" (less than 3 seconds!).
So on one hand I'm demonstrating that roaming does NOT depend ONLY on the client side and that APs can be the culprit.
On the other hand, I'm also showing how bad the WAP2000 product is (it's more expensive than the WAP54G but is completely unreliable).
No wonder there are so few references on the web to the WAP2000 device.
"Cisco" isn't as good as it sounds (I know it's "small business" but it's still Cisco).
If someone here has had a similar experience and has found a solution, please let me know.
Otherwise, I'm definitely not going to value the "Cisco/Linksys" brand as well as I did in the past.
Thanks,
Vieri

To get the best roaming, you need to make sure you have enough coverage. That usually means a good site survey was performed to specify how many access points and the locations of the access point. Without this piece, there is no guarantee of roaming.
As far as WDS, you can setup an autonomous ap as a WDS server that is either dedicated as a WDS or is a WDS server and also serves clients.
Sent from Cisco Technical Support iPhone App

Basic question on roaming with 12XX APs

Hello,
We are installing 6 or so Autonomous 1242s which will be side by side with an already installed group of autonomous 1100 series. Does roaming between APs on the same SSID happen automatically as you reach a certain low level of signal, is there anything specific that has to be setup? I've read about WDS, but the clients are not using Cisco Aironet NICs and are using WEP. Any assistance on how the roaming takes place and how to make it as seamless as possible would be fantastic!
Thanks,
JG

Roaming is the behavior of the wireless client. How and why a client roams is based on the driver largely. Some clients roam better than others and use different measurements to indicate when a client should roam.
When a client hits its threshold it will send PSP (power save poll) frames to notify the access point to which it is already associated to, to buffer frames as the client goes off channel to find other access points to roam to. The client will flood all channels with probe request, access points within the range which hear the probe request will respond with probe responses.
The client will then decided based on probe responses which access point it will then auth and ass to ..
With all that being saidâ¦ you want to make sure you have a proper survey done so you don't have access points to close or to far away to each other, thus causing co - adjacent channel interference.
Normally you want your access points powered at the lowest client level. Again, you don't really want them very loud (reaching further than they need to) or to low where you have a ton of access points either.

WDS and Roaming??

I have read other posts on this topic, but still cannot seem to make full sense of the issue. Here is my situation:
I have read through this thread...thanks to all. I have a similar situation, but have not yet purchased or attempted to implement, but have a slightly different network topology in mind. I would like to know before I go and drop the cash if I am on target. Here goes:
Internet
|
_DSL Modem_
|
AX3----------(Roaming/Ethernet)------AX1----------(Roaming/Ethernet)-------AX2
WDS main
AX4
WDS Remote/no wireless
Imac (ethernet)
Three AXs in attic of large house connected via ethernet, set to dual mode. AX1 is connected to DSL Modem/Internet. AX3 is connected and bridged (roaming) to AX1 and AX2 in attic, but also set as the WDS main. AX4 is on the first floor, directly (but two floors lower) from AX3 and will be configured an a WDS Remote with an iMac (gen 2) directly connected via ethernet.
Is the a sensible solution (wiring to first floor in a 1925 plaster walled house is a headache to say the least).
What I am trying to accomplish is using a wireless connection between a third floor attic space, and a first floor non-wireless machine, while still providing good wireless coverage throughout the house for wireless devices (apple TV-XP laptop etc).
Thoughts from those who know way more than I??

Duane,
Thanks for the feedback. I am worried about the density of the walls 12-18inch thick and am pretty sure filled with old lead paint in the undercoats. I have been so disappointed with the coverage areas I have seen in older houses with wireless, I thought some overkill might be necessary. But I may have over done it a bit.
I have determined a slightly different configuration after fishing some walls today, and am planning on installing the DSL in the basement (instead of the attic). This way I can:
1: attach an airport extreme under the house (centrally located) attached to the DSL
2: wire from under the house to 1st floor location with an ethernet link to the iMac
3: make an ethernet run from the basement to attic (2 floors away) thru a chase I found
I will try using just two AXs in the attic and see what the coverage is. What is the best tool for determining overlap of wireless signals. This might help in planning the network. I bought an AE gigabit today, in hopes that I could determine rage etc. in the house.
Again,
Thanks for the input.

WDS and WPA with 2x Express and 1 x Extreme - barbed wire in the *** easier

Frankly I am disgusted at the near impossibility of getting this to work after 5 hours of playing, resetting and stuffing around. Apple need to pull their fingers out and realise that "we make em simple so you don't need docs" is not going to cut it for everything.
Each time I get aways into this (got it working sans WPA after 3 hrs) I get either a non subnet IP address, or the Setup Utility can see but not open a station. No probs hard rests all around and awayyyyy we go again.
At this stage I will NEVER purchase a Airport base station again. My years with NetGear showed how it can be done properly.
If this keeps up, and factoring in my 2 day old dead iMac, I'm off to Dell for a complete technology refresh!
Has anyone ever got this simple configuration to work? if so can you point me at some doc or tips?
Forgive me for wanting security and wireless access at the same time!
Rant=off, apologies=on
regards Paul

Thanks Dwayne,
However I had already upgraded Firmware on all devices.
I actually solved the issue as follows:
1) The problem was that using the auto-config feaature of the Airport Admin Utility kept crashing as it tried to update the Main Base Station. It was in effect freezing in the rejoin and getting a 169.x private address - therefore unable to see the 10.0.x subnet of the network.
2) Use the auto-config, but once the Remote Base Station(s) are updated, power them off before the wizard gets to the Main Base Stattion.
3) It then manages to see the right subnet and can complete the update.
My guess is that this is an isue with more than 2 Airports and the very slow speed of the DHCP service on the Airport Extreme.
I am dissapointed to say the least.
Cheers
Paul

Connect to a specific AP541N in a cluster system, and issue with cluster+WDS

We are running with four AP541N in a cluster (connected to a SA540), where they all broadcast on the same SSID and channel (9). If we forces one offline by unplugging the power, a client is automatically connected to another AP in the cluster. But we have a few questions:
1) For testing purpose, is it possible from Vista/Win7/XP to force connection onto a specific AP in the cluster? Only one network is shown in the list, and the AP with best signal seems to be the one automatically choosen.
2) One problem we have found is that two of the APs have a WDS connection between them (one is at a location where we could not easily cable it). This also seems to basically work fine with clustering, but if the wired part of the WDS goes offline, the clients already connected to the wireless WDS AP does not get kicked out, but do of course loose their connection to the network. Even worse, clients connected to the wired WDS AP (which "went down"), might be transferred to the wireless AP with no network connection since the signal from this might be the best...! Any way to solve this, so that APs depending on the WDS kicks out their clients if the WDS is broken....?
We do also seem to be biten by the "speed degrade" issue of the APA541N now-and-then, particulary on the AP beeing the wired part of the WDS. Using WPA-PSK, and having set the recommended "key refresh" setting to 0, without seeming to help anything at all. Running FW 1.8.0, and really hoping for a new FW fixing this issue to appear soon!
- Ola

Thanks Dave!
The setup is like this:
SA540
|
|- AP#1
|- AP#2 ( ( ( WDS ) ) ) AP#3
|- AP#4
|- + printer
The network is intended mostly for laptops which uses wireless network. The implementation is on a sports arena, and to get good enough coverage we had to put AP#3 in a tower across the outdoor space. It have free sight with only glass windows between to where AP#2 is (which is also quite high), but AP#3 then helps to cover the ground area which AP#2 did not properly do alone. So AP#3 is connected to AP#2 with WDS, and acts like a repeater. No equipment is connected to the ethernet port of the AP#3. We are not able to acheive the same coverage from any place where AP#3 could have been cabled, so WDS from AP#2 is our only option here.
If AP#2 goes down (as in forced down by unplugging the power when testing), clients connected to AP#3 is left untouched but looses their connection with the network. Non of the other cabled AP's are in such a postition that they can set up a another WDS to AP#3 (as it seems is possible with AP541N, to have several WDS connections on one unit, without me investigating further into this). The best would be that AP#3 would kick out the connected clients if WDS goes down, since most of the potential clients might be able to get a useable connection to AP#1 instead.
Problem 2 here is that error recovery on this should hopefully happen automatically, since there might not be any technicians around at all the time this is beeing used.
Even that it is announced to be so, we find the loss of speed with WDS to be quite noticeable. Sitting with a laptop at the same location as AP#3, and getting a 3of5 bar signal from AP#2 with a 11g laptop, we get max internt speed (which is ~10Mbps). But then booting the AP#3 and connecting to this instead, we only get speed in the range 3-4Mbps. Should the WDS and the AP acting as repeater drop the speed this much? WDS is configured with WPA-PSK and spanning tree enabled. All the AP's are running in 11bgn mode, and the regular broadcasted net is using WPA-PSK too.
- Ola

WDS wired and wifi with mixed airports

Hi,
I've been having a heck of a time with 'fixing' a mixed wired and wifi network. 2 days so far and it's still not how I want it.
It was working okay, then I started getting errors with IP's being duplicated, so I started over.
Here's what I have :
Orange France Livebox (dsl router)
ABS-g (dual ethernet)
ABS-n (pre-mixed g/n environment)
2 AExpress-g
Netgear Switch
Original setup :
livebox to netgear switch, feeding wired ABS-g (dual ethernet) and wired ABS-n (pre-mixed g/n environment). ABS-g acting as Main for WDS and feeding ABS-n via the switch, plus 2 AExpress-g via wifi.
It all worked for about 2 months. Then the problem with duplicate IP addresses.
So now the setup I have is :
Livebox wired to ABS-n, which then feeds to Netgear Switch to LAN wired, plus, 2 AExpress-g on WDS via wifi.
This works.
Here's the problem :
I want to extend the wifi network via wired, because there is some distance between the base stations. HOWEVER. Whenever I connect one of the base stations, which is configured as WDS Remote, via wired, I instantly loose my internet connection ... everywhere. Wired and wifi.
The base stations get self assigned addresses and I have to take the cable out of the ABS-Remote and then, take the cable (from the Livebox to the ABS-n) out of the ABS-n and put it directly into my Mac, to get the connection back.
I have restarted, zeroed everything many times. Finally I have narrowed the problem down to trying to have a wired connection to one of the WDS remotes. As soon as I plug a cable into a WDS Remote, I loose the connection.
Can anyone suggest what I might be doing wrong, or how I could reconfigure to enable either the ABS-g (dual ethernet) or one of the ABSExpress's to operate via a wired connection, thus much more effectively extending the wifi network.
Any help/pointers much appreciated.
Grant

Please take a look at this Apple Support reference to see if it will help you identify your AirPort: Identifying AirPort Hardware
I have seen that link elsewhere on this board. Unfortunately it's out of date. Yes you can go to the first page and visually identify your airport unit, but there is no model number next to the pictures. Clicking the 'More Info' link returns an error that the page does not exist.
The same holds true for the Apple pdf about designing Airport Networks. Dead link.
In a roaming network, ALL of the AirPorts must be connected by Ethernet or be on the same Ethernet subnet. Adding the Ethernet switch to one the 802.11n AirPort Extreme Base Station's (AEBSn) LAN ports will provide the additional wired ports for the AEBS and the AXs.
Since you have the AEBS connected by Ethernet to the Livebox, all of the AirPorts must all be reconfigured as bridges. Each will broadcast their own wireless network, but this network will have the same Network Name and use the same encryption setting. The only difference is that each AirPort must operate on a radio channel at least 3-5 channels away from that used by next nearest AirPort to prevent interference.
Having spent another hour or so, reconfiguring again, I've understood, that I cannot have an unwired ABS on a roaming network, even if it would appear to be on the same subnet. It gets no IP and is therefore lost in space.
So it would seem that anyone wishing to include some wired and some unwired ABS in a single 'seamless' network, needs to make a WDS for all the unwired ones ... and a Roaming network (with the same network name and password as the Main ABS network) for the wired ones.
This is what I have done and it looks to be working perfectly. All are in Bridge mode and all are on Automatic Channel ... and I note that the Airport Utility automatically gave a very distant channel to the wired ABS.
The network appears to be stable and fast. Phew.
As an aside ... it's a shame that the Airport Utility, whilst clearly a very clever piece of software, doesn't have more helpful explanations of what is going on. The wording is often ambiguous at best. A teeny bit more explanation would have saved me hours and hours of wasted time.

Consistent Roaming with WDS on AP1142n WAPs

Hi there
Background
I have 3 Cisco AP1142n with one as the WDS and running local radius, the WDS then authenticates to an external FreeRadius server. The SSID is using EAP-TLS authentication.
The other 2 AP's are running as WDS clients and they have registered and authenticated fine against local radius on WDS AP
Problem
Users are able to roam however 90% of the time this does not work and users who are connected to a VPN lose their connection and have to re-ath to the SSID.. I am also seeing the pattern is that when users roam from WDS-Client AP 1 to WDS-Client AP2 , this does not work however when they then re-auth to WDS-Client AP2 and back to AP1 this works fine.
I have following debug enabled on the WDS device
General OS:
AAA Authentication debugging is on
AAA Authorization debugging is on
dot11/wlccp authenticator:
receive packet debugging is on
transmit packet debugging is on
state machine debugging is on
process debugging is on
Mac Authentication debugging is on
Dispatcher debugging is on
List of MNs with WDS events debugging enabled :
b88d.1213.1b3a
The question I have is the following line which I keep seeing in the output
May 13 12:24:47.980: AAA/AUTHOR: auth_need : user= 'xxx' ruser= 'AP-WDS-01'rem_addr= '10.x.x.x' priv= 1 list= '' AUTHOR-TYPE= 'commands'
May 13 12:24:51.243: AAA/AUTHOR: auth_need : user= 'xxx' ruser= 'AP-WDS-01'rem_addr= '10..x.x.x' priv= 15 list= '' AUTHOR-TYPE= 'commands'
May 13 12:25:17.259: AAA/AUTHOR: auth_need : user= 'xxx' ruser= 'AP-WDS-01'rem_addr= '10.x.x.x' priv= 15 list= '' AUTHOR-TYPE= 'commands'
Do these lines tell me anything?
Also in addition
WDS Statistics for last 4d19h:
   Current AP count: 3
   Current MN count: 0
   AAA Auth Attempt count: 12
   AAA Auth Success count: 12
   AAA Auth Failure count: 0
   MAC Spoofing Block count: 0
   Roaming without AAA Auth count: 15
   Roaming with full AAA Auth count:5
   Fast Secured Roaming count: 0
   MSC Failure count: 0
   KSC Failure count: 0
   MIC Failure count: 0
   RN Mismatch count: 0
What do the above bold lines tell me?
Kind Regards

Agree with Rasika..
if you are using 802.1x, then only you would want to configure WDS for the key caching.
if you are using a PSK, then all you need to do is configure the AP exactly the same way, with the exception of the IP address on the BVI interface, as long as the ssid and encryption are the same, and there is overlap between the cells the client should roam between the AP
Regards

How to improve client handover and roaming between AP's

Improving client Handover and roaming between APs
There are a few standards and methodologies available to use to improve handover of clients between APs. Most are focused on VOIP technologies, but it must always be remembered that we cannot control the client Handover (especially with legacy clients) we can only encourage them. Some Standards and methods work well for some environments and some do not - test the recommendations extensively before implementing in a live Production environment. It must also be noted that all settings take effect immediately once applied, however from a client perspective it might need to re-associate for the changes to take effect client side.
As with everything else in IT, if a perfect method/solution existed there would only be one - try them all and keep the best.
The Standards and Definitions
802.11k
IEEE 802.11k allows a device to quickly identify nearby APs that are available for roaming. When the signal strength of the current AP weakens and the device needs to roam to a new AP, it will already know the best candidate AP with which to connect to.
802.11r
IEEE 802.11r specifies fast Basic Service Set (BSS) transitions between access points by redefining the security key negotiation protocol, allowing both the negotiation and requests for wireless resources to occur in parallel.
When a device roams from one AP to another on the same network, 802.11r streamlines the authentication process. BSS allows a devices to associate with APs more quickly. Coupled with 802.11k's ability to quickly identify the target AP, BSS's faster association method may enhance application performance.
Handoff Assist
The AP monitors the RSSI for every associated client. If the RSSI for a specific client falls below "low-rssi-threshold" and continues to fall for the "rssi-falloff-wait-time", then the AP will send a de-auth to the client.
The de-auth is meant to kick the client away from the current AP and get it to re-authenticate to a nearby AP. This will have the effect of helping a client handover between 2 APs.
BUT (Big But), if the client gets de-authed and takes a while to re-authenticate (if it even does re-authenticate automatically after a de-auth), then this will have the effect of destroying communication instead of helping it -- mostly found with legacy clients.
Remove Lower Transmit Rates
Removing lower transmit rates is a way to promote better roaming, BUT not all clients respond well, or even respond to it.
The practice is that the basic rates are a subset of the transmit rates. If you only want to allow speeds 9 and up, you would select only the transmit rates of 9 and up, and the basic rates of 9 and 11. If a legacy client expects the rates of 1 and 2 it will not connect.
Local Probe Threshold
Local probe Threshold prevents a client from connecting to an AP with a too low a signal - helps more with initial connection than roaming.
The local probe threshold parameter is not supposed to force clients to roam as soon as they pass near an access point with a good signal, but rather to NOT hold on to an access point with a weak signal (avoiding sticky clients).
PMK Caching
Defined by 802.11i and is a technique available for authentication between a single AP and a station. If a station has authenticated to an AP, roams away from that AP, and comes back, it does not need to perform a full authentication exchange. Only the 802.11i 4-way handshake is performed to establish transient encryption keys.
Opportunistic Key Caching (OKC)
Is a similar technique to PMK, but not defined by 802.11i, for authentication between multiple APs in a network where those APs are under common administrative control. An Aruba deployment with multiple APs under the control of a single controller is one such example. Using OKC, a station roaming to any AP in the network will not have to complete a full authentication exchange, but will instead just perform the 4-way handshake to establish transient encryption keys
Implementation and Configuration
802.11k
802.11k is configured in your VAP profile. Tick the option to “Advertise 802.11k”. There after set the Handover Trigger Feature Settings.
Tick the “Enable Handover Trigger feature” and then set RSSI threshold by specifying the -dBm level at what the hand over trigger should be sent to the client
802.11r
802.11r is configured under SSID of your VAP profile. Tick the option to “Advertise 802.11r”
HandofF Assist
Station Handoff Assist is enabled in RF Optimization under the RF Management section of AP configuration.
Tick the “Station Handoff Assist” option to enable it, next set the Low RSSI Threshold – the threshold determines above what level no deauth gets sent
Lower Transmit Rates
Transmit rates can be adjusted in the Advanced tab of SSID under your VAP profile.
Remember that the basic rates are a subset of the transmit rates. If you only want to allow speeds 9 and up, you would select only the transmit rates of 9 and up, and the basic rates of 9 and 11
Local Probe threshold
Local Probe threshold can be adjusted in the advanced tab of SSID under your VAP profile.
Depending on the density of your APs consider values between 20 and 40 -- 40 being aggressive in an AP dense area.
Deny Broadcast Probes
Denying Broadcast Probes can cause problems with Roaming especially if the SSID is hidden – leave option disabled.

Hi, thank you for the helpful guidance. I have a basic question, if the device roam from one AP to another AP with the same SSID. Is there a need of re-authentication given a) the network uses EAP based authentication; b) the network uses MAC address authentication. If there is no need of EAP re-authentication, how the 802.11 keys are moved to the new AP. Thank you very much if you could help me clarify my thought.

WDS and authentication

We have 1200 APs configured with mobility networks (mGRE tunnels terminated on a WLSM). The APs are pointed at the WLSM WDS and pass their authentication requests to the WLSM acting as the WDS using WLCCP. However, these APs also provide wireless access to the local wired networks. This can be configured, but it appears that all authentication requests go via the WDS (i.e. all locally configured RADIUS servers for local network authentication are ignored).
The WLSM Deployment Guide suggests that it is possible to have "WDS" and "non-WDS" SSIDs coexist. The consequence is that the availability of the WDS (on the WLSM) becomes critical, even for APs which could authenticate local wireless users through RADIUS servers configured directly on the AP.

WDS checks its local list for authentication . If the Mac address is not present it uses configured Radius server for authentication. Make sure Mac address is either in the Local list or Radius server. If you are using Radius server make sure Mac address is configured as user

Roaming with the same Ip address

folks,
very strange, i have mutliple vlans defined on my access-ponts, when i use a laptop and roam, i get the same ip address when i disassociate and them reassociate with another access-point, shouldn't i be getting a new one???
Thanks

This is the normal behavior. When multiple APs are deployed and a certain set of clients to roam between all of these APs, they should be set to use the same SSID and the same VLAN. If they are put on different VLANs,clients will have problems getting new IP addresses or may have disconnects when they get a new IP address.

E2500 with multiple APs for guest access

I got 5 E2500 routers and the main one has setup to IP address 192.168.1.254 and the rest APs are programmed into the bridge mode with the IP address 192.168.1.245 through 248. The secured wireless network works fine when I roaming between these APs but the only AP that I can get internet access for guest wireless network is the main (192.168.1.254) router; for every other APs, I will get the guest log on screen (prompt for guest access password) and no internet access after I type in the correct access password. Does the E2500 support multiple APs guest or it requires a special way to configure it? Please help...
Jim

Guest Access allows you to provide Internet connection to your guests, however, they will not have access to your computers or other personal data. When you set up your Valet or Linksys Wireless-N router, the Cisco Connect software will create two wireless networks with the same Wireless Network Name (SSID) that differs from one another by a -guest suffix to one of the wireless network names.
So first of all remove all the networks from the preferred list of the computer and then try to connect.

I am traveling to India, north and south, with my ipad 2, G-3. It is activated by AT and T. How do I use it in India? Do I need to purchase a sim card there and if so what kind? Would they be available in the Delhi airport or where else in central Delhi?

I am traveling to India, north and south, with my ipad 2, G-3. It is activated by AT and T. How do I use it in India? Do I need to purchase a sim card there and if so what kind? Would they be available in the Delhi airport or where else in central Delhi?

Also in order not to pay a fortune for the service is it better to acquire if needed a SIM card only once there?
Check with your carrier about roaming charges. They are usually prohibitive. Best to get a local SIM.

WDS and Closed Network

In an already existing WDS network (functioning in G model) is it possible to select the "Closed Network" in all my WDS routers and still have WDS functioning?
The reason I ask is because it is possible one of my neighbours is sabotaging my network and making it "invisible" there might a less likely chance for him to find my network (as long as he's not that savvy). What's been happening is I discovered today that the reason Time Capsule backups were happening so slowly is because my network conflicts with his--but only recently. I was on radio signal 1 and so was he/she. So I switched it to radio signal 11. Less than 2 hours later, his/her network radio signal is also on 11. So I have my suspicions...

Yes, my network is closed now. Security has always been enabled at WPA2 but enabling security does nothing to remedy malicious radio interference (if that is what my neighbour is doing). The reason I want to set it to "close" (invisible) is so that if the neighbour is not savvy enough, s/he will think my network is gone and no longer try to use the same channel I am.
Yesterday, I realised the reason my Time Capsule backups were going so slowly is because my neighbour was using the same radio frequency as I was (Channel 1). His/her network has existed for a while now and we never clashed before. So I thought it must have been just conincidence. So then I switched over to Channel 11. Well, two hours later, his/her network was also on Channel 11 making my network go from speeds of 54 to 11. So, I thought this is possibly him/her playing around and interfering with my network so I decided to go "invisible."
You are right that someone who is a bit more knowledgeable can figure out what the invisible networks are. It's not that hard. Even I can use iStumbler to see them. But, may s/he is not that savvy--I'm hoping.
Enabling security does nothing for radio interference. I've always had WPA2 security on.

Extracting Embedded Files From a PDF with Adobe.APS

I'm not sure if this needs to be here in security or if it needs to be in another forum, so if an admin feels it needs to move to a different forum, feel free to.
The situation I am in is that I get about 100-150 pdf's a day that I need to extract an embeeded file from. Right now this is a completely manual process and is very time consuming. What I have been trying to do is automate the process of extraction.
The issue I am running into is that the files are encrypted with Adobe.APS, and so my java code won't handle the security, and I can't find any other software that handles Adobe.APS.
I was wondering if Adobe had a product that could do this, or if there was an API that could handle this. I can perform the extraction on a platform of any flavor (Windows, Mac, Linux, etc...).
Any help in this regard would be greatly appreciatted. Thanks.

In my case I have a drop-down list of files with preloaded filenames to attach. Here is the code that works for me on a click of button.
var selectFileName = form1.subform.DropDownList1.rawValue;
if (selectFileName != "Please Select") {
var doc = event.target;
doc.importDataObject(selectFileName);
var MyPar1 = doc.getDataObject(selectFileName);
var filename = MyPar1.path;
After you click the button it open a windows dialog box asking you to choose the file and adds the attachment to the attachment pane in runtime. To view the attachments simply view the attachment pane in runtime after you add the attachments.
Good luck,
SekharN

WDS and Roaming with 1130AG APs

Similar Messages

Maybe you are looking for