[pptp-server] problem with routing table on client

[Reply To List Only]

I thought the answer to this a while back was that Microsoft always gave
out an assumed netmask based on IP Classes.  186.x.y.z is from class A
space, and the server has given you a Class A netmask.

If you have any dynamic routing protocols implemented, ie RIP or
something more intelligent, you'll be automatically receiving receiving
routing table entries for local subnets.  These routing entries will be
more specific than your 186.0.0.0/8, so your gateway/VPN box should
choose then over your 186/8, yielding a more logical route to those
advertised subnets.

Does your 8-bit mask become a 24-bit mask when using IP pools from
182.168.x.0 for the PPTP IPs?

Allan


bao wrote:
> 
> Good day everyone,
> 
> I'm using RH7.3, kernel 2.4.18-3 with ppp-mppe 2.4.1-6 (rpm version) and
> pptpd 1.1.2-2. Everything works great
> except one little problem. Our network is 186.200.127.160-191. When VPN
> is up, I check the client side routing
> table and see an entry similar to this:
> 186.0.0.0    255.0.0.0    186.200.127.187    186.200.127.187    1
> 
> I have seen discussions about Microsoft always giving the wrong subnet
> mask (i.e., 255.0.0.0).
> But with this huge subnet 186.0.0.0 instead of 186.200.127.0 (desirably
> 186.200.127.160 and subnet mask
> 255.255.255.224), there is possibly a huge amount of traffic going
> to/from this huge network. And all of it
> will be blocked by the firewall on the pptp server.
> 
> Is there any work-around that anyone has known of?
> 
> Thanks for any help
> 
> _______________________________________________
> pptp-server maillist  -  pptp-server at lists.schulte.org
> http://lists.schulte.org/mailman/listinfo/pptp-server
> --- To unsubscribe, go to the url just above this line. --