On 11/14/2012 07:23 PM, Marc Chamberlin wrote:
On 11/9/2012 6:17 PM, Cristian Rodríguez wrote:
El 09/11/12 05:46, Marc Chamberlin escribió:
computername IN A IPAddress:port
No, no.. the domain name system does not understand ports in that way.. Thanks Cristian, yes I understand this will not work, it was just the concept that I was after....
You need to setup an openVPN server in your network, see http://www.shorewall.net/OPENVPN.html I am in the process of grokking VPN (openVPN) and believe it may be the right answer. But it is a complicated solution and not one that I will be able to easily explain to others on how to set up. I think I have it set up and working for my own laptop, but it is not easy to test unless I am outside of my own internal network, so progress is slow....
I took a brief look at shorewall, but so far have avoided using it as I would like to stay within the supported utilities provided by openSuSE.
My understanding is if a package is in the official distribution than it is supported and in shorewall case it is part of 12.2 hence it is supported if there is a bug. If you mean Yast support then the answer is no shorewall does not have yast integration and it is very unlikely it will have Yast support in the future.
Perhaps you can explain what is the difference between using shorewall and SuSEFirewall2? I have long been using SuSEFirewall2 to configure my
Susefirewall is easy to configure for simple tasks, shorewall is more advanced in its configuration. But at the end they both are front ends to iptables. One simple example is using multiple internet providers. Configuring by SuSEFirewall2 means using the custom script and that configuration is not easy. On the other hand achieving such a configuration with shorewall is not so complicated.
firewall, (which I believe in turn configures iptables underneath the covers) and yes it does have it's warts and bugs but as least I know what to avoid, for the most part (such as using YaST2->Security and Users->Firewall to configure it!).... Not sure I want to learn another tool unless there is a real advantage to doing so... Is there insofar as openVNP is concerned?
Shorewall comes with really good documentation and if you follow the guides then configuring your firewall is not that difficult. Having said that ,if you read the documentation Cristian pointed out you should be able to come out with a solution for SuSEfirewall2 also. Togan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org