Acesso Via outra subnet [RESOLVIDO]

1. Acesso Via outra subnet [RESOLVIDO]

Giovane Bertol
giovanebertol

(usa CentOS)

Enviado em 04/04/2016 - 08:43h

Bom dia Pessoal,

estou quebrando a cabeça já fazem 4 dias com o acesso ao site que configurei no apache, via subnet diferente do servidor.

Meu servidor tem o ip 172.16.0.3/16 e acessando na mesma subrede funciona que é uma maravilha, porém quando tento acessar via a rede 192.168.0.0/24 não tem cristo de conseguir.
Tento acessar via telnet, a conexão demora, e às vezes até conecta, porém não retorna dados da página para a subrete 192.168.0.0. Alguém poderia me ajudar?

Abaixo minha configuração do apache:


ServerRoot "/etc/httpd"

Listen 80

<VirtualHost *:80>
DocumentRoot /var/www/html/wordpress
ServerName wiki.caxias.ifrs.edu.br
ErrorLog /var/log/httpd/error.log
CustomLog /var/log/httpd/access.log combined
</VirtualHost>

Include conf.modules.d/*.conf


User apache
Group apache
ServerAdmin root@localhost

#ServerName www.example.com:80

#
# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other
# <Directory> blocks below.
#
<Directory />
AllowOverride none
Require all denied
</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.
#

#
# 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 "/var/www/html"

#
# Relax access to content within /var/www.
#
<Directory "/var/www">
AllowOverride None
# Allow open access:
Require all granted
</Directory>

# Further relax access to the default document root:
<Directory "/var/www/html">
Require all granted
#
# 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.4/mod/core.html#options
# for more information.
#
Options 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.
#
Require all granted

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
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ".ht*">
Require all denied
</Files>

#
# 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 debug

<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://www.example.com/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/ "/var/www/cgi-bin/"

</IfModule>

#
# "/var/www/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/var/www/cgi-bin">
AllowOverride None
Options None
Require all granted
</Directory>

#<Directory /var/www/html/>
# AuthType NTLM
# AuthName CAXIAS.IFRS.LOCAL
# require valid-user
# PythonAuthenHandler pyntlm
# PythonOption Domain CAXIAS.IFRS.LOCAL
# PythonOption PDC SRV01.CAXIAS.IFRS.LOCAL
# PythonOption BDC !!BACKUP_DOMAIN_CONTROLLER!!
#</Directory>

<IfModule mime_module>
#
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
#
TypesConfig /etc/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>

#
# Specify a default charset for all content served; this enables
# interpretation of all content as UTF-8 by default. To use the
# default browser choice (ISO-8859-1), or to allow the META tags
# in HTML content to override this choice, comment out this
# directive:
#
AddDefaultCharset UTF-8

<IfModule mime_magic_module>
#
# 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
</IfModule>

#
# 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://www.example.com/subscription_info.html
#

#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall may be 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.
# Defaults if commented: EnableMMAP On, EnableSendfile Off
#
#EnableMMAP off
EnableSendfile on

# Supplemental configuration
#
# Load config files in the "/etc/httpd/conf.d" directory, if any.
IncludeOptional conf.d/*.conf
#ProxyPreserveHost On

#ProxyPass wiki.caxias.ifrs.edu.br http://localhost:80/wordpress
#ProxyPassReverse wiki.caxias.ifrs.edu.br http://localhost:80/wordpress
#ProxyPass 172.16.0.254 http://localhost:80/wordpress
#ProxyPassReverse 172.16.0.254 http://localhost:80/wordpress




  


2. Re: Acesso Via outra subnet [RESOLVIDO]

Carlos Alberto de Souza Barbosa
souzacarlos

(usa Outra)

Enviado em 04/04/2016 - 09:11h

Bom dia, como estão tuas configurações de firewall? Que tipo de equipamento de borda (ROUTER) vc utiliza para interligar mesmo que logicamente essas subredes?

aguardo


3. Acesso Via outra subnet

Giovane Bertol
giovanebertol

(usa CentOS)

Enviado em 04/04/2016 - 09:24h

Bom dia souzacarlos,
estou utilizando o pfsense, que possui três interfaces físicas, uma Externa e duas internas, conectado a três switches, um somente conexão externa, outro rede 192 e o último na rede 172. No firewall liberei o tráfico para a rede nas duas placas, também desabilitei o firewall no servidor web para testar. Não tenho nenhum log de erro e no acess_log tenho apenas a requisição.

192.168.0.200 - - [04/Apr/2016:09:24:38 -0300] "GET / HTTP/1.1" 302 15072 "-" "Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E)"

Não sei se fiz por entender.

Desde já agradeço


4. Re: Acesso Via outra subnet [RESOLVIDO]

Carlos Alberto de Souza Barbosa
souzacarlos

(usa Outra)

Enviado em 04/04/2016 - 10:10h

giovanebertol escreveu:

Bom dia souzacarlos,
estou utilizando o pfsense, que possui três interfaces físicas, uma Externa e duas internas, conectado a três switches, um somente conexão externa, outro rede 192 e o último na rede 172. No firewall liberei o tráfico para a rede nas duas placas, também desabilitei o firewall no servidor web para testar. Não tenho nenhum log de erro e no acess_log tenho apenas a requisição.

192.168.0.200 - - [04/Apr/2016:09:24:38 -0300] "GET / HTTP/1.1" 302 15072 "-" "Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E)"

Não sei se fiz por entender.

Desde já agradeço


Bom dia.
Cara tudo indica ser problema de roteamento, com vc mesmo disse a requisição tá chegando, não nenhum especialista em PFSENSE mas firewall e firewall. Favor conferir se a liberação em todos os sentidos estão liberados.

Caso queira bater um papo sobre isso pode add no skype

SKype: carlossouzainfo



5. Resolvido

Giovane Bertol
giovanebertol

(usa CentOS)

Enviado em 27/04/2016 - 07:51h

Bom dia Pessoal,

resolvi o problema. As configurações estavam corretas, o problema foi com a interface da VM, que não sei porque caldas d'água não fazia o roteamento, migrei a mesma máquina para outro servidor e pronto funcionou.

Obrigado.






Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts