Well, there could be a server and a client. But I had thought we'd duplicate the setup for our library gateway. In which there is one machine tunneling everything on port 443 to the open internet gateway (your box). Then the users at the mtgs don't have to install the OpenVPN client to get it to work, they just set their gateway to the machine that has the OpenVPN client on it.
But maybe that is too agressive. Lets just get a client+server combo up and running first. The server can access the Library's WiFi. Ed Robert Citek wrote: > > On Sep 22, 2005, at 12:45 PM, Ed Howland wrote: > >> We could do OpenVPN internally with say three machines (two endpoints >> and a client) And just test it with HTTP:80. Then transfer that >> knowledge to an outside libary thing. > > > Yup. That's what I was thinking. First, get it to work. Then make > it work better. > > BTW, how do you envision the setup? Why three machines? I was > thinking just two: one server, one client. But admittedly I haven't > thought it all the way through, yet. > > Regards, > - Robert > http://www.cwelug.org/downloads > Help others get OpenSource software. Distribute FLOSS > for Windows, Linux, *BSD, and MacOS X with BitTorrent > > > _______________________________________________ > CWE-LUG mailing list > [email protected] > http://www.cwelug.org/ > http://www.cwelug.org/archives/ > http://www.cwelug.org/mailinglist/ -- Ed Howland WDT Solutions, LLC. [EMAIL PROTECTED] (314) 962-0766 _______________________________________________ CWE-LUG mailing list [email protected] http://www.cwelug.org/ http://www.cwelug.org/archives/ http://www.cwelug.org/mailinglist/
