Hi, got a serverwit a public ip. I made a vpn with openswan, I made a virtual interface eth0:0 with ip 192.168.1.1. The vpn works(pinging, ssh login etc to 192.168.1.1) on my local network, when shorewall is not running. When shorewall is up pinging to 192.168.1.1 don''t goes, also ssh login. it will work on the public ip. The vpn is up and running and connects with no errors. On the server I opened ports 10000, 500, 22. I think I need to get eth0:0 in the interfaces file and create a new zone ''loc'' or something? but shorewall doesn''t like eth0:0 in the interfaces file. Could somebody help me Grts Bart ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
Bart Verstraete wrote:> Hi, > got a serverwit a public ip. > I made a vpn with openswan, I made a virtual interface eth0:0 with ip > 192.168.1.1. The vpn works(pinging, ssh login etc to 192.168.1.1) on my > local network, when shorewall is not running. When shorewall is up > pinging to 192.168.1.1 don''t goes, also ssh login. it will work on the > public ip. The vpn is up and running and connects with no errors. On the > server I opened ports 10000, 500, 22. > I think I need to get eth0:0 in the interfaces file and create a new > zone ''loc'' or something? but shorewall doesn''t like eth0:0 in the > interfaces file. > > Could somebody help mehttp://www.shorewall.net/IPSEC-2.6.html -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
Tom Eastep wrote:> Bart Verstraete wrote: >> Hi, >> got a serverwit a public ip. >> I made a vpn with openswan, I made a virtual interface eth0:0 with ip >> 192.168.1.1. The vpn works(pinging, ssh login etc to 192.168.1.1) on my >> local network, when shorewall is not running. When shorewall is up >> pinging to 192.168.1.1 don''t goes, also ssh login. it will work on the >> public ip. The vpn is up and running and connects with no errors. On the >> server I opened ports 10000, 500, 22. >> I think I need to get eth0:0 in the interfaces file and create a new >> zone ''loc'' or something? but shorewall doesn''t like eth0:0 in the >> interfaces file. >> >> Could somebody help me > > http://www.shorewall.net/IPSEC-2.6.htmlAnd you might also want to review http://www.shorewall.net/Shorewall_and_Aliased_Interfaces.html -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/