07-27-2005 11:10 PM - edited 03-09-2019 11:58 AM
When doing remote access VPN. T
he ip pool is defined as 192.168.0.0 - 192.168.0.10
After initiating the session the client receives 192.168.0.0 and assigned.
Communication is happening.
Any valid reasons.
07-28-2005 07:34 AM
ip subnet-zero
07-28-2005 08:08 AM
The restriction that normally makes 192.168.0.0 an invalid address is based on assumptions about communicating in a LAN environment and the subnetting process that supports that communication. With VPN and other technologies that implement point to point communications and supply peer addresses from an address pool, there is really no reason why the "subnet address" should be avoided (and the restriction that usually makes 192.168.0.0 invalid is that it is the subnet address). 192.168.0.0 is just one address in the pool and there is no subnet to process. So the address is valid for VPN.
Having said that if I were configuring the VPN environment I would probably avoid having the zero address in the pool. I would have some concerns that some other devices might have code in their IP stack that would consider the 192.168.0.0 to be an invalid host address and might have difficulty in communicating with it.
HTH
Rick
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide