[ previous ] [ next ] [ threads ]
 
 From:  Chris Buechler <cbuechler at gmail dot com>
 To:  M0n0wall Dev List <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall-dev] /31 CIDR mask
 Date:  Sat, 8 Jan 2005 14:21:05 -0500
On Sat, 08 Jan 2005 00:15:41 -0500, Mykel <Mykel at mware dot ca> wrote:
> Chris Buechler wrote:
> 
> >/31 should really be removed from the selection drop downs, since it's
> >not a valid CIDR mask (well, 0 usable IP's in a /31 so it's pointless
> >to have).
> >
> >I know it uses a for...next type of thing to go from 1-32 (iirc) but
> >it really needs to exclude 31.
> >
> Why? I can get a /31 routed to from the ISP, if I *route* the 2 IPs as
> /32s, they're both usable. But why should I have to write twice the
> firewall rules?
> 
> And yes - we do this. Not on a daily basis, but there's a handful of
> clients we've done this for.
> 

For the firewall rules, it's fine, since that does comprise of two
IP's.  For the interfaces, it's not going to work if you assign a /31.
 I should have specified interface screens only.

-Chris