[c-nsp] Cisco 1700 as a vpn server

[Timothy Arnold]

Another alternative is to use 192.168.x addresses but I would need to
somehow add another static route as I have another network attached via
10.1.1.245 - unless I can make the vpn server the default route somehow?

Cheers
Tim


On Wed, 2005-02-23 at 23:52 +1300, Reuben Farrelly wrote:

> I am not certain but I *think* this might be just the way Windows clients 
> appear to handle VPDN type access.  I bet if you use a 192.168.0.0 address 
> you'll see a class C sized mask appear in the Windows routing table 
> instead, regardless of what mask you specify for your pool.
> 
> Having said that, it's not really a problem as the router will proxy-arp on 
> behalf of the client when contacting LAN IP addresses, and Windows will 
> forward anything not for itself even if on the same subnet, back to the 
> router going the other way.  It is a Point-To-Point type link, afterall.
> 
> Are you seeing any specific problem?
> 
> reuben
> 
> 
> 
> At 11:39 p.m. 23/02/2005, you wrote:
> >Hi,
> >
> >I have set-up a Cisco 1700 as a vpn server. Th fa interface has the
> >address 10.1.1.13/24
> >
> >I set-up a pool of 10 addresses from the 10.1.1.0/24 address space. The
> >client connects fine and gets an address, but the subnet mask is
> >255.0.0.0
> >
> >Any ideas?
> >Thanks
> >Tim.
> >
> >_______________________________________________
> >cisco-nsp mailing list  cisco-nsp at puck.nether.net
> >https://puck.nether.net/mailman/listinfo/cisco-nsp
> >archive at http://puck.nether.net/pipermail/cisco-nsp/
>