Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Version 8.2(1) and ASDM 6.2(1)%ASA-1-199010: Signal 11 caught in process/fiber (Unicorn Proxy Thread)/(unicorn-proxy) at address 0x3ed, corrective action at 0x9ff2340Yesterday I made a DNS change to move my VPN clients over from our vpn3k machines to...
So I have an ASA in a little abnormal setup.The site has a managed router far down stream and my only option for VPN is to have a static translated to my ASA.My ASA has only one interface plugged in, inside. Things seem to work great, I can ping thin...
I have a 3750-48-ps that I've had unplugged for a couple of months, went to plug it in yesterday and nothing happened... No lights or anything.Wondering if part of the AC part of the power supply went out I went and tried the DC connector, and nothin...
There are all kind of nice features regarding TCP port randomization, however with these new DNS problems starting I'm curious about UDP port randomization, for DNS especially.My internal recursive DNS servers were vulnerable to this new port randomi...
I have a bunch of attack requests not being logged by my asa-5550 version 7.2(4)On my web-server I see an attack:B.A.D.IP; HTTP/1.0 - [23/Jul/2008:11:37:30 -0700] GET /downloads/file/fid?;DECLARE%20@S%20CHAR(4000);SET%20@S=CAST(0x4445434C415245204054...
Wondering if you've resolved this?I've got an 8.2(1) box that behaves perfectly, but my new 8.2(2) box exhibits this exact behavior. I can log in with domain\username but if I don't specify the domain it implies machine\username and fails.
Didn't have anything to do with unicorn threads, did it?I had some reboots yesterday that I believe to be caused by VPN messages syncing between the active and primary machines, version 8.2(1). Did Cisco provide any recommendations?
You need to touch the router and the firewall. Below assumes everything is class C subnetted.In the router you will need a route:! ip route 192.168.3.0 255.255.255.0 10.24.112.254!Traffic will know how to get from the router to this network, which is...
