But I usually get a good response when I post under this alias. I shall
post again.
To start from the top I have configured a superscope on my network to
contain 192.168.48.x and 192.168.47.x because I started running out of
addresses in my poorly configured DHCP pool on the 192.168.48.x network.
When someone grabs an IP from the 47.x network all is well and it can
communicate with everything on the 48.x network.
I have setup a VPN server and now when someone grabs an IP from the 47.x
network they have no idea about how to get to the 48.x network. That is,
unless the client has the "use default gateway on remote network" then there
is a default route for all traffic. This isn't what I want, though. The
client must use their own connection to surf the internet because of
bandwidth constraints.
My question is how do I give the client a static route to reach the 48.x
network if they grab a 47.x address?
My situation is similar to a off-subnet situation. Maybe I am doing
something wrong in the 47.x subnet child-scope. Would it be safe to play
with option 249 in there? Or would that muck up my local users? How can I
selectively give static routes to certain people (sorry for the typing out
loud).
I will buy a beer (or six) for the person that has a good solution for this
TIA...
-Steven-