Apache X Iptables [RESOLVIDO]

1. Apache X Iptables [RESOLVIDO]

Marcelo Neves Ribeiro
sd_ribeiro

(usa Debian)

Enviado em 22/11/2010 - 18:37h

Olá!! Esse é o meu primeiro post, então vamos a minha dúvida.
Na empresa que trabalho me pediram para montar uma rede interna. Configurei a rede e os computadores conforme o esquema a seguir:

internet->rede da empresa(que distribui a internet para as seções)->firewall(iptables, que eu montei no ubuntu)->os computadores(são 24 pc's, tudo com windows xp).

Apenas um desses computadores está com windows server 2003, no qual instalei o apache+mysql+php+phpmyadmin manualmente.
O problema é que não consigo que outro pc com xp acesse as paginas em php que fiz para poder acessar o banco de dados da server 2003. Já futuquei na configuração do apache e não deu certo. Será as regras do iptables. Se alguém puder me ajudar.
Minhas regras.

#Compartilha a internet
modprobe iptable_nat
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -o eth0 -j MASQUERADE

#Politica Padrão
iptables -P INPUT DROP
iptables -P OUTPUT DROP
iptables -P FORWARD DROP

###Liberando acesso a web
iptables -A INPUT -i lo -j ACCEPT
iptables -A OUTPUT -o lo -j ACCEPT
iptables -A INPUT ! -i eth0 -j ACCEPT
iptables -A INPUT -i eth1 -j ACCEPT
iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A OUTPUT -m state --state ESTABLISHED,RELATED,NEW -j ACCEPT
iptables -A FORWARD -m state --state ESTABLISHED,RELATED,NEW -j ACCEPT

## Libera acesso ao servidor web na rede interna
iptables -A INPUT -p tcp --dport 80 -j ACCEPT
iptables -A OUTPUT -p tcp --sport 80 -j ACCEPT
iptables -A INPUT -p tcp --sport 80 -j ACCEPT
iptables -A OUTPUT -p tcp --dport 80 -j ACCEPT

## Libera ping na rede
iptables -A INPUT -s 192.168.0.0/24 -p icmp --icmp-type 8 -j ACCEPT

## Abre para rede local
iptables -A INPUT -p tcp --syn -s 192.168.0.0/255.255.255.0 -j ACCEPT

## Impede a abertura de novas conexões
iptables -A INPUT -p tcp --syn -j DROP

entre outras de proteção mas de acesso é isso ai. Se este estiver meio fraco ajude-me a melhorá-lo pois sou principiante em firewall e copiei este de vc's.


  


2. Re: Apache X Iptables [RESOLVIDO]

Renato Carneiro Pacheco
renato_pacheco

(usa Debian)

Enviado em 22/11/2010 - 21:51h

Vc tem certeza q copiou isso do site? Tem algumas coisas ae sem sentido. Exemplo, na linha abaixo:

## Impede a abertura de novas conexões
iptables -A INPUT -p tcp --syn -j DROP

Pra q isso se vc já colocou a política INPUT como DROP???

No seu caso, pra quem está começando, não comece com política tudo DROP, pois sempre falta algo pra liberar. Comece apenas com INPUT DROP e os outros deixe como ACCEPT. Quando vc acostumar-se mais com as regras e como os pacotes se comportam, dae vc passa a fechar mais o cerco.

Outra coisa q achei muito estranho: esse firewall é pra teste ou tá funcionando em produção? Se estiver em produção, a montagem da sua rede ficou estranha, pois vc num força nenhum tráfego a passar pelo firewall.

Mudando d assunto, se o seu firewall tá como gateway para outras máquinas, realmente o firewall pode estar atrapalhando. Não sei como está ligado esses computadores, mas as regras não me parecem estar certas. Teste-as colocando as políticas como ACCEPT (exceto a INPUT) e tente d novo.


3. Re: Apache X Iptables [RESOLVIDO]

Marcelo Neves Ribeiro
sd_ribeiro

(usa Debian)

Enviado em 23/11/2010 - 09:28h

Olá Renato obrigado por responder a minha dúvida. Rapaz eu fui copiando pedaços de script e colando no meu meio se compreender direito o que estava fazendo apenas testando e se funcionasse ia copiando outro pedaço. Na empresa o setor de informatica que possui firewall e servidor é que gerencia a rede e posssui varios setores. Eu tava tentando isolar a parte da rede do setor que trabalho do resto da rede, pois o pessoal podia acessar o computadores da minha seçao e o chefe queria impedir isso e pediu pra tentar fazer isso. Li varios tutoriais e script e fui testando como conseguir compatilhar a internet pelo firewall que configurei na nossa ”subrede ” fui testando outros scripts e colando, pelo que você falou fiz muita besteira, vou usar sua dica depois retorno. Grande abraço, Deus te abençõe.


4. Re: Apache X Iptables [RESOLVIDO]

Marcelo Neves Ribeiro
sd_ribeiro

(usa Debian)

Enviado em 29/11/2010 - 15:29h

desculpe a demora, mas andei atarefado. nao deu certo a dica do renato, nem colocando a politica ACCEPT. Qual será meu erro.
PS Só consigo pinga na maquina com windows server 2003, nas outras não consigo


5. Re: Apache X Iptables [RESOLVIDO]

Renato Carneiro Pacheco
renato_pacheco

(usa Debian)

Enviado em 29/11/2010 - 15:36h

Qual q é a faixa da rede da sua empresa?


6. Re: Apache X Iptables [RESOLVIDO]

Marcelo Neves Ribeiro
sd_ribeiro

(usa Debian)

Enviado em 08/12/2010 - 10:20h

Olá, estive viajando. Respondendo a pergunta sobre a faixa de rede da empresa: 10.200.X.X. Então para montar a sub rede, eu solicitei um IP fixo ao setor de informatica e eles me passaram 10.200.0.XXX que usei no firewall e compartilhei a internet com os outro pc's desta nova sub-rede que criei. Pois antes todo mundo que utiliza a internet acessava direto do setor de informatica com IP dinâmico, como já expliquei eu quero isolar da rede da empresa o setor onde trabalho, mas acessando a internet atraves do servidor da empresa.
Bom, vou exemplificar como ficou a estrutura da sub-rede:

INTERNET->REDE DA EMPRESA->SWITCH->FIREWALL(que configurei para isolar minha sub rede)->SWITCH->COMPUTADORES DO SETOR ONDE TRABALHO.

Em um destes computadores instalei o windows server 2003 que tambem possui o apache+mysql+php. No meu firewall tem duas placa de rede uma para internet e a outra a rede interna do meu setor com IP 192.168.0.1. O PC com o win server 2003 está com o ip 192.168.0.2, nele o apache roda direitinho, com sigo acessar o banco de dados pelas paginas que criei com php, só que quando tento acessa de outro pc da sub-rede não funciona, mas eu consigo pinga de outro pc. Até coloquei a política do iptables tudo ACCEPT, mas não deu certo. Vou mandar uma copia do httpd.conf do apache, para vc olhar se consigui diagnosticar algo de erra que possa me ajudar, agradeço.

#

# This is the main Apache HTTP server configuration file. It contains the

# configuration directives that give the server its instructions.

# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.

# In particular, see

# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>

# for a discussion of each configuration directive.

#

# Do NOT simply read the instructions in here without understanding

# what they do. They're here only as hints or reminders. If you are unsure

# consult the online docs. You have been warned.

#

# Configuration and logfile names: If the filenames you specify for many

# of the server's control files begin with "/" (or "drive:/" for Win32), the

# server will use that explicit path. If the filenames do *not* begin

# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"

# with ServerRoot set to "C:/Arquivos de programas/Apache Software Foundation/Apache2.2" will be interpreted by the

# server as "C:/Arquivos de programas/Apache Software Foundation/Apache2.2/logs/foo.log".

#

# NOTE: Where filenames are specified, you must use forward slashes

# instead of backslashes (e.g., "c:/apache" instead of "c:\apache").

# If a drive letter is omitted, the drive on which httpd.exe is located

# will be used by default. It is recommended that you always supply

# an explicit drive letter in absolute paths to avoid confusion.



#

# ServerRoot: The top of the directory tree under which the server's

# configuration, error, and log files are kept.

#

# Do not add a slash at the end of the directory path. If you point

# ServerRoot at a non-local disk, be sure to point the LockFile directive

# at a local disk. If you wish to share the same ServerRoot for multiple

# httpd daemons, you will need to change at least LockFile and PidFile.

#

ServerRoot "C:/Arquivos de programas/Apache Software Foundation/Apache2.2"



#

# Listen: Allows you to bind Apache to specific IP addresses and/or

# ports, instead of the default. See also the <VirtualHost>

# directive.

#

# Change this to Listen on specific IP addresses as shown below to

# prevent Apache from glomming onto all bound IP addresses.

#

#Listen 12.34.56.78:80

Listen 80



#

# Dynamic Shared Object (DSO) Support

#

# To be able to use the functionality of a module which was built as a DSO you

# have to place corresponding `LoadModule' lines at this location so the

# directives contained in it are actually available _before_ they are used.

# Statically compiled modules (those listed by `httpd -l') do not need

# to be loaded here.

#

# Example:

# LoadModule foo_module modules/mod_foo.so

#

LoadModule actions_module modules/mod_actions.so

LoadModule alias_module modules/mod_alias.so

LoadModule asis_module modules/mod_asis.so

LoadModule auth_basic_module modules/mod_auth_basic.so

#LoadModule auth_digest_module modules/mod_auth_digest.so

#LoadModule authn_alias_module modules/mod_authn_alias.so

#LoadModule authn_anon_module modules/mod_authn_anon.so

#LoadModule authn_dbd_module modules/mod_authn_dbd.so

#LoadModule authn_dbm_module modules/mod_authn_dbm.so

LoadModule authn_default_module modules/mod_authn_default.so

LoadModule authn_file_module modules/mod_authn_file.so

#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so

#LoadModule authz_dbm_module modules/mod_authz_dbm.so

LoadModule authz_default_module modules/mod_authz_default.so

LoadModule authz_groupfile_module modules/mod_authz_groupfile.so

LoadModule authz_host_module modules/mod_authz_host.so

#LoadModule authz_owner_module modules/mod_authz_owner.so

LoadModule authz_user_module modules/mod_authz_user.so

LoadModule autoindex_module modules/mod_autoindex.so

#LoadModule cache_module modules/mod_cache.so

#LoadModule cern_meta_module modules/mod_cern_meta.so

LoadModule cgi_module modules/mod_cgi.so

#LoadModule charset_lite_module modules/mod_charset_lite.so

#LoadModule dav_module modules/mod_dav.so

#LoadModule dav_fs_module modules/mod_dav_fs.so

#LoadModule dav_lock_module modules/mod_dav_lock.so

#LoadModule dbd_module modules/mod_dbd.so

#LoadModule deflate_module modules/mod_deflate.so

LoadModule dir_module modules/mod_dir.so

#LoadModule disk_cache_module modules/mod_disk_cache.so

#LoadModule dumpio_module modules/mod_dumpio.so

LoadModule env_module modules/mod_env.so

#LoadModule expires_module modules/mod_expires.so

#LoadModule ext_filter_module modules/mod_ext_filter.so

#LoadModule file_cache_module modules/mod_file_cache.so

#LoadModule filter_module modules/mod_filter.so

#LoadModule headers_module modules/mod_headers.so

#LoadModule ident_module modules/mod_ident.so

#LoadModule imagemap_module modules/mod_imagemap.so

LoadModule include_module modules/mod_include.so

#LoadModule info_module modules/mod_info.so

LoadModule isapi_module modules/mod_isapi.so

#LoadModule ldap_module modules/mod_ldap.so

#LoadModule logio_module modules/mod_logio.so

LoadModule log_config_module modules/mod_log_config.so

#LoadModule log_forensic_module modules/mod_log_forensic.so

#LoadModule mem_cache_module modules/mod_mem_cache.so

LoadModule mime_module modules/mod_mime.so

#LoadModule mime_magic_module modules/mod_mime_magic.so

LoadModule negotiation_module modules/mod_negotiation.so

#LoadModule proxy_module modules/mod_proxy.so

#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so

#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so

#LoadModule proxy_connect_module modules/mod_proxy_connect.so

#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so

#LoadModule proxy_http_module modules/mod_proxy_http.so

#LoadModule reqtimeout_module modules/mod_reqtimeout.so

#LoadModule rewrite_module modules/mod_rewrite.so

LoadModule setenvif_module modules/mod_setenvif.so

#LoadModule speling_module modules/mod_speling.so

#LoadModule ssl_module modules/mod_ssl.so

#LoadModule status_module modules/mod_status.so

#LoadModule substitute_module modules/mod_substitute.so

#LoadModule unique_id_module modules/mod_unique_id.so

#LoadModule userdir_module modules/mod_userdir.so

#LoadModule usertrack_module modules/mod_usertrack.so

#LoadModule version_module modules/mod_version.so

#LoadModule vhost_alias_module modules/mod_vhost_alias.so



<IfModule !mpm_netware_module>

<IfModule !mpm_winnt_module>

#

# If you wish httpd to run as a different user or group, you must run

# httpd as root initially and it will switch.

#

# User/Group: The name (or #number) of the user/group to run httpd as.

# It is usually good practice to create a dedicated user and group for

# running httpd, as with most system services.

#

User daemon

Group daemon



</IfModule>

</IfModule>



# 'Main' server configuration

#

# The directives in this section set up the values used by the 'main'

# server, which responds to any requests that aren't handled by a

# <VirtualHost> definition. These values also provide defaults for

# any <VirtualHost> containers you may define later in the file.

#

# All of these directives may appear inside <VirtualHost> containers,

# in which case these default settings will be overridden for the

# virtual host being defined.

#



#

# ServerAdmin: Your address, where problems with the server should be

# e-mailed. This address appears on some server-generated pages, such

# as error documents. e.g. admin@your-domain.com

#

ServerAdmin mnribeiro_7@hotmail.com



#

# ServerName gives the name and port that the server uses to identify itself.

# This can often be determined automatically, but we recommend you specify

# it explicitly to prevent problems during startup.

#

# If your host doesn't have a registered DNS name, enter its IP address here.

#

ServerName localhost:80



#

# DocumentRoot: The directory out of which you will serve your

# documents. By default, all requests are taken from this directory, but

# symbolic links and aliases may be used to point to other locations.

#

DocumentRoot "C:/Arquivos de programas/Apache Software Foundation/Apache2.2/htdocs"



#

# Each directory to which Apache has access can be configured with respect

# to which services and features are allowed and/or disabled in that

# directory (and its subdirectories).

#

# First, we configure the "default" to be a very restrictive set of

# features.

#

#<Directory />

# Options FollowSymLinks

# AllowOverride None

# Order deny,allow

# Deny from all

#</Directory>



<Directory />

Options FollowSymLinks

AllowOverride None

Order allow,deny

Allow from all

</Directory>



#

# Note that from this point forward you must specifically allow

# particular features to be enabled - so if something's not working as

# you might expect, make sure that you have specifically enabled it

# below.

#



#

# This should be changed to whatever you set DocumentRoot to.

#

<Directory "C:/Arquivos de programas/Apache Software Foundation/Apache2.2/htdocs">

#

# Possible values for the Options directive are "None", "All",

# or any combination of:

# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews

#

# Note that "MultiViews" must be named *explicitly* --- "Options All"

# doesn't give it to you.

#

# The Options directive is both complicated and important. Please see

# http://httpd.apache.org/docs/2.2/mod/core.html#options

# for more information.

#

Options Indexes FollowSymLinks



#

# AllowOverride controls what directives may be placed in .htaccess files.

# It can be "All", "None", or any combination of the keywords:

# Options FileInfo AuthConfig Limit

#

AllowOverride None



#

# Controls who can get stuff from this server.

#

Order allow,deny

Allow from all



</Directory>



#

# DirectoryIndex: sets the file that Apache will serve if a directory

# is requested.

#

<IfModule dir_module>

DirectoryIndex index.html index.php default.php main.php

</IfModule>



#

# The following lines prevent .htaccess and .htpasswd files from being

# viewed by Web clients.

#

<FilesMatch "^\.ht">

Order allow,deny

Deny from all

Satisfy All

</FilesMatch>



#

# ErrorLog: The location of the error log file.

# If you do not specify an ErrorLog directive within a <VirtualHost>

# container, error messages relating to that virtual host will be

# logged here. If you *do* define an error logfile for a <VirtualHost>

# container, that host's errors will be logged there and not here.

#

ErrorLog "logs/error.log"



#

# LogLevel: Control the number of messages logged to the error_log.

# Possible values include: debug, info, notice, warn, error, crit,

# alert, emerg.

#

LogLevel warn



<IfModule log_config_module>

#

# The following directives define some format nicknames for use with

# a CustomLog directive (see below).

#

LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined

LogFormat "%h %l %u %t \"%r\" %>s %b" common



<IfModule logio_module>

# You need to enable mod_logio.c to use %I and %O

LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio

</IfModule>



#

# The location and format of the access logfile (Common Logfile Format).

# If you do not define any access logfiles within a <VirtualHost>

# container, they will be logged here. Contrariwise, if you *do*

# define per-<VirtualHost> access logfiles, transactions will be

# logged therein and *not* in this file.

#

CustomLog "logs/access.log" common



#

# If you prefer a logfile with access, agent, and referer information

# (Combined Logfile Format) you can use the following directive.

#

#CustomLog "logs/access.log" combined

</IfModule>



<IfModule alias_module>

#

# Redirect: Allows you to tell clients about documents that used to

# exist in your server's namespace, but do not anymore. The client

# will make a new request for the document at its new location.

# Example:

# Redirect permanent /foo http://localhost/bar



#

# Alias: Maps web paths into filesystem paths and is used to

# access content that does not live under the DocumentRoot.

# Example:

# Alias /webpath /full/filesystem/path

#

# If you include a trailing / on /webpath then the server will

# require it to be present in the URL. You will also likely

# need to provide a <Directory> section to allow access to

# the filesystem path.



#

# ScriptAlias: This controls which directories contain server scripts.

# ScriptAliases are essentially the same as Aliases, except that

# documents in the target directory are treated as applications and

# run by the server when requested rather than as documents sent to the

# client. The same rules about trailing "/" apply to ScriptAlias

# directives as to Alias.

#

ScriptAlias /cgi-bin/ "C:/Arquivos de programas/Apache Software Foundation/Apache2.2/cgi-bin/"



</IfModule>



<IfModule cgid_module>

#

# ScriptSock: On threaded servers, designate the path to the UNIX

# socket used to communicate with the CGI daemon of mod_cgid.

#

#Scriptsock logs/cgisock

</IfModule>



#

# "C:/Arquivos de programas/Apache Software Foundation/Apache2.2/cgi-bin" should be changed to whatever your ScriptAliased

# CGI directory exists, if you have that configured.

#

<Directory "C:/Arquivos de programas/Apache Software Foundation/Apache2.2/cgi-bin">

AllowOverride None

Options None

Order allow,deny

Allow from all

</Directory>



#

# DefaultType: the default MIME type the server will use for a document

# if it cannot otherwise determine one, such as from filename extensions.

# If your server contains mostly text or HTML documents, "text/plain" is

# a good value. If most of your content is binary, such as applications

# or images, you may want to use "application/octet-stream" instead to

# keep browsers from trying to display binary files as though they are

# text.

#

DefaultType text/plain



<IfModule mime_module>

#

# TypesConfig points to the file containing the list of mappings from

# filename extension to MIME-type.

#

TypesConfig conf/mime.types



#

# AddType allows you to add to or override the MIME configuration

# file specified in TypesConfig for specific file types.

#

#AddType application/x-gzip .tgz

#

# AddEncoding allows you to have certain browsers uncompress

# information on the fly. Note: Not all browsers support this.

#

#AddEncoding x-compress .Z

#AddEncoding x-gzip .gz .tgz

#

# If the AddEncoding directives above are commented-out, then you

# probably should define those extensions to indicate media types:

#

AddType application/x-compress .Z

AddType application/x-gzip .gz .tgz



#

# AddHandler allows you to map certain file extensions to "handlers":

# actions unrelated to filetype. These can be either built into the server

# or added with the Action directive (see below)

#

# To use CGI scripts outside of ScriptAliased directories:

# (You will also need to add "ExecCGI" to the "Options" directive.)

#

#AddHandler cgi-script .cgi



# For type maps (negotiated resources):

#AddHandler type-map var



#

# Filters allow you to process content before it is sent to the client.

#

# To parse .shtml files for server-side includes (SSI):

# (You will also need to add "Includes" to the "Options" directive.)

#

#AddType text/html .shtml

#AddOutputFilter INCLUDES .shtml

</IfModule>



#

# The mod_mime_magic module allows the server to use various hints from the

# contents of the file itself to determine its type. The MIMEMagicFile

# directive tells the module where the hint definitions are located.

#

#MIMEMagicFile conf/magic



#

# Customizable error responses come in three flavors:

# 1) plain text 2) local redirects 3) external redirects

#

# Some examples:

#ErrorDocument 500 "The server made a boo boo."

#ErrorDocument 404 /missing.html

#ErrorDocument 404 "/cgi-bin/missing_handler.pl"

#ErrorDocument 402 http://localhost/subscription_info.html

#



#

# EnableMMAP and EnableSendfile: On systems that support it,

# memory-mapping or the sendfile syscall is used to deliver

# files. This usually improves server performance, but must

# be turned off when serving from networked-mounted

# filesystems or if support for these functions is otherwise

# broken on your system.

#

#EnableMMAP off

#EnableSendfile off



# Supplemental configuration

#

# The configuration files in the conf/extra/ directory can be

# included to add extra features or to modify the default configuration of

# the server, or you may simply copy their contents here and change as

# necessary.



# Server-pool management (MPM specific)

#Include conf/extra/httpd-mpm.conf



# Multi-language error messages

#Include conf/extra/httpd-multilang-errordoc.conf



# Fancy directory listings

#Include conf/extra/httpd-autoindex.conf



# Language settings

#Include conf/extra/httpd-languages.conf



# User home directories

#Include conf/extra/httpd-userdir.conf



# Real-time info on requests and configuration

#Include conf/extra/httpd-info.conf



# Virtual hosts

#Include conf/extra/httpd-vhosts.conf



# Local access to the Apache HTTP Server Manual

#Include conf/extra/httpd-manual.conf



# Distributed authoring and versioning (WebDAV)

#Include conf/extra/httpd-dav.conf



# Various default settings

#Include conf/extra/httspd-default.conf



# Secure (SSL/TLS) connections

#Include conf/extra/httpd-ssl.conf

#

# Note: The following must must be present to support

# starting without SSL on platforms with no /dev/random equivalent

# but a statically compiled-in mod_ssl.

#

<IfModule ssl_module>

SSLRandomSeed startup builtin

SSLRandomSeed connect builtin

</IfModule>



LoadModule php5_module "C:/php/php5apache2_2.dll"

AddType application/x-httpd-php .php

PHPIniDir "C:/php"


7. Re: Apache X Iptables [RESOLVIDO]

Renato Carneiro Pacheco
renato_pacheco

(usa Debian)

Enviado em 08/12/2010 - 10:44h

Já q vc falow q tá usando o Windows Server, olha se o firewall dele num tá habilitado. Se tiver, desabilite-o.


8. Re: Apache X Iptables [RESOLVIDO]

Marcelo Neves Ribeiro
sd_ribeiro

(usa Debian)

Enviado em 08/12/2010 - 10:59h

Sim, desabilitado.


9. Re: Apache X Iptables [RESOLVIDO]

Renato Carneiro Pacheco
renato_pacheco

(usa Debian)

Enviado em 08/12/2010 - 11:35h

Pra certificar q o problema tá no servidor d firewall, comente todas as regras (acrescentando cerquilha no começo de cada linha) e deixe apenas as linhas abaixo:

modprobe iptable_nat
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

#Politica Padrão
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT

Não se esqueça d limpar as regras antes:

# iptables -F
# iptables -t nat -F


10. Re: Apache X Iptables [RESOLVIDO]

Marcelo Neves Ribeiro
sd_ribeiro

(usa Debian)

Enviado em 08/12/2010 - 12:27h

OK. Fiz conforme vc descreveu, mas continua não acessando.


11. Re: Apache X Iptables [RESOLVIDO]

Renato Carneiro Pacheco
renato_pacheco

(usa Debian)

Enviado em 08/12/2010 - 14:02h

Então tente uma conexão direta com outro computador (ligando um cabo crossover ou ligando direto no switch) pra v se conecta tb.


12. Re: Apache X Iptables [RESOLVIDO]

Marcelo Neves Ribeiro
sd_ribeiro

(usa Debian)

Enviado em 08/12/2010 - 20:39h

Tudo bem vou tentar e depois posto aki. Não sei se eh relevante mas no pc que tah o win server eu configurei um dominio,mas não inseri os outros pc neste dominio, somente um e este tambem não acessa.



01 02



Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts