On Wed, 2011-07-06 at 13:16 -0600, José Roberto Alas wrote: > Greetings to all > > I need to redirect my ip public to private, I have: > > In file "nat": > No no eth0 200.30.178.2 10.5.xx
That clearly is not a valid /etc/shorewall/nat entry. Did you mean
200.30.178.2 eth0 10.5.xx no no
>
> In file "rules":
> ACCEPT net loc: 10.5.xx tcp 80 - 200.30.178.2
>
> In file "shorewall.conf"
> IP_FORWARDING=On
> IP_FORWARDING=On
>
> I have the output on eth0 to internet (200.30.178.1), with a public IP.
>
> The problem:
> When I consult the ip 200.30.178.2 I shows the output of apache
> firewall server, where it is installed shorewall, I do the NAT.
Where are you 'consulting' from? It must be from a system that connects
to your Firewall through eth0. It cannot be from a local system or from
the firewall itself.
-Tom
--
Tom Eastep \ When I die, I want to go like my Grandfather who
Shoreline, \ died peacefully in his sleep. Not screaming like
Washington, USA \ all of the passengers in his car
http://shorewall.net \________________________________________________
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
