In article < .com>,
<> wrote:
>Guys i've setup a static statement and believe i've put in the
>necessary access list to allow the required ports to be forwarded could
>you have a look over this and see if i've missed anything obvious
>PIX Version 6.3(4)
6.3(5)112 mitigates a security attack, but you might have to open
a case to get it.
>access-list inside_outbound_nat0_acl permit ip 192.168.100.0 255.255.252.0 192.168.91.0 255.255.255.0
>access-list inside_outbound_nat0_acl permit ip 192.168.100.0 255.255.252.0 192.168.92.0 255.255.255.0
>access-list inside_outbound_nat0_acl permit ip 192.168.100.0 255.255.252.0 192.168.200.0 255.255.248.0
So far that implies that 192.168.100.0 255.255.252.0 is internal and
192.168.91/24, 192.168.92/24, and 192.168.200.0 255.255.248.0 are outside
(or lower security)
>access-list inside_outbound_nat0_acl permit ip 192.100.20.0 255.255.255.0 192.168.200.0 255.255.248.0
>access-list inside_outbound_nat0_acl permit ip 192.100.20.0 255.255.255.0 192.168.92.0 255.255.255.0
>access-list inside_outbound_nat0_acl permit ip 192.100.20.0 255.255.255.0 192.168.91.0 255.255.255.0
Those have the same outside destinations but suggest 192.100.20.0 is
internal. 192.100.20/24 is *public* IP space (avenet.com)
>access-list inside_outbound_nat0_acl permit ip 192.168.100.0 255.255.252.0 192.100.21.0 255.255.255.0
Which suggests that 192.100.21/24 (Coalition for Networked Information)
is external
>access-list inside_outbound_nat0_acl permit ip 192.100.20.0 255.255.255.0 192.100.21.0 255.255.255.0
That's consistant, 192.100.20/24 internal, 192.100.21/24 external.
>ip address inside 192.168.102.33 255.255.252.0
>route inside 192.100.20.0 255.255.255.0 192.168.102.3 1
Again consistant, 192.168.100.0 255.255.252.0 and 192.100.20/24 internal.
But it just seems unlikely -- if you are the Coalition for Networked
Information of Washington DC, then why would you have a VPN to
Avnet Inc of Chandler Arizona??
>access-list out-acl permit tcp host xxx.xxx.xxx.105 any eq https
>access-list out-acl permit tcp any host xxx.xxx.xxx.105 eq https
>access-list out-acl permit tcp host xxx.xxx.xxx.105 any eq pptp
>access-list out-acl permit tcp any host xxx.xxx.xxx.105 eq pptp
>access-list out-acl permit tcp host xxx.xxx.xxx.105 any eq smtp
>access-list out-acl permit tcp any host xxx.xxx.xxx.105 eq smtp
>access-list out-acl permit tcp host xxx.xxx.xxx.105 any eq www
>access-list out-acl permit tcp any host xxx.xxx.xxx.105 eq www
I gather that xxx.xxx.xxx.105 is one of your public IPs. If so, then
get rid of all of the lines "permit tcp host".
You appear to be missing,
access-group out-acl in interface outside
>ip address outside xxx.xxx.xxx.109 255.255.255.240
>ip address inside 192.168.102.33 255.255.252.0
>ip address state 192.168.90.1 255.255.255.0
>ip local pool PPTP 192.168.91.1-192.168.91.254
>ip local pool IPSEC 192.168.92.1-192.168.92.254
>failover ip address outside xxx.xxx.xxx.108
>failover ip address inside 192.168.102.32
>failover ip address state 192.168.90.2
>failover link inside
You do not appear to do anything with the 'state' interface other than
set up failover for it?
>global (outside) 10 interface
>nat (inside) 0 access-list inside_outbound_nat0_acl
>nat (inside) 10 0.0.0.0 0.0.0.0 0 0
>static (inside,outside) xxx.xxx.xxx.105 192.168.101.93 netmask 255.255.255.255 0 0
>route outside 0.0.0.0 0.0.0.0 xxx.xxx.xxx.97 1
>route inside 192.100.20.0 255.255.255.0 192.168.102.3 1
>sysopt connection permit-ipsec
>sysopt connection permit-pptp
>crypto dynamic-map outside_dyn_map 20 match address outside_cryptomap_dyn_20
>crypto map outside_map 20 match address outside_cryptomap_20
>crypto map outside_map 40 match address outside_cryptomap_40
>crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
>crypto map outside_map interface outside
>isakmp enable outside
>isakmp policy 20 authentication pre-share
>isakmp policy 20 encryption des
>isakmp policy 20 hash md5
>isakmp policy 20 group 2
>isakmp policy 20 lifetime 86400
DES MD5 is more often group 1; you might want to add another policy
with a higher policy number to support that case.
>vpngroup VPN address-pool IPSEC
>vpngroup VPN split-tunnel VPN_splitTunnelAcl
>vpdn group 1 accept dialin pptp
>vpdn group 1 client configuration address local PPTP
>vpdn enable outside
|