Hi, the subnet in /29 is actually from 216.24.2.0 to 216.24.2.7 which includes 216.24.2.4 (basically an host of an /29 subnet).
If you want to include 216.24.2.8 also you should consider a bigger subnet (/28 for example) that will include 216.24.2.0 - 216.24.2.15. the right subnet may be : 216.24.2.0/*28* On 6 October 2011 21:34, Gregori Parker <[email protected]> wrote: > Try: > > ip route 216.24.2.0 255.255.255.248 216.24.0.54 > > > Router is complaining because your /29 cant have a base address of .4 > > > On 10/6/11 12:22 PM, "Joseph Mays" <[email protected]> wrote: > > >It feels strange to be asking a question about something as simple as a > >subnet here, but I'm honestly not sure what's going on in this case. > >Probably something simple. > > > >As you can see from the following set of commands, the router is fine > >with breaking the following addresses up into /30's, but not fine with > >the aggregate of the two routes into a /29. > > > >gw1.armplc(config)#ip route 216.24.2.4 255.255.255.252 216.24.0.54 > >gw1.armplc(config)#no ip route 216.24.2.4 255.255.255.252 216.24.0.54 > >gw1.armplc(config)#ip route 216.24.2.8 255.255.255.252 216.24.0.54 > >gw1.armplc(config)#no ip route 216.24.2.8 255.255.255.252 216.24.0.54 > >gw1.armplc(config)#ip route 216.24.2.4 255.255.255.248 216.24.0.54 > >%Inconsistent address and mask > > > >_______________________________________________ > >cisco-nsp mailing list [email protected] > >https://puck.nether.net/mailman/listinfo/cisco-nsp > >archive at http://puck.nether.net/pipermail/cisco-nsp/ > > > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > -- Mohamed Touré 06 38 62 99 07 _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
