I have a ASA 5505 with the security plus license. I have created 3 vlans. 1. Outside sec level set to 0. 2. Inside with a security level of 100 with a network of 192.168.10.0 and the third vlan is 192.169.20.0 with a security level of 100. I have the security option set to allow communication between vlans when the security level is the same. The .20.0 network is used for wireless which is working with no issues. I have a cisco WAP4410N with a management address of 20.2 I have an issue that from the wlan vlan I cannot access the ASA from either SSH or https. But hard wired to the 10.0 network i can access both WAP and ASDM. There are no special FW rules yet just the default. I can also ping nodes on each vlan from the opposing vlansI have added the WLAN for management access to the ASDM and SSH. when looking at the logs I see no denies i actually see the teardown of the connection when accessing https://192.168.10.1/admin
Make sure you have on your ASA
ssh <ip> <Subnet> <interface name>
Ip and subnet would be the allowed IP/subnet.
so it would resemble
ssh 10.0.0.0 255.255.0.0 WLANInterface
LANadmn
ASKER
yup thats in my config.
I have worked with ASA's before but this is a first I am adding a WAP4410N to the mix. I see on the WAP you can change the native, & management VLAN. but when I change it I cant get to the device at all. I end up resetting the device.
When hardwired I can access both ASA & WAP. When wireless I can only access WAP when I try to connect to the ASA by https (http://ip/admin) or ssh I can see the teardown happening in the logs just no connection. I do have the option on to allow communication with the same security level.
What I am saying is if your on the WLAN side of your asa you would connect to the wlan IP of your ASA.
On the inside of your ASA you would connect to the inside IP of your asa.
I wouldn't setup the outside as that could be a security issue. I personally do it because I have a static IP at my house and I hate coming into work for simple things.
After reconfiguring the WAP & ASA using your method above worked. I just dont understand why if I am on the wireless I cant access 10.1 from the 20.1 vlan. I can ping nodes just cant access the ASDM or SSH. Now I am going to play around with the vlans on my WAP. thanks again
pclinuxguru
It's because your connecting to an interface on the ASA not routing traffic.
LANadmn
ASKER
so should I create a static route from the 20.0 to the 10.0 and visa versa
ssh <ip> <Subnet> <interface name>
Ip and subnet would be the allowed IP/subnet.
so it would resemble
ssh 10.0.0.0 255.255.0.0 WLANInterface