RE: Cisco >224.0/3 problems..

["Martin, Christian" <CMartin () mercury balink com>]

Did you try ip mroute?

RES-RTR6(config)#ip mroute 224.0.0.0 255.255.0.0 Null0
RES-RTR6(config)#no ip mroute 224.0.0.0 255.255.0.0 Null0
RES-RTR6(config)#^Z
RES-RTR6#
Feb  1 17:53:56 EST: %SYS-5-CONFIG_I: Configured from console by chris
on consol
e
RES-RTR6#
RES-RTR6#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
RES-RTR6(config)#no ip multicast-rou
RES-RTR6(config)#ip mroute ?
  A.B.C.D  Source address

RES-RTR6(config)#ip mroute 224.0.0.0 224.0.0.0 null 0
RES-RTR6(config)#ip multicast-rou
RES-RTR6(config)#no ip mroute 224.0.0.0 224.0.0.0 null0
RES-RTR6(config)#^Z
RES-RTR6#
      




> -----Original Message-----
> From: James Rishaw [mailto:jamie () dilbert ais net]
> Sent: Monday, February 01, 1999 2:07 PM
> To: nanog () merit edu
> Subject: Cisco >224.0/3 problems..
>
>
> Hello all,
>
>   Ran into a problem, thought maybe someone else has run into this and
> knows of a "fix", if this is intentional or what not.
>
>   It seems that Cisco IOS has a problem dealing with addresses above
> 224.0.0.0/3.
>
>   This came up in an e-mail with Paul Vixie about MAPS RBL, 
> where I asked
> him why 224+ wasn't filtered.  The reply was: IOS ignores it. 
>  GateD likes
> it, IOS doesn't.
>
>   I'm finding that IOS isn't propagating routes, etc., (nor 
> will it even
> seem to *recognize*) address space above 224.
>
>   To wit:
>
>
> As a /3:
> bordercore1.chi(config)#ip route 224.0.0.0 224.0.0.0 Null0
> %Invalid destination prefix
>
> /8, close to the end of address space:
> bordercore1.chi(config)#ip route 252.0.0.0 255.0.0.0 null0
> %Invalid destination prefix
>
> As a /24:
> bordercore1.chi(config)#ip route 225.0.0.0 255.255.255.0 Null0
> %Invalid destination prefix
>
> bordercore1.chi(config)#ip route 230.0.0.0 255.255.255.0 Null0
> %Invalid destination prefix
>
> It's not Null0:
>
> bordercore1.chi(config)#ip route 234.128.230.123 255.255.255.255 h9/0
> %Invalid destination prefix
>
> bordercore1.chi(config)#ip route 241.102.34.93 
> 255.255.255.255 atm4/0  
> %Invalid destination prefix
>
> I know this is all "multicast" space, but considering 
> classless routing
> and CIDR, shouldn't this space be usable and able to be manipulated ?
>
> -jamie
> -- 
> jamie rishaw (efnet:gavroche) @ AIS / Exodus
> "I want peace on earth and goodwill towards men."
> "We are the United States Government.  We don't do that sort 
> of thing."
>   --sneakers