[Shorewall-users] linux not accessible through VPN

mrmailer mrmailer at myway.com
Wed Dec 17 15:12:40 PST 2003

Well, I'd like to just disable shorewall for eth1.  Would sticking a # in front of the interface for eth1 in interfaces and putting a # in front of the rules for it, and restarting shorewall, disable shorewall firewalling for eth1 completely?

 --- On Wed 12/17, Tom Eastep < teastep at shorewall.net > wrote:
From: Tom Eastep [mailto: teastep at shorewall.net]
To: mrmailer at myway.com, shorewall-users at lists.shorewall.net
Date: Wed, 17 Dec 2003 11:15:16 -0800
Subject: Re: [Shorewall-users] linux not accessible through VPN

On Wednesday 17 December 2003 10:48 am, mrmailer wrote:<br>> Well, I don't think it's multiple zones, is it, at least not in the way<br>> specified on the page(192.168.x.? and 192.168.x+1.?), because to the linux<br>> machine, this should just appear as another local machine pinging it,<br>> right?<br><br>The article deals with routers/VPN servers in the local zone and goes on to <br>discuss when you need multiple zones, when you don't and options for <br>configuring those zones.<br><br>> I don't need the linux machine to be able to access the other <br>> machines through the vpn, only the linux machine to be accessible itself<br>> through the vpn, if that makes sense.<br>><br><br>Uh -- packets have to go in both directions; for the linux machine to be <br>accessible "through the VPN", the machines on the other end of the VPN must <br>be accessible from the linux machine. Does the Linux box have a route through <br>the VPN server to the remote system?<br><br>-Tom<br>-- <br>To
 m Eastep    \ Nothing is foolproof to a sufficiently talented fool<br>Shoreline,     \ http://shorewall.net<br>Washington USA  \ teastep at shorewall.net<br><br><br>

No banners. No pop-ups. No kidding.
Introducing My Way - http://www.myway.com

More information about the Shorewall-users mailing list