Unoffical empeg BBS

Quick Links: Empeg FAQ | RioCar.Org | Hijack | BigDisk Builder | jEmplode | emphatic
Repairs: Repairs

Topic Options
#298839 - 31/05/2007 12:53 Cisco ASA 5510 firewall and traceroute
wfaulk
carpal tunnel

Registered: 25/12/2000
Posts: 16706
Loc: Raleigh, NC US
Does anyone have enough familiarity with the Cisco ASA 5500 series firewalls to tell me how to configure it so that I can traceroute (and ping, for that matter) from inside the firewall to the Internet? My current outgoing policy is to allow all traffic from inside to out. I have the feeling that part of the problem may be that the replies to the pings and traceroute packets aren't being mapped back to the inside IP address properly (or at all), but, as much as I hate Cisco firewalls, I find it hard to believe that it cannot do what a $25 home firewall can do.
_________________________
Bitt Faulk

Top
#298840 - 31/05/2007 13:10 Re: Cisco ASA 5510 firewall and traceroute [Re: wfaulk]
oliver
addict

Registered: 02/04/2002
Posts: 691
I think you'd want something like this...

access-list 101 permit icmp any any echo-reply
access-list 101 permit icmp any any source-quench
access-list 101 permit icmp any any unreachable
access-list 101 permit icmp any any time-exceeded
access-group 101 in interface outside
_________________________
Oliver mk1 30gb: 129 | mk2a 30gb: 040104126

Top
#298841 - 31/05/2007 14:38 Re: Cisco ASA 5510 firewall and traceroute [Re: oliver]
wfaulk
carpal tunnel

Registered: 25/12/2000
Posts: 16706
Loc: Raleigh, NC US
Ah. I needed an incoming rule. Gotcha. I figured that since it had to map the incoming packet back to the original NATted host that it would be implicit. After all, I don't have to havin incoming rules for other reply packets. Then again, TCP does open a VC, and I don't know if I'd have to do the same thing for UDP replies.

Regardless, it worked. Thanks muchly.
_________________________
Bitt Faulk

Top