BassTech Posted February 4, 2014 Posted February 4, 2014 (edited) Cut a long story short, I was setting up some new firewall rules yesterday for our BYOD system that's soon being installed. However, I have somehow managed to accidentally delete an existing rule, knocking our entire school offline. I have looked at the logs and it seems to be dropping packets out to the internet now, but I can't find out how to rectify it. I've attached some screenshots of our config. [ATTACH=CONFIG][/ATTACH] [ATTACH=CONFIG][/ATTACH] [ATTACH=CONFIG][/ATTACH] (Currently using mobile hotsopt) Edited February 4, 2014 by BassTech
seawolf Posted February 4, 2014 Posted February 4, 2014 Don't you have a config backup that you could restore on the firewall to get it back to a working state? If not, then big lesson learned for you. Configuration management begins with backing up your configs. It is clear from the logs that it is the firewall rule "OUTSIDE_access_out" that is causing the problem. I can't see a firewall rule with this name in your screenshots though. I do note that you have several "Ruckus-Squid" rules disabled. Are those deprecated rules or should they be active? p.s. I wouldn't recommend posting firewall screenshots showing all of your firewall rules including ports and IP addresses on the open net.
Willott Posted February 4, 2014 Posted February 4, 2014 From a brief look, it looks like the traffic being blocked on the log is DNS requests to some external servers - determine which internal IPs need to access which external IPs for DNS (I'd guess that you have AD and therefore your DCs probably do internal DNS and have forwarders for external - check IPs there), then I think you need a rule in the OUTSIDE outgoing rules (OUTSIDE_access_out would suggest interface OUTSIDE, on outgoing rules) to allow UDP 53 from your internal IPs requiring access to DNS to the external DNS servers set as forward lookup on your DNS servers. Doing that may then show other blocked packets - presently any web request is generating a DNS request which is being blocked, so any further traffic may be blocked, but difficult to know. If you only deleted one rule, it may have been an allow all external type rule, so now may be an opportune time to lock down. Cheers Will
cpjitservices Posted February 4, 2014 Posted February 4, 2014 Can you not issue a rollback ? not sure if this is an option on Cisco but on our Juniper Routers/Firewalls you can issue a rollback command, you can time it to so it will roll back for like 30 minutes and then commit it if it works. Which Cisco Firewall is this ?
FN-GM Posted February 4, 2014 Posted February 4, 2014 Not sure if it applies to ASA but on iOS switches you can just reload the device and it will restore the startup config. Unless you saved it.
BassTech Posted February 4, 2014 Author Posted February 4, 2014 Hi all, Managed to successfully re-create the rule and now all is well. Lesson learned I think, I should've backed it up first - amateur mistake! Thanks PS - Deleted firewall screenshots now too for obvious reasons.
FN-GM Posted February 4, 2014 Posted February 4, 2014 Hi all, Managed to successfully re-create the rule and now all is well. Lesson learned I think, I should've backed it up first - amateur mistake! Thanks PS - Deleted firewall screenshots now too for obvious reasons. I would backup anyway, just incase the whole device dies.
Willott Posted February 4, 2014 Posted February 4, 2014 Out of interest - what was the rule that you'd deleted?
BassTech Posted February 4, 2014 Author Posted February 4, 2014 I would backup anyway, just incase the whole device dies. I have done @Willott - the link between the two NICs allowing TCP/UDP traffic to pass between them. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now