my windows vista vpn client interface receives an ip in: 192.168.50.0/24
and the server pushes a route to the local lan 192.168.5.0/24
In my windows vista (client) the user account does not have admin privileges and as a consequence the pushed route do not have effect.
A solution I think that would solve the problem is in the openvpn server is using TAP and do a bridge with the lan interface.
is there any other option?
-
This works equally well for Windows 7 (64bit). Maybe we can have the question's title changed to reflect that?– PaulJul 8, 2010 at 15:37
2 Answers
Give the user(s) "network operator" privs, this will allow the pushed route to work, but doesn't confer too much extra "power" :)
As far as I know, there's work being done to allow openvpn to run as a priviledged service, which should solve these issues. Not sure where that's got to. See this link also
-
-
1I believe he is suggesting you add the user to the 'Network Configuration Operators" local group. Sep 6, 2009 at 18:28
-
-
I just checked in this windows vista Home (PT) Portuguese version, this group does not exist as a local group. Checked using the 'NET LOCALGROUP' from the command line. I have upgrade the user permissions for this, or change the operative system to professional version. Thank you guys. Sep 7, 2009 at 14:51
-
Have added a URL to my post which details some further methods. I did presume you would be using XP Pro though. Sep 7, 2009 at 15:58
I did a different thing now.
I connected the server to the vpn network using the open vpn client as a service and now there is need to push this route because its virtual network adapter connects do the vpn and the clients can "talk" to each other.