Re: [fw-wiz] Problems logging deny's on Cisco Routers?

From: Luca Berra (bluca_at_comedia.it)
Date: 04/23/04

  • Next message: Bill Royds: "RE: [fw-wiz] Stanford break in"
    To: firewall-wizards@honor.icsalabs.com
    Date: Fri, 23 Apr 2004 23:04:51 +0200
    
    

    On Thu, Apr 22, 2004 at 04:21:00PM -0400, Manson, Jim wrote:
    >Scott,
    >
    >I know this is a late post, and you may have resolved this already, but try
    >adding a port range:
    >
    >deny ip any any range 0 65535 log

    ip protocol does not have notion of ports.

    L.

    -- 
    Luca Berra -- bluca@comedia.it
            Communication Media & Services S.r.l.
     /"\
     \ /     ASCII RIBBON CAMPAIGN
      X        AGAINST HTML MAIL
     / \
    _______________________________________________
    firewall-wizards mailing list
    firewall-wizards@honor.icsalabs.com
    http://honor.icsalabs.com/mailman/listinfo/firewall-wizards
    

  • Next message: Bill Royds: "RE: [fw-wiz] Stanford break in"

    Relevant Pages

    • Re: Allow Wimba Live Classroom via ISA 2004 on SBS 2003
      ... Maybe I can get it to work by defining the custom protocol with primary UDP ... If not a custom access rule, to what rule do I attach the custom protocol? ... Port Range From: 5998 To: 5998. ...
      (microsoft.public.windows.server.sbs)
    • Re: PC Anywhere Outbound
      ... > I have created a protocol in the Toolbox with the following information: ... Port Range = 5631-5632 ... Direction = Outbound ... > SECONDARY CONNECTIONS ...
      (microsoft.public.isa.vpn)
    • Re: PC Anywhere Outbound
      ... > I have created a protocol in the Toolbox with the following information: ... Port Range = 5631-5632 ... Direction = Outbound ... > SECONDARY CONNECTIONS ...
      (microsoft.public.isa.clients)
    • Re: PC Anywhere Outbound
      ... > I have created a protocol in the Toolbox with the following information: ... Port Range = 5631-5632 ... Direction = Outbound ... > SECONDARY CONNECTIONS ...
      (microsoft.public.isaserver)
    • Re: PC Anywhere Outbound
      ... > I have created a protocol in the Toolbox with the following information: ... Port Range = 5631-5632 ... Direction = Outbound ... > SECONDARY CONNECTIONS ...
      (microsoft.public.isa)