I ordered a IPS module to a small ASA to replace a Snort IDS Server.I want only to perform IDS and reporting (not inline) The design (simplified) is
The problem is that i read this morning that ASA cannot handle this type of scenario, it can only analyse the traffic that is passing through it. Is there a chance to make this work ?
I am trying to finish a project and i now have a very un-natural networking question, but i figure that this is the correct place to ask it.
Tools:
Routing Device = Router.
Test App = Creates and Sends Packets through my machine's NIC via NDIS Driver.
WAN = Internet.
VPN = Connected over WAN.
I am trying to route/forward/nat promiscuous packets "TO" the Internet to finish my project. The packets are not addressed to my routing device, but it must take them and forward them on to a VPN connected over the WAN. The packets are actually created by my NDIS test app. This means that the packets will be generated on my local LAN, but will not contain the MAC or IP of the routing device. So they will only enter my routing device while it is running in a promiscuous mode.. how would you try to route promiscuous packets out to the internet?
How i can enable promiscuous mode on my Atheros AR9285 Wireless Network Adapter? I'm using windows 7 starter.driver version of my Atheros AR9285 Wireless Network Adapter:9.2.0.427.
View 4 Replies View RelatedWe have a typicaly environment, access, distribution, core, all switches are 6500s.I have a lab environment where machines should not talk to each other, so I think private vlans would be good for this. The problem is that the access connects to the distribution with a 802.1q trunk, while the distribution connects to the core with an 802.1q trunk. See the attached image for reference.
In this case, I would configure the primary vlan (888) on the two access switches, as well as the isolated (886) and the community (887), and set the associations.
vlan 886
name Isolated_PVLAN
private-vlan isloated
vlan 887
name Community_PVLAN
private-vlan community
vlan 888
private-vlan primary
private-vlan association 886,887
exit
The host ports would be set as such.
interface g3/40
switchport mode private-vlan host
switchport private-vlan host-association 888 886
My question is where to I put the promiscuous port? Is it on the uplink between the access and distribution? And If I configure it as I have below, what about the other VLANs that are needed at the access switch? Do they still pass through the trunk as normal, even with the private-vlan configuration? Or would every other VLAN need to be configured as a secondary private-vlan on the promiscuous port?
interface g5/1
switchport mode private-vlan promiscuous
switchport private-vlan mapping 888 886,887
Also, would VLAN access-lists be a better method for controlling this traffic?
Last night, I lost my NetFlix connection. It was no biggy, I just restarted the Cheers episode that I had been watching. This morning, I checked the DIR-655 log and the following is what I had found (date and times aren't accurate).
May 24 03:22:33 info [1076865.190000] device br0 left promiscuous mode
May 24 03:22:29 info [1076861.620000] device br0 entered promiscuous mode
May 24 03:20:20 info [1076732.020000] device br0 left promiscuous mode
May 24 03:20:16 info [1076728.140000] device br0 entered promiscuous mode
May 24 01:45:42 info [1071054.590000] device br0 left promiscuous mode
[code]....
Promiscuous Mode is usually the result of sniffing according to Wiki. Whatever is promiscuous mode. Also, I don't know what device br0 is. I do have my Brother wireless printer connected to the DIR-655 but it's device name is BRW0022581FB096. I was wireless at the time of connection problem, and the wired computer connected to the DIR-655 had been off.
I have a Wireless-G USB Compact USB Network Adapter (WUSB54GC V1.0). Running XP. How do I set Promiscuous mode for this adapter?
View 1 Replies View RelatedTo set up AnyConnect on my ASA5505? I have my VPN access working properly through the Cisco client however I want to be able to use the clientless program as well that is available.
View 1 Replies View RelatedASA 5505 Sec plus lic w/OS 9.1
I want to setup a quick and simple VPN server on my ASA. I want to do local authentication and, once authenticated, I want to allow all internal access. I only have 1 WAN IP. I'm finding a ton of conflicting info online. The ASA is already setup and is operational. I just need the correct commands to setup the VPN.
There is so much mis-information on the Internet and Cisco's own support site has bits and pieces everywhere (I've found at least 5 support pages in Cisco that address this subject), none work or are directly targeted at what I would consider is a major use case for this product. I can see from the many posts everywhere that getting L2TP/IPSEC to work is a major problem, requiring many configuration steps that all have to be perfect and there seems to be some trick to get it to work that most people struggle with. Most of the advice out there is impertinent and highly technical but doesn't work.
I would like to know if there is any consolidated instructions that WORK to create a VPN server on the 5505 using the ASDM and also how to set your Windows 7 (or 2008) client to work with it.
Like I've said, I've spent hours and hours on this and have yet to get anything to work. I have a brand new 5505 connected directly to DSL (static IP) that I ran the wizard on and followed the best advice I could find (by the way there's TONS of information on getting XP to work but afaik, this does NOT work for windows 7). Now that I've tried various things without success, I believe I've gotten it so fouled up I need to reset to factory defaults and start over.
I also have another brand new 5505 connected to a different DSL line. Behind that firewall, I have both windows 7 clients and windows 2008 server. I've tried lots of different things to get these to work including the registry hacks (which, if indeed is required, I seriously can't believe that Cisco hasn't given us a tool for).
I have tried to use the ASDM to do all my programming as I find the CLI to be extremely error prone and virtually incomprehensible.So, what the world needs is one place that gives all the instructions on what to do, step-by-step that really work for this simple use case of windows connecting to the ASA.
I have an ASA 5505 configured using easy VPN connecting to our corporate ASA. The ASA5505 is configured for network extension mode with a routable subnet. The clients that hang off the ASA 5505 are DHCP and get their IP address and DNS settings from the ASA 5505. I have a split tunnel setup, so only certain networks go over the tunnel back to corporate. Local Internet browsing goes out the ASA 5505 to the ISP.
My questions is how to setup split-dns. i would like to have my clients query the ISP's DNS servers for Internet based websites and when they need to access the exchange server the query goes to our corporate DNS servers. I see a setting for DNS names under the group policy on the corporate ASA, but how does the client know which DNS server to use?
The clients receive a primary DNS server (ISP) and a secondary (Corporate DNS) from the ASA5505.
I have an ASA 5505 that I would like to use only as a VPN access device into my network. I am looking for the most secure setup.
Currently I have a router with 4 networks/subnets: DMZ, public, protected, perimeter. DMZ is public DNS and web, no access to any other subnets, only 80 and 53 from public. Perimeter is an edge email server, only port 25 allowed to the email server on the protected subnet. Protected is all internal servers and workstatoins, no access from any other subnet and limited access out to public.
Where would I place the VPN device?
I have been asked to setup a VPN on a stick setup so that people on the move can use the encryption of our SSL VPN for web browsing etc using Any Connect. This works fine, whats my ip shows the external IP of the office when connected to the VPN and all traffic is pushed down the pipe. The only issue is when connected I have no access to local resources such as IP printers etc. How to do this on 5505?
View 6 Replies View RelatedI have a new Cisco ASA 5505 which I am trying to just setup so that all computers on the LAN can get to the internet (browsing and ping). My current setup attached.
View 1 Replies View RelatedI have an ASA 5505 with a dynamic IP address from the ISP.What I need to accomplish is the following:
- Either setup that ASA (Dynamic IP)VPN with an IOS router (Static IP)
- Or setup that ASA (Dynamic IP) with another ASA (Static IP)
I need to setup a L2L vpn between two ASA 5505 model. but due to poor planning and documentation both sites has same subnet (192.168.1.0/24) now i need to set up L2L wtih overlapping subnets. is it possible with asa 5505?
View 1 Replies View RelatedI have a problem with a branch office setup, and I can't for the life of me think of what the problem is.I have a remote office setup, using an ASA 5505 that is set up to establish an easy vpn connection to the central network. The connection at the branch office is a 20/5 cable modem, the central network has a 25/25 fiber connection.
The issue I have is this. Wired clients work fine at this branch office, at least 95% of the time. I have a lightweight AP there that can come up and join the controllers at the central network, no problem. I haven't done anything with H-REAP because there are really no resources locally they need that would allow them to do their work, so all traffic is tunneled back to the WLC.
Wireless clients can authenticate to the AP, and I can get 15-20ms ping responses from them all day. Latency never comes close to the 600ms proposed limit with CAPWAP. Yet, for some reason the performance of the clients is problematic. Webpages will frequently not load correctly, they experience some freezing, and with one application we use - it refuses to load completely.If we bring these same computers to an AP connected to our central network, on the same SSID, they work flawlessly.
Something about this particular location is causing a lot of grief for our users.For what it's worth, we are running WCS 7.0.230.0 and the WLCs are on 7.0.116.0. The ASA is running a pretty basic configuration, pretty much out of the box with the easy vpn configuration entered.
I currently use MS ISA Server 2006 to protect a windows internal network, where there is also an MS Exchange server. I have acquired a Cisco 5510 to enhance security at main office. Later I will have ASA 5505 for branches, including VPN-ning. to have firewall at main office. I have several public IPs and would like to setup DMZ for Web, Exchange server and FTP. How do I setup interface and sub-interface for the DMZ?Can I continue using ISA Server connecting to Cisco 5510 on the perimeter? If so, How do I set the interfaces (and sub-interfaces) as well as NAT-ting and access configuration between the inside and outside?
View 12 Replies View RelatedI have setup a vpn connection at my remote offices with a 5505. At my main office I have a 5510.From my remote offices I can PING my Main office server. However when I go to set up a vpn connection through windows network and sharing center I can't seem to have the connection connect.....
View 15 Replies View RelatedI'm having trouble setting up a second IPSec VPN tunnel on my Cisco ASA 5505 to another office. I was able to setup the first one with no problem through the ASDM, but have not been able to get the second one up.The IPSec tunnel is connecting to a WRVS4400N router at the other office. I tried debugging crypto isakmp, and crypto ipsec, but I'm getting nothing. Below is the config. Does something look wrong on my end? I also attached a screenshot of the parameters setup on the remote router.
View 7 Replies View RelatedI have two 5505's facing each other over 10meg dsl internet links with slow up links, I think that the uplink is around 768K and down is 10meg.Behind each ASA on each end sits a pbx they are using H.323 point to point trunk for connectivity to talk to each other one the g.729 codec. I've read a little on Qos and I'm wondering if GRE over IPSecis the way to configure this setup. I'm needing recomendations. There are is no qos at present configured and its not working well at times. There are only 5 phones at the remote site and 5 computers. The remote end only supports 3 vlans as well. I'm new to ASA.
View 1 Replies View Relatedi need to configure a ASA 5505 in transparent mode.learned from Internet, my configuration is :
int e0/0 --- vlan 1---->nameif outside
int e0/4 --- vlan 2------> nameif inside
gloable ip is 172.17.104.10 255.255.255.0
http server enable
http 172.17.104.0 255.255.255.0 inside
when i connect the outside interface to one PC with ip addr 172.17.104.194 my PC connect to inside interface with ip 172.17.104.249 cannot ping each other even when i set rules as permit any any on both direction
I followed a few Youtube videos and replicated another ASA's VPN configuration through ASDM to create the Anyconnect VPN on the ASA 5505.
The problem is, after everything checked and triple checked, I still cannot get to https://external_IP. I can post configs if needed, but I really did replicate another ASA almost exactly.An online port scan shows my external IP as "not listening on port 443".However, when I run on the ASA :
I get the following (external IP changed to 123.123.123.123 for the forums):
Protocol Socket Local Address Foreign Address State
TCP 0004426f 192.168.8.4:22 0.0.0.0:* LISTEN
SSL 0574f7af 123.123.123.123:443 0.0.0.0:* LISTEN
DTLS 0577b0ef 123.123.123.123:443 0.0.0.0:* LISTEN
TCP 06fa8d1f 123.123.123.123:80 0.0.0.0:* LISTEN
SSL 079385bf 192.168.8.4:444 0.0.0.0:* LISTEN
So it does appear to be listening on the external IP on the outside interface correctly.I went ahead and tried the whole "change the ASDM port" as you can see from the inside interface being changed to 444 but management isn't even enabled on the outside interface so I'm not sure why it is acting this way.
The outside interface is plugged into a DSL modem. I don't think this DSL modem has any real intelligence, but I was going to disconnect the ASA and plug my laptop into the outside interface (on the same subnet) and then see if I could reach it. That was the only thing I could think of...that possibly the DSL modem was blocking the inbound traffic.
i want to setup a vpn connection between Cisco asa 5505 and centos server.
Here is my senerio:
ASA 5505
Public IP address 155.155.155.2
Local NETWORK : 192.168.6.X
Centos Server
------------------
Public ip address : 155.155.155.6
I have two 5505 ASA. I would like to know can I make two 5505 failover redundant with active standby setup?
View 11 Replies View RelatedI have a newly aquired asa 5505 that I just set up to the bare minimum configurations. I followed a cisco paper on how to create a "remote access vpn" setup for ipsec. I can sucessfully connect and establish a VPN, but when I try to access an inside resource from the vpn address, the asa blocks it.
Specific error is: Code...
I'm trying to set up a 5505 (running 8.3) so that i can use the client vpn through RADIUS authentication.I have set up a new local RAIDUS windows box and used the ASDM asistant and a few other guides to setup the 5505.
View 3 Replies View Relatedhow can I setup that the backup connection will start but after 30s of icmp timeout the default gateway (tracket object - 192.168.1.1)
My configuration:
sla monitor 123
type echo protocol ipIcmpEcho 192.168.1.1 interface outside
num-packets 3
frequency 10
sla monitor schedule 123 life forever start-time now
route outside 0.0.0.0 0.0.0.0 192.168.1.1 1 track 1
route backup 0.0.0.0 0.0.0.0 192.168.2.1 254
track 1 rtr 123 reachability
I am planning to imlpement an ASA 5505 in my home network and I am wondering if this is a valid configuration. I am wondering if it is necessary to have 3 separate internal subnets or if these can be cabeled together in a more efficient fashion?
I plan to keep the 2 servers (game, e-mail) branched off the ASA directly in a DMZ configuration. The rest of the clients connect through the wireless/wired router.
Any unforseen problems with a setup like this (Modem -> Firewall -> Internal Router)? I have read sites that say I will have to accept an IP via DHCP for the ASA's external interface.
I'm having trouble setting up the correct rules on an ASA 5505 I'm using in my home office. I have a couple of IP Cams I need to access remotely.
I've tried setting up simple NAT(PAT) and/or Access Rules, but it hasn't worked. I have a single dynamic IP for the Outside interface. Call it 77.76.88.10 and I am using PAT. The CAM is setup to connect on port 80, but could be configured if necessary. I've tried setting up NAT Rules using ASDM as follows:
Match Criteria: Original Packet
Source Intf = outside
Dest Intf = inside
[Code]....
I'm afraid to use CLI only because I am not confident I'll know how to remove changes if I make a mistake.
I have two ASA 5505's. One is currently setup as my firewall connected to the Cox Cable modem and wireless AP. I have another ASA that I would like to use, I have an idea that I could set that one up as a VPN unit, but not sure how I could do that. If that is not an option, can you provide the command line instructions on how to setup the VPN via the console cable. [code]
View 1 Replies View RelatedI have been using static NAT to map between a single server behind an ASA 5505 and a single public IP address. In other words, I've been doing this:
object network NAT_ME
nat (inside,outside) static interface
Now I would like to start using the clientless VPN feature of the ASA, so I of course don't want that particular port forwarded to the server. Is there a way to define such an exclusion? I've tried several things, including setting up a separate NAT rule to direct that port back to the ASA's interface, without luck.
If that is not possible, what configuration would I need to move to in order to get the behavior that I want? It is important that all (non-VPN) traffic is passed exactly as it arrives at the firewall (whether it is coming from internal or external), with the exception of changing the IP address (i.e., I need static port mappings for some of my services).
I have assigned a task to configure a vpn between windows 2008 server and cisco asa 5505, what kind of vpn should i go with as the windows 2008 server r2 is on cloud and is it possible to configure site-to-site vpn for this network senario or not.. i have try ikev1/ipsec remote access vpn with l2tp with (CHAP, MS-CHAP v2) and couldn't find any document which will allow me to configure windows 2008 server to behave a client and connect it to asa, well what i did is that i configured a dail-up connnect with l2tp and found the following debug message
Sep 09 20:04:02 [IKEv1 DEBUG]IP = 172.16.32.5, Oakley proposal is acceptable
Sep 09 20:04:02 [IKEv1 DEBUG]IP = 172.16.32.5, IKE SA Proposal # 1, Transform # 1 acceptable Matches global IKE entry # 1
[Code].....
I'm working on setting up a template configuration for the Cisco ASA 5505 device that we'll use to configure more routers for various client needs. One of the requirements requested of me is the following: Internal hosts assigned a DHCP address are blocked from the internet Internal hosts with a static IP are permitted access to internet All internal hosts can communicate regardless of state
Now, I'm fairly new to this and I'm certain my terminology isn't correct so googling the problem has been fruitless. I have followed basic configuration guides and have configured the device to hand out DHCP addresses to hosts plugged in ports 1-7. If I'm plugged in and specify my address manually in the OS I am blocked from any access so I can only assume there is an access policy or some rule preventing me from authenticating against the router despite having set up VLAN1 to be the entire class C subnet. What sort of steps would I need to do to configure this? New access lists. For the record, the dhcp addresses are in the range of 10.100.31.64-10.100.31.95. VPN users are assigned an address from 10.100.31.220-10.100.31.240 and there seems to be no issues with that configuraiton. I don't wish to constrain what addresses a user can use should they specify a static IP (10.100.31.5 should be just as valid as 10.100.31.100).