Hi, I apologize if this isn't the best place to ask this question, but I'm hoping someone here can at least point me to the right direction. I don't even know if lt2pd is the right place to fix the problem I'm seeing, but I'm guessing that l2tpd and/or pppd are the most likely places to find a solution.
The question is: is there a configuration option somewhere on the server that I can use to specify the network address & subnet mask that the client will use when adding the vpn connection to its routing table? Background: After reading Jacco de Leeuw's great documentation at http://www.jacco2.dds.nl/networking/freeswan-l2tp.html, I have a working openswan/l2tp server running on Debian unstable (sid) using certificates for authentication. The clients are all Windows XP SP2 using the built-in vpn client. The problem I have is that the routing table on the client doesn't end up with the settings I'd like. When the client adds the vpn connection to its routing table, I want the subnet mask to be 255.255.255.0. However, if I leave the "use default gateway on remote network" option at the default "checked" setting in the advanced TCP/IP properties on the client, the client adds a 0.0.0.0/0 route at the top of the routing table, which makes all network traffic go through the vpn connection (definitely not what I want). If I turn off that setting, the client creates a route using a 255.255.0.0 mask, which is closer to what I want. If I manually change the routing table on the client, everything works exactly as I would like, but it would be better if that routing table manipulation wasn't necessary. Is there something else I can do to make it use a 255.255.255.0 subnet mask? Thanks for any help you can provide, even if it's just a pointer to another e-mail list! (RTFM responses are fine with me too, but it would be great if you can tell me which FM I should be reading.) -Kevin
