From: Greg Wendel (gwendel@gmail.com)
Date: Sun Jan 20 2008 - 04:59:27 ARST
You can also run into problems with /31 with DHCP. I was trying to setup
autoconfig of new devices using /31's but the Cisco DHCP pool would not
respond using this network. I dropped back to /30 and everything worked.
Cisco is aware of the risks of these special networks and that is why they
warn you when you enable /31's on a multiaccess interrface such as
fastethernet.
Thanks,
On Jan 19, 2008 8:07 AM, Farhan Anwar <farhan.anwar@gmail.com> wrote:
> Hi Guys,
> Just an off topic,
> On my way to exploring DocCD in the final days, every-time i read 31-Bit
> Prefixes in IP Addressing Section i got curious to lab it up and see how
> they work, finally i have tested them in 2 min scenario. There is no room
> for directed broadcasts as you can see only 2 addresses are there.
>
> R4 IP: 150.1.1.0/31
> R5 IP: 150.1.1.1/31
>
> Rack1R4#sh run inter s1/1
> Building configuration...
>
> Current configuration : 107 bytes
> !
> interface Serial1/1
> ip address 150.1.1.0 255.255.255.254
> serial restart-delay 0
> clock rate 64000
> end
> ---------------------------------------
>
> Rack1R5#sh run inter s1/1
> Building configuration...
>
> Current configuration : 89 bytes
> !
> interface Serial1/1
> ip address 150.1.1.1 255.255.255.254
> serial restart-delay 0
> end
>
> ---------------------------------------
>
> Rack1R5#ping 150.1.1.0
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 150.1.1.0, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 4/34/64 ms
> Rack1R5#
>
> --
> Farhan Anwar
> www.farhananwar.com
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
-- Gregory Wendel Springfield VA, 22153
This archive was generated by hypermail 2.1.4 : Fri Feb 01 2008 - 10:38:00 ARST