Lately we discovered that Windows 7, Cisco IPsec VPNs and buildin UMTS Cards, also called WWAN Cards, do not work togehter. So we are now going the next step to the Cisco AnyConnect on the ASA Platform.
Here the snipplet from the release notes:
Support for Windows 7 on x64 (64-bit). This release, however, does not support WWAN devices (also called wireless data cards) on Windows 7 x86 (32-bit) and x64.
How to setup a Simple FCIP Tunnel with the Cisco MDS9222i
FCIP (Fibre Channel over IP) is a power full technologie for linking Fiber Channel based storage networks over IP network. We use this to link our mainframe with a second tape library in a different location, aprox 40 km.
Those days we faced the problem that we recived a mail with approx 150 recipients. Somewhere in the communication it seams that a mail address is broken by the asa.
On the Outside of the ASA you see following in the trace:
Inside E-Mail Server (Blue) mail.example.comOutside E-Mail Server (Red) mail.asdf.com220-mail.example.com ESMTP Server [Wed, 18 Aug 2010 10:30:58 +0200]220-Ready to recycle your bits, but we don't want220 your unsolicited or bulk e-mail (ie: spam)EHLO mail.asdf.com250-mail.example.com Hello mail.asdf.com [192.168.0.1]250-SIZE 4194304250-PIPELINING250-AUTH PLAIN LOGIN CRAM-MD5 NTLM250-STARTTLS250 HELPMAIL FROM:<asdf@asdf.com> SIZE=42157RCPT TO:<user1@example.com><output omited>RCPT TO:<user20@example.com>RCPT TO:<user21@250 OKexample.com>RCPT TO:<user22@example.com>RCPT TO:<user23@example.com>RCPT TO:<user24@example.com><output omited>250 Accepted<output omited>250 Accepted501 <user21@XXXXXXXXXXXXXX: '>' missing at end of address250 Accepted250 Accepted250 Accepted
On the Inside of the ASA you see following in the trace:
Inside E-Mail Server (Blue) mail.example.comOutside E-Mail Server (Red) mail.asdf.com220-mail.example.com ESMTP Server [Wed, 18 Aug 2010 10:30:58 +0200]220-Ready to recycle your bits, but we don't want220 your unsolicited or bulk e-mail (ie: spam)EHLO mail.asdf.com250-mail.example.com Hello mail.asdf.com [192.168.0.1]250-SIZE 4194304250-PIPELINING250-AUTH PLAIN LOGIN CRAM-MD5 NTLM250-STARTTLS250 HELPMAIL FROM:<asdf@asdf.com> SIZE=42157RCPT TO:<user1@example.com><output omited>RCPT TO:<user20@example.com>RCPT TO:<user21@250 OKXXXXXXXXXXXXXXRCPT TO:<user22@example.com>RCPT TO:<user23@example.com>RCPT TO:<user24@example.com><output omited>250 Accepted<output omited>250 Accepted501 <user21@XXXXXXXXXXXXXX: '>' missing at end of address250 Accepted250 Accepted250 Accepted
This is a little bit strange so i will ask the Guys from Cisco if this is a known feature or a bug.
For the Momemt we have disabled the esmtp fixup, on monday we will do future analysis.
If you feel this helps a bit or may be not ? Please leave a comment.
How to use Tacacs+ on Cisco ASA for Shell and Web Authentication
Assume the Tacacs+ Servers are:
Cisco ACS Server 1
10.120.10.11
Cisco ACS Server 2
10.120.10.12
[sourcecode gutter=”false” autolinks=”false”]
aaa-server AAA-TACACS+ protocol tacacs+
!
aaa-server AAA-TACACS+ (Management) host 10.120.10.11
key YYYYXXXYYY
!
aaa-server AAA-TACACS+ (Management) host 10.120.10.12
key YYYYXXXYYY
!
! Delete the old local only configuration
no aaa authentication http console LOCAL
no aaa authentication ssh console LOCAL
!
aaa authentication http console AAA-TACACS+ LOCAL
aaa authentication ssh console AAA-TACACS+ LOCAL
aaa authentication enable console AAA-TACACS+ LOCAL
aaa authorization command AAA-TACACS+ LOCAL
!
[/sourcecode] If you have allready configured aaa for the ssh you might see something like
[sourcecode autolinks=”false” gutter=”false” highlight=”2″]
asa1(config)# aaa authentication ssh console AAA-TACACS+ LOCAL
Range already exists.
[/sourcecode]
Then you must first disable the aaa authentication and than add the new settings.
[sourcecode autolinks=”false” gutter=”false”]
no aaa authentication ssh console LOCAL
aaa authentication ssh console AAA-TACACS+ LOCAL
[/sourcecode]
If you feel this helps a bit or may be not ? Please leave a comment.
We recently bought so new Firewalls to replace to aged Cisco PIX515e with some new Gear. We decided to use Ciscos new Firewall flagship the Cisco ASA Devices. Everything was fine after the replacement, we transfered the configuration from the old boxes to the new with the help of the Cisco Security Manager.
Later that day there was complains about e-mails are not delivered properly.
On the Cisco PIX with Software 6.2 we had implemented following:
no fixup smtp
For the ASA5510 we had to implement following
policy-map type inspect esmtp esmtp_pmap
parameters
allow-tls action log
policy-map global_policy
class inspection_default
no inspect esmtp
inspect esmtp esmtp_pmap
exit
exit
If you feel this helps a bit or may be not ? Please leave a comment.
Access-based Enumeration (ABE) is a smart feature to let users see only the folders they have access to.
But if you have Cisco WAAS deployed in your network please be aware you have to add a Dynamic share to the waas configuration so the waas knows about this.
—– EDIT BEGIN —–
2010-09-17 We found out the Hardway you have to add the System to the AD. So i will show the Story in a new Post:-) Stay tuned, guys.
—– EDIT END ——-
Cisco Wide Area Application Services Configuration Guide (Software Version 4.1.7)
Step 1
For creating a dynamic share you have to add a Domain to the Cental Manager eg “Dynamic Shares”
Step 2
Create a entry under the dynamic shares in the global configuration.
On the WAE CLI
ToBe Done
If you feel this helps a bit or may be not ? Please leave a comment.
If you want to configure tacacs+ on the Cisoc MDS9222i Series you have to enable first the feature.
[sourcecode autolinks=”false” gutter=”false”]
feature tacacs+
[/sourcecode]
After this the commands to configure the Tacacs+ are available.
[sourcecode autolinks=”false” gutter=”false”]
feature tacacs+
!
tacacs+ distribute
tacacs-server timeout 10
tacacs-server host 10.0.243.247 key 0 secertkey
tacacs-server host 10.0.243.248 key 0 secretkey
tacacs+ commit
!
aaa group server tacacs+ AAA-Servers
server 10.0.243.247
server 10.0.243.248
deadtime 5
!
aaa authentication login default group AAA-Servers
aaa authentication login console local
aaa authentication login error-enable
!
ip route 10.0.243.247 255.255.255.255 10.0.160.1 interface mgmt0
ip route 10.0.243.248 255.255.255.255 10.0.160.1 interface mgmt0
!
interface mgmt0
ip address 10.0.160.99 255.255.255.0
switchport description Management
switchport speed 100
[/sourcecode]
On the ACS side you have to configure the shell profile with the following role:
[sourcecode autolinks=”false” gutter=”false”]
shell:roles="network-admin"
[/sourcecode] If you feel this helps a bit or may be not ? Please leave a comment.
