Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello everyone, I'm looking at the best way so set up my VPN.
If I have multihomed firewall system with a DMZ (similar to the setup shown at www dot linuxjournal.com/article/4415), what is the best way to set up a VPN connection to my internal network?
The intuitive way would be to forward VPN traffic through the firewall to a VPN server on the internal net. However this seems to go against the whole DMZ philosophy.
The more correct way would be to have a VPN server running in the DMZ, but this would require some form of access to the internal network as well.
Ol;ong a similar line, is it more usual to open ssh access by ssh'ing to the DMZ and allowing a user to ssh from there to the internal network?
what is the best way to set up a VPN connection to my internal network?
it really depends on many things including your routing and firewalling administration skill, and the most important : finance and electricity.
Quote:
The intuitive way would be to forward VPN traffic through the firewall to a VPN server on the internal net. However this seems to go against the whole DMZ philosophy.
no not really. A DMZ not necessarily on a separate subnets than your internal - you can administer a bastion host using your firewalling skills - how a certain traffic from and to bastion host should not communicate with other host in the same subnet?
Quote:
The more correct way would be to have a VPN server running in the DMZ, but this would require some form of access to the internal network as well.
a DMZ best implementation is to have it on a separate subnet than your ordinary LAN - so it must route - from there you can define a better security parameter such as NAT or firewall rules etc.
Quote:
is it more usual to open ssh access by ssh'ing to the DMZ and allowing a user to ssh from there to the internal network?
SSH is only a protocol and operates in its own way - there are many other protocol that any applications need to operate in certain ways.
But assume my DMZ is a different subnet from my internal LAN, the question remains, should my multihomed firewall route VPN traffic via the DMZ or directly to the internal network?
The other thought I had - does it make more sense to allocate a public IP just for vpn.mydomain.com, put a dedicated firewall there and port it straight through to the internal network? Then I could use the same IP for extenal ssh access.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.