| PLEX86 | ||
|
VPN and Fedora serverWin client 4276In researching the issue, I found this site: Which helps explain and set up OpenVPN using the bridged, as opposed to tunneled method. This sounds like the method I need to use, since while the VPN server will be on a Linux box, the client is using Windows and will need to see other Windows machines on the LAN. VPN and Fedora serverWin client 4277 For successful setting up of a VPN, you need pretty good understanding of IP network addressing and routing principles. You could start with Rusty's Guides from Don't... However, this site's instructions for setting up the bridge, refers to, although doesn't make direct reference (at least not to a simpleton like me) of having to make chandes to the SECOND NIC in the router-NAT. Here's my problem. Our network is like this: The parbreastioned T1 line comes in to a remotely managed router-NAT owned by the company that manages our phone lines and provides the Internet connection. We don't have access to this router's settings. We can call them and have a port forwarded, for example, but that's about it. The VPN server will be on a Fedora 2 machine that's behind this router, on the same switch as the rest of the machines on the LAN. VPN and Fedora serverWin client 4278 Tauno Voipio understanding Thanks, I'll give it a read! I see the other fellow's endorsing reply, so I look forward to taking the... How drastically is this going to change things? Our router manager has said they'll open and forward whatever ports we want on the router to an internal IP...but from what I'm reading on the site I linked above, that might not be good enough. Tips? Thanks! Liam
|
||||
VPN and Fedora serverWin client 4277 Linux groups from Newsgroups The #1 Usenet Provider on the Internet
|
||||