Welcome to Firewall.cx   Cisco Technical Knowledgebase
Modules
· Home
· Alternative Menu
· Amazon
· Cisco Decrypter
· Cisco Lab Partners
· Feedback
· Forums
· Max Arcade
· Private Messages
· Recommend Us
· Statistics
· Stories Archive
· Submit News
· Surveys
· Topics
· Web Links
· Your Account
 
Cisco Knowledgebase Articles
 
Site Info
Your IP: 38.107.191.113

Welcome, Anonymous
Nickname
Password

· Register
· Lost Password
Server Date/Time
8 September 2010 21:52:46 EEST (GMT +3)
 
Top Downloads
 
Gold Lab Partners


 
Firewall.cx: Forums

Firewall.cx :: View topic - Cisco ASA 5505 - Problem to access Internet from Inside host
Forums Home
Forum FAQ :: Search :: Memberlist :: Usergroups
Profile :: Log in to check your private messages :: Log in

View next topic
View previous topic
Post new topic   Reply to topic
Author Message
danny_lin
New Member
New Member


Joined: Jan 12, 2008
Posts: 3

PostPosted: Sat Jan 12, 2008 12:50 pm    Post subject: Cisco ASA 5505 - Problem to access Internet from Inside host Reply with quote

Hi All,

I have a problem to access Internet from inside host, even I have configured all neccessary ACL for the firewall. The internet connection is PPPoe (Wimax), and it can ping outside directly from the firewall, but if I tried to ping the outside url from inside host, it does not reply.

The following is my configuration of the firewall:
ASA Version 7.2(3)

!

hostname ciscoasa
domain-name default.domain.invalid
enable password [removed by smurf] encrypted
names
name 41.198.x.x outside_world description Internet Address
name 41.0.0.0 outside_network
!
interface Vlan1
nameif inside
security-level 100
ip address 192.168.2.1 255.255.255.0
!
interface Vlan2
nameif outside
security-level 0
pppoe client vpdn group Mweb
ip address pppoe setroute
!
interface Ethernet0/0
switchport access vlan 2
!
<--- More --->
interface Ethernet0/1
!
interface Ethernet0/2
!
interface Ethernet0/3
!
interface Ethernet0/4
!
interface Ethernet0/5
!
interface Ethernet0/6
!
interface Ethernet0/7
!
passwd [removed by smurf] encrypted
ftp mode passive
dns domain-lookup inside
dns domain-lookup outside
dns server-group DefaultDNS
name-server 196.47.x.x
name-server 196.47.x.x
domain-name default.domain.invalid
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
<--- More --->
object-group service AllowServices tcp
port-object eq ftp
port-object eq www
port-object eq https
port-object eq pop3
port-object eq ssh
object-group network ALLSERVERS
network-object host 192.168.2.10
network-object host 192.168.2.12
access-list inside_nat_static extended permit ip 192.168.2.0 255.255.255.0 host outside_world
access-list inside_access_in extended permit ip 192.168.2.0 s55.255.255.0 192.168.2.0 255.255.255.0
access-list inside_access_in extended permit icmp 192.168.2.0 255.255.255.0 host outside_world
access-list inside_access_in extended permit tcp interface outside interface inside
access-list inside_access_in extended permit tcp 192.168.2.0 255.255.255.0 host outside_world
access-list inside_access_in extended permit tcp interface inside interface inside
access-list aclin extended permit tcp interface outside object-group ALLSERVERS object-group AllowServices
access-list aclout extended permit tcp 192.168.2.0 255.255.255.0 object-group AllowServices interface outside
access-list aclout extended permit ip host outside_world any
access-list aclout extended permit udp 192.168.2.0 255.255.255.0 host outside_world
access-list aclout extended permit ip 192.168.2.0 255.255.255.0 host outside_world
access-list aclout extended permit tcp 192.168.2.0 255.255.255.0 any
pager lines 24
logging enable
logging asdm informational
<--- More --->
mtu inside 1500
mtu outside 1500
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-523.bin
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0
static (inside,outside) outside_network access-list aclout
access-group inside_access_in in interface inside
access-group aclout out interface inside
access-group aclin in interface outside
route outside 0.0.0.0 0.0.0.0 192.168.x.x 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout uauth 0:05:00 absolute
http server enable
http 192.168.2.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
telnet timeout 5
<--- More --->
ssh timeout 5
console timeout 0
vpdn group Mweb request dialout pppoe
vpdn group Mweb localname xxx
vpdn group Mweb ppp authentication chap
vpdn username xxx password *********
dhcpd auto_config outside
!
dhcpd address 192.168.2.2-192.168.2.129 inside
dhcpd enable inside
!
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
parameters
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
<--- More --->
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
inspect icmp
!
service-policy global_policy global
username lind password [removed by smurf] encrypted
prompt hostname context
Cryptochecksum:dc074ba17adb5edf4e91078e9eb8edff
: end

May anyone please check what could be the error with my configuration? I have tried to reconfigure the firewall for so many times since last year December, but without any success. Crying or Very sad

Thanks
Back to top
View user's profile Send private message
sp1k3tou
Occasional Member
Occasional Member


Joined: Jun 25, 2006
Posts: 65
Location: Buffalo, NY

PostPosted: Sun Jan 13, 2008 2:02 am    Post subject: Reply with quote

I have only configured the simple things on the ASA before, but I think your default route is what is making your inside host not be able to get out. What is the ip of your default gateway of your pppoe connection? Thats what your going to want to put in where you have 192.168.x.x You could also load ASDM and watch the firewall logs to see what is going on. If your not sure how to connect to ASDM here is your url for it on the inside https://192.168.2.1

route outside 0.0.0.0 0.0.0.0 192.168.x.x 1
Back to top
View user's profile Send private message
Smurf
Forum Moderator
Forum Moderator


Joined: Aug 10, 2006
Posts: 1387
Location: GT Manchester, UK

PostPosted: Sun Jan 13, 2008 3:56 pm    Post subject: Reply with quote

I think you need to remove the

Code:
route outside 0.0.0.0 0.0.0.0 192.168.x.x 1


The line
Code:
ip address pppoe setroute
(setroute at the end)

should be configuring the default route for you.

If you remove it and do a show route to see if there is a default route configured.

I have not really played with the ASA myself but i think this may be it.

Wayne
_________________
Wayne Murphy
Firewall.cx Team Member
www.firewall.cx

Now working for a Security Company called Sec-1 Ltd in the UK, for any
Penetration Testing work visit www.sec-1.com or PM me for details.
Back to top
View user's profile Send private message Visit poster's website
danny_lin
New Member
New Member


Joined: Jan 12, 2008
Posts: 3

PostPosted: Tue Jan 15, 2008 10:10 am    Post subject: Default route Reply with quote

I have configured without the default route before, and then it does not have a static route to the ISP when I do show route. The only problem is that only the interface outside can talk to dns server, but not the interface inside. The problem is that the interface inside cannot communicate to the interface outside. That's the only problem that I need to solve now, therefore I can access the Internet.
Back to top
View user's profile Send private message
Smurf
Forum Moderator
Forum Moderator


Joined: Aug 10, 2006
Posts: 1387
Location: GT Manchester, UK

PostPosted: Tue Jan 15, 2008 3:31 pm    Post subject: Reply with quote

Hi there,

Can you confirm, are you trying to ping the External interface from the Internal Interface (or viceversa) ?
_________________
Wayne Murphy
Firewall.cx Team Member
www.firewall.cx

Now working for a Security Company called Sec-1 Ltd in the UK, for any
Penetration Testing work visit www.sec-1.com or PM me for details.
Back to top
View user's profile Send private message Visit poster's website
danny_lin
New Member
New Member


Joined: Jan 12, 2008
Posts: 3

PostPosted: Wed Jan 16, 2008 10:20 am    Post subject: Reply with quote

I tried to ping the external interface from internal interface. Internal -> External. The packet is always deny by implicit ACL, when I did packet trace from ASDM.
Back to top
View user's profile Send private message
stefan0n
New Member
New Member


Joined: Mar 20, 2008
Posts: 1

PostPosted: Thu Mar 20, 2008 5:25 pm    Post subject: Reply with quote

any hint to solve danny question? I'm experiencing the same troubles with the asa 5505... Sad
Back to top
View user's profile Send private message
Display posts from previous:       
Post new topic   Reply to topic

View next topic
View previous topic
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum




smartDark Style © 2002 Smartor
Powered by phpBB © 2001, 2002 phpBB Group
 
Forums ©

© Copyright 2000-2010 Firewall.cx - All Rights Reserved

Copyright of all documents and images belonging to this site by Firewall.cx. Information contained on this site is copyrighted material.

It is illegal to copy or redistribute this information in any way without the written consent of Firewall.cx


Firewall.cx disclaims any responsibility for software and information obtained through this site or its links.


Page Generation: 0.65 Seconds