Search results for query: *

Alright, slowly but surely I'll get it. That makes sense and would only be logical. Anyway, thank you very much again!

I initially used the SDM and that is what assigned the acl to the internal interface. I have the config back, but I removed the acl from my LAN interface and added what was in 100 to the WAN acl. So if I assigned an inbound acl to my LAN interface would I have to mimic the inbound for it also...

Sadly I should have caught that, but thank you very much. One of these days I'll get it figured out. I have added that to the acl for my WAN interface and now I just have to get a good working outbound acl. I truly appreciate the help!

I would like to understand this more. I started from scratch and it works without any acl's at the moment or the IOS firewall enabled. Is the reason you are stating I need the route based policy due to the firewall or because of both the firewall and acl's?

You make a valid point. Thanks for pointing me in the right direction! Checking out docs on it now.

So could I remove that line and add ip route 10.65.10.0 0.0.0.0 xx.xx.xx.5 to get my traffic from internal out and then add another line to route what I need incoming into the 10.65.10.0 network? ex 128.2.0.0 255.255.0.0 10.65.10.10 ?

Correct I do not have any other route other than ip route 0.0.0.0 0.0.0.0 xx.xx.xx.5 going outside. What would I need to add then without opening up more than I need to?

That points to our gateway to the internet (which is another internal router to the outside world) which is working. That port is for teamspeak and if I try to connect to my 1841's outside IP it fails to connect stating it cannot see the server.

I have a cisco 1841 with 12.4 IOS with the advanced ip services. I am passing traffic from internal to external without issues. I have searched for a while without a solid solution to my issue. I am sure that those who know Cisco well will spot my mistake right away, but I clearly do not know...