RE: [fw-wiz] ip classless?

From: Michael (topo2_at_pacbell.net)
Date: 04/26/03

  • Next message: Melson, Paul: "RE: [fw-wiz] Best practices for outsourcing firewall management"
    To: firewall-wizards@honor.icsalabs.com
    Date: Fri, 25 Apr 2003 22:16:57 -0700
    

    For one, ip classless (referring to CIDR) allows you to have access
    lists that are not based on classfull (i.e., A, B, and C) subnets (more
    preciseness). It also allows for more flexibility and specificity in
    allocating (subnetting) your address space. Not sure if that
    helps......

    -----Original Message-----
    From: firewall-wizards-admin@honor.icsalabs.com
    [mailto:firewall-wizards-admin@honor.icsalabs.com] On Behalf Of Behm,
    Jeffrey L.
    Sent: Friday, April 25, 2003 8:11 AM
    To: firewall-wizards@honor.icsalabs.com
    Subject: [fw-wiz] ip classless?

    I'm wondering, and perhaps this isn't the right forum, but...what are
    the
    *security* implications of changing "no ip classless" to "ip classless"
    in a
    Cisco Router IOS. The router is the perimeter router, between the DMZ
    and
    the Internet.

    I found http://www.networkking.net/out/IPClassless.php (a humorous, but
    informative read, thanks Bernard) which, to me, says, if you break a
    class
    into pieces, you have to tell the router about every single piece of the
    class, otherwise the router will simply drop packets to destinations (in
    that class) you haven't told the router about. However, the article in
    the
    above URL deals with RIP, whereas my case only deals with static
    routing.

    So, to extrapolate that out to just static routing, do the same rules
    apply?
    We are arguing that rather than having to specify how to route all the
    specific destinations in that class (some inside, but most out to the
    Internet), that one could just specify static routes (to those
    destinations
    we know are on inside) to the inside interface, and enable "ip
    classless"
    and let it direct the "other stuff" to the default route, i.e. out to
    the
    Internet.

    We feel more comfortable simply using multiple static routes to get that
    class routed correctly, so this question is mostly academic at this
    point. I
    guess the underlying problem we have is that just because we don't fully
    understand "ip classless" we feel *more* secure using static routes. The
    question is, do they accomplish exactly the same thing, or should we be
    paranoid regarding the "ip classless?" Could someone bounce packets
    off/through the router by having ip classless enabled, whereas they
    couldn't
    if it was disabled?

    Jeff
    _______________________________________________
    firewall-wizards mailing list
    firewall-wizards@honor.icsalabs.com
    http://honor.icsalabs.com/mailman/listinfo/firewall-wizards

    _______________________________________________
    firewall-wizards mailing list
    firewall-wizards@honor.icsalabs.com
    http://honor.icsalabs.com/mailman/listinfo/firewall-wizards


  • Next message: Melson, Paul: "RE: [fw-wiz] Best practices for outsourcing firewall management"

    Relevant Pages

    • Re: Totally different IPs on the same LAN?
      ... one of the IP subnets, then it would have to send packets targeted at ... matter that there's a quicker way that bypasses the router. ... static routes, though. ... which should also avoid the need for going through a router. ...
      (comp.dcom.lans.ethernet)
    • [fw-wiz] ip classless?
      ... Cisco Router IOS. ... Internet), that one could just specify static routes (to those destinations ... understand "ip classless" we feel *more* secure using static routes. ...
      (Firewall-Wizards)
    • Re: static routes
      ... when using static routes to specific subnets and the WAN ... redirect message and rearranges routes to use default router. ...
      (freebsd-net)
    • Re: Help configuring Point-To-Point T1
      ... that you could have a VLAN that spans across both offices? ... 1700 series router w/ Internet T1 ... 3560 Switch ... because you wouldn't have to worry about tons of static routes. ...
      (comp.dcom.sys.cisco)
    • Re: vpn probl
      ... If the VPN router is not the default router, ... > handeling the static routes so, when remote workstations need to ping ... > 172.16.x.x they go though Vpn remote router, and when they need to go ...
      (microsoft.public.windows.server.networking)