1 |
Hi Grant, |
2 |
|
3 |
On Tue, Feb 12, 2008 at 5:41 AM, Grant <emailgrant@×××××.com> wrote: |
4 |
> I'm hoping to use the vpn in three few ways: |
5 |
> |
6 |
> 1. imap and smtp between my laptop and the mail server |
7 |
> 2. ssh from my laptop to the remote server |
8 |
> 3. cups printing from the remote server to the print server |
9 |
|
10 |
I don't think you need a VPN to SSH from your laptop to the remote |
11 |
server -- SSH is already encrypted. |
12 |
|
13 |
If your laptop is always behind your local firewall, then it should be |
14 |
sufficient to have an OpenVPN tunnel established between your local |
15 |
firewall/print server and your remote server. This should allow you to |
16 |
print. |
17 |
|
18 |
Configuring the routes on your laptop to go through your local |
19 |
firewall and VPN to the remote server should allow you to grab your |
20 |
mail. |
21 |
|
22 |
If you move around with your laptop then you'll need to establish the |
23 |
VPN tunnel to your remote server anytime you need to grab your mail |
24 |
from anywhere else but home (behind your local firewall). |
25 |
|
26 |
On Tue, Feb 12, 2008 at 5:53 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
27 |
> IMHO you should always go with routed first, then bridged if you need |
28 |
> it. |
29 |
> |
30 |
> Ask yourself this question: do you really need ethernet traffic to go |
31 |
> through the vpn? There are cases where it could be useful, but I'm hard |
32 |
> pressed to find a general case. |
33 |
> |
34 |
> With a routed vpn, you work with IP addresses, just like you do on the |
35 |
> internet. |
36 |
|
37 |
As Alan said, try going with routed first. |
38 |
|
39 |
Also, think about whether you really need this. As mentioned above, |
40 |
SSH doesn't need to be tunneled over a VPN. IMAP and SMTP can be |
41 |
encrypted too. That leaves printing, for which you could use VPN. |
42 |
|
43 |
Have fun! |
44 |
Mike |
45 |
-- |
46 |
gentoo-user@l.g.o mailing list |