Is it safe to NAT to the TCP/IP printer on the appropriate port in the router? Will I get unwanted documents from hackers or is this not a huge problem?
Keep in mind that even printer firmware (presuming it's a printer and not a print server like CUPS) has security vulnerabilities. There have been reports of printers getting 'bots installed on them. You may get random messages from people, much like junk-fax.
If you can run ssh (and Linux et al.) you can set up a VPN. You could also consider OpenVPN or IPSec. However, for small and especially ad hoc deployments ...
OpenSSH version 4.3 and later supports a VPN tunnel feature. So you can start your
Once you've established such a tunnel you should be able to securely access your printer, your file shares, your e-mail, internal web interaces, etc. through that tunnel.
Eventually I'll write up a proper HOWTO on this (most of those I found on the 'net are missing some details). Also I'll want to fiddle with some of them get get it running as non-root and put a wrapper around it to automatically restart things on disconnect, etc. But here's some basic notes.
I'm assuming your running Linux ... Debian or Ubuntu. (Should work under any newer distro, and probably is a little easier for RHEL/CentOS or Novell since I think those will have the
(NOTE: there are details for doing this using a restricted access key, adding said restrictions to the end of the key in the
... and you should now have a working VPN tunnel. The
Note: to access other systems behind $VPNGATE you'll have to ensure that those systems know about your 172.31.. (VPN) routes (at least their default routers should have static routes pointing to $VPNGATE ... for the return trips, of course. Alternatively you could perform NAT on $VPNGATE so that all your remote/laptop traffic "looks like" traffic from $VPNGATE to the rest of your network. Either way, you'll also have to
As you can see this is a very rough outline and I have to figure out a few more details for my own usage.