Friends I have the following Cisco DPC3825. Enter the settings and put in the DMZ web server that I have, but when I try to access it from another network I get the error code 504, which is the gateway problem. I can access the server via ssh without problems. Research on google for 3 days and can not find the solution to my problem.
This router is different compared to the ones I had.
The IP to access my router via web from the local network is 192.168.100.1, and the IP of the server I put in the DMZ is 192.168.0.17.
No other information could you provide to clarify my problem.
Sincerely Fidel Dominguez
How exactly is the Cisco related to the CentOS server?? If ssh works then you should get the same result unless the device is loaded and not fit for the job!! How do you setup this cisco device?? by CLI or other methods? try this: http://www.cisco.com/web/consumer/support/modem_DPC3825.html#~user-guides in case you passed this we can try to help you more.
Eliezer
On 08/09/2013 12:46 AM, Fidel Dominguez wrote:
Friends I have the following Cisco DPC3825. Enter the settings and put in the DMZ web server that I have, but when I try to access it from another network I get the error code 504, which is the gateway problem. I can access the server via ssh without problems. Research on google for 3 days and can not find the solution to my problem.
This router is different compared to the ones I had.
The IP to access my router via web from the local network is 192.168.100.1, and the IP of the server I put in the DMZ is 192.168.0.17.
No other information could you provide to clarify my problem.
Sincerely Fidel Dominguez _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 8/8/2013 2:46 PM, Fidel Dominguez wrote:
The IP to access my router via web from the local network is 192.168.100.1, and the IP of the server I put in the DMZ is 192.168.0.17.
assuming the network masks for both those are /24 (255.255.255.0) they won't be able to communicate directly as they are on different subnets. the usual trick is to temporarily add a virtual IP to the host you're trying to connect from, like eth0:1 == 192.168.100.2 then it will be able to reach 192.168.100.1
But, as the other guy said, what exactly does this have to do with CentOS ?
The router is connected by network cable, and the only thing that changes in the configuration of the router was add the web server IP to the DMZ zone.
On Thu, Aug 8, 2013 at 3:28 PM, John R Pierce pierce@hogranch.com wrote:
On 8/8/2013 2:46 PM, Fidel Dominguez wrote:
The IP to access my router via web from the local network is
192.168.100.1,
and the IP of the server I put in the DMZ is 192.168.0.17.
assuming the network masks for both those are /24 (255.255.255.0) they won't be able to communicate directly as they are on different subnets. the usual trick is to temporarily add a virtual IP to the host you're trying to connect from, like eth0:1 == 192.168.100.2 then it will be able to reach 192.168.100.1
But, as the other guy said, what exactly does this have to do with CentOS ?
-- john r pierce 37N 122W somewhere on the middle of the left coast
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
This is the error messages:
"Server error
The server for http://www.mydomain.com took too long to respond. It may be overloaded.
Error code: 504"
Any idea???
On Thu, Aug 8, 2013 at 4:23 PM, Fidel Dominguez fdvalero.rhel@gmail.comwrote:
The router is connected by network cable, and the only thing that changes in the configuration of the router was add the web server IP to the DMZ zone.
On Thu, Aug 8, 2013 at 3:28 PM, John R Pierce pierce@hogranch.com wrote:
On 8/8/2013 2:46 PM, Fidel Dominguez wrote:
The IP to access my router via web from the local network is
192.168.100.1,
and the IP of the server I put in the DMZ is 192.168.0.17.
assuming the network masks for both those are /24 (255.255.255.0) they won't be able to communicate directly as they are on different subnets. the usual trick is to temporarily add a virtual IP to the host you're trying to connect from, like eth0:1 == 192.168.100.2 then it will be able to reach 192.168.100.1
But, as the other guy said, what exactly does this have to do with CentOS ?
-- john r pierce 37N 122W somewhere on the middle of the left coast
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 8/8/2013 4:23 PM, Fidel Dominguez wrote:
The router is connected by network cable, and the only thing that changes in the configuration of the router was add the web server IP to the DMZ zone.
since we have no idea what your network topology is, and what "DMZ" means in this context, meh.
anyways, THIS IS TOTALLY OFFTOPIC ON THIS LIST. take it to a Cisco list or to Cisco technical support or something.
-
Eliezer Croitoru -
Fidel Dominguez -
John R Pierce