CONFIGURARE UN ROUTER ATLANTIS CON UN PIX 506E

[danielepaol]

Ciao a tutti e buon anno,
la Telecom mi ha aggiornato l' ADSL portandola a 6 Mbit quindi mi ha messo l' ADSL2 e con il precedente router (cisco 827) non mi veniva supportata e quindi ho messo in piedi un router Atlantis WebShare 141W ed infatti l' ADSL adesso va però non riesco a collegarci il Firewall 506E, qualcuno di voi saprebbe aiutarmi? Se volete vi posto la configurazione del firewall . . .
Grazie,
Daniele

[andrewp]

Posta un disegnino prima

[danielepaol]

ecco il disegnino del firewall

Password:
Type help or '?' for a list of available commands.
PIX> ena
Password: *********
PIX# wr t
Building configuration...
: Saved
:
PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 6YXTu4UWiWehCwt5 encrypted
passwd 6YXTu4UWiWehCwt5 encrypted
hostname CSD-PIX
domain-name pix.local
clock timezone CEST 1
clock summer-time CEDT recurring last Sun Mar 2:00 last Sun Oct 3:00
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol ils 389
fixup protocol pptp 1723
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
name 81.174.59.217 router-F5-Adsl
name 81.174.59.218 pix-outside
access-list acl_in permit icmp any any
access-list acl_in permit tcp any any
access-list acl_in permit udp any any
access-list acl_out permit icmp any any
access-list acl_out permit tcp any host
access-list acl_out permit tcp any host
access-list 100 permit ip 192.168.1.0 255.255.255.0 172.16.10.0 255.255.255.0
access-list 100 permit ip 192.168.1.0 255.255.255.0 192.168.20.0 255.255.255.0
access-list 110 permit ip 192.168.1.0 255.255.255.0 192.168.20.0 255.255.255.0
access-list tunnel-acl permit ip 192.168.1.0 255.255.255.0 172.16.10.0 255.255.255.0
pager lines 24
logging on
logging trap informational
logging facility 4
logging host inside 192.168.1.250
mtu outside 1500
mtu inside 1500
ip address outside pix-outside 255.255.255.248
ip address inside 192.168.1.254 255.255.255.0
ip verify reverse-path interface outside
ip audit info action alarm
ip audit attack action alarm
ip local pool pptp-pool 172.16.10.1-172.16.10.10
ip local pool luigi 172.16.10.26 mask 255.255.255.255
pdm location 192.168.1.0 255.255.255.0 inside
pdm location 172.16.10.0 255.255.255.0 outside
pdm location 192.168.1.252 255.255.255.255 inside
pdm location 192.168.1.250 255.255.255.255 inside
pdm history enable
arp timeout 14400
global (outside) 1 81.174.59.219
nat (inside) 0 access-list 100
nat (inside) 1 192.168.1.0 255.255.255.0 0 0
access-group acl_out in interface outside
access-group acl_in in interface inside
route outside 0.0.0.0 0.0.0.0 router-F5-Adsl 1
route inside 10.50.3.0 255.255.255.0 192.168.1.250 10
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server RADIUS (inside) host dc2 digital timeout 5
aaa-server LOCAL protocol local
http server enable
http 172.16.1.47 255.255.255.255 inside
http 192.168.1.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
sysopt connection permit-pptp
crypto ipsec transform-set myset esp-des esp-md5-hmac
crypto dynamic-map dynmap 30 set transform-set myset
crypto map newmap 10 ipsec-isakmp
crypto map newmap 10 match address 110
crypto map newmap 10 set peer 81.174.36.130
crypto map newmap 10 set transform-set myset
crypto map newmap 30 ipsec-isakmp dynamic dynmap
crypto map newmap interface outside
crypto map dynmap client configuration address initiate
crypto map dynmap client configuration address respond
crypto map dynmap client authentication RADIUS
isakmp enable outside
isakmp key ******** address 81.174.36.130 netmask 255.255.255.255
isakmp identity address
isakmp client configuration address-pool local pptp-pool outside
isakmp nat-traversal 20
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption des
isakmp policy 10 hash md5
isakmp policy 10 group 1
isakmp policy 10 lifetime 1000
isakmp policy 30 authentication pre-share
isakmp policy 30 encryption des
isakmp policy 30 hash md5
isakmp policy 30 group 2
isakmp policy 30 lifetime 86400
vpngroup wins-server idle-time 1800
vpngroup luigi address-pool luigi
vpngroup luigi dns-server dc2 csd2k
vpngroup luigi wins-server dc2 csd2k
vpngroup luigi default-domain retent.local
vpngroup luigi split-tunnel tunnel-acl
vpngroup luigi idle-time 1800
vpngroup luigi password ********
telnet 192.168.1.0 255.255.255.0 inside
telnet timeout 5
ssh 0.0.0.0 0.0.0.0 outside
ssh timeout 60
console timeout 10
vpdn group 1 accept dialin pptp
vpdn group 1 ppp authentication pap
vpdn group 1 ppp authentication chap
vpdn group 1 ppp authentication mschap
vpdn group 1 client configuration address local pptp-pool
vpdn group 1 client configuration dns csd2k csd2k
vpdn group 1 client configuration wins dc2 csd2k
vpdn group 1 client authentication aaa RADIUS
vpdn group 1 pptp echo 60
vpdn username luigi password *********
vpdn enable outside
terminal width 80

[andrewp]

Pensavi scherzassi quando ho chiesto un disegno?!

Comunque, mi pare di capire a spanne che prima aveva IP pubblico, ora devi creare tu una point 2 point router-firewall e poi una rete interna sull'inside.

[danielepaol]

Sorry . . . allora cerco di essere più chiaro: io ho un collegamento ADSL con la NGI e 8 indirizzi IP statici, il router ha un' indirizzo ip statico che è l' 81.174.59.217 e il firewall ne ha un' altro, quindi anche con questo router gli indirizzi IP sono sempre gli stessi.
Daniele

[Wizard]

Il concetto è questo:

int pubblica del router: ip della punto-punto
int interna del router: un ip pubblico del range utilizzabile

int outside pix: un ip pubblico del range utilizzabile
int inside pix: tua rete interna
default gateway pix: ip pubblico int interna del router
nat su ip int outside

[danielepaol]

Ciao Wizard,
sei stato chiarissimo, infatti questa mattina ho riconfigurato l' indirizzo IP inside e outside del router con quello pubblico del mio provider e poi ho ricollegato il firewall e adesso funziona tutto ad hoc.
Grazie mille per il vostro aiuto.
Daniele