Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I have some services running on my PC at home. It is behind a router, so it has a local ip, like 192.168.*.*. My router is registered at no-ip.com, so hopefully
I would like to connect to my pc from my workspace. It is a big company using proxy, so I cannot have direct connection.
Also I would like to have a secure connection.
Do you have any idea to realize it? Should I try VNC, ssh tunnel, or ?.
Generally you just need to set up a port forwarding rule in your home router to redirect any incoming requests on the desired port to the machine's local IP. You can use SSH, VNC, or any other services that listen on a dedicated port.
The network setup at your office typically doesn't matter unless you're trying to connect in reverse (home to work).
If the company is smart they disabled almost everything. I'd consider barracudaserver and use https. Every once in a while they offer it free.
As above you have to learn how to NAT your home modem/router. Some have a build in app that can connect to DDNS services and change dns name to ip when you dynamic ip changes. If not then you'd need a client at home to change no-ip's dns entry. Better to nat the ports to the box instead of that other setting. I forget that name, but it opens all outside ports to the internal lan.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
I think the "DMZ" in the NAT+router is supposed to open the box to the internet but my experience was that it didn't seem to work and I ended up forwarding the ports I needed to the machine on the LAN. You also need to reserve an IP address for the machine you'll be connecting to on the router.
One place I worked I couldn't even SSH on port 80 to my home box though (I tried non-standard and default) so ended up giving up and using my phone to connect to home instead.