Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I am working in a windows 7 corporate environment with a proxy and I need to run a application which uses ping to check a connection.
www.google.com is accessible from the browser but when I try to run ping www.google.com from the command prompt I get host unreachable.
PS: I tried telnet www.google.es 80/443 and it doesn't work, I already tried attacking the IP but it doesn't work (timeout).
Unfortunately this is not possible, web proxies understand specific set of protocols HTTP, HTTPS, TCP , some streaming protocols, whatever they support would be either TCP or UDP based. But ping is ICMP. You can't pipe ICMP through a web proxy.
However, you have some alternatives:
1- Ask your IT team to open ICMP for you from firewall, assume routing exist.
2- Recode the application to test connectivity using HTTP requests instead of ping.
3- Add whatever host the application is testing the connectivity with to the windows hosts file and map it to 127.0.0.1:
127.0.0.1 www.somehost.com
This will make the application thinking connectivity exist.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I am struggling with some problem, probably because there is simply not enough information on the web regarding some specifics I am trying to setup.
I have bought OpenVPN service via tun (routing).
I connect to the OpenVPN server through Raspberry PI (serving me as router), which has two interfaces - eth0 for handling Internet connection and wlan0 for my internal LAN.
My goal is to setup firewall in such way, that I can filter tun-ned income traffic and be able to reach web from LAN behind wlan0. Also - everything should go via VPN.
From the architectural point of view I think it should look like this:
INPUT, FORWARD - dropped,
OUTPUT - allowed,
eth0 allows to flow only packets via default OpenVPN service port,
tun adapter should have all INPUT-related policies applied and should be NAT-ted.
What you think - is this correct thinking? I have managed so far to be able to ping from SSH-ed Raspberry PI into web, but yet no DNS - do I understand correctly that I should have own DNS forwarder? DHCP server is set on Raspberry PI.
Thanks!
I have already solved the issue. For those which are interested - incoming packets from LAN are processed by openvpn client (tun/tap), then passed over internet-facing interface. So it was a mater of setting correct forwarding between interfaces. /etc/resolv.conf just had to been overwritten with global (like Google) DNSes to solve ping-related problem.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I purchased a domain through Amazon Route 53 and am hosting my Node.js/ExpressJS app on an Amazon Linux EC2 Instance server. I can get my site to run on my EC2 server by using the public IP:portNumber or by using the publicDNS:portNumber, but I am struggling to understand how to set up the record sets in the hosted zone section of the Route 53 console to have my website point to www.thedomainipurchased.com:portNumber. I also read somewhere that you can't add the port number onto the public ip like that, so I would like to know how to set up both records to do this. I'm new to DNS, which is why I've had such a hard time although I'm sure to some people this seems very simple so would really appreciate any feedback to be explained in as basic and simple of a way as possible. Record Set Picture here
DNS only provides a way to map names to the IP addresses of hosts. Except under very limited circumstances you can't include a port number. DNS simply isn't designed to do that.
Ports are determined by the protocol involved. If you use a web browser to connect via HTTP then it will default to using port 80. If you use a web browser to connect via HTTPS then it will default to using port 443. When you send e-mail the default port is 25. When you SSH into a server the default port is 22. And so on. Default ports are essentially part of the specification for the global internet.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have this routing table:
I used SSH to be able to use my Raspberry Pi on my laptop screen. Everything was fine until I opened my browser and wanted to ping Google in the terminal. I can't, though.
When I try to ping 8.8.8.8 (Google's nameserver), I get the message below the routing table in the image above. But the strange thing is, when I run SSH with PuTTY on a different laptop, the Internet connection is fine. So probably the problem is on my laptop.
How can I fix this issue?
Seems like you are using 192.168.1.1 as a gateway, yet you have configured 192.168.137.0/24 as the network.
You should either try to configure the default gateway to - perhaps - 192.168.137.1 or your IP address to 192.168.1.x.
An ifconfig output would be handy.
Edit:
Add default gateway:
route add default gw 192.168.137.1
You might also need to remove current default gateway(s).
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I've got a reply from my server admin as "Do you need any ports open?"
On this server one website is hosted which is not getting loaded. So I conveyed him that the website is not getting loaded though I'm able to login to the given IP address through FTP client (File Zilla) and ssh (using terminal).
Actually I want to access the files at the said IP address through FTP client and its working fine. My main issue is that the website is not loading.
I'm not getting what does this question mean and what should I reply to it? I'm not aware of any such thing.
Services on the network use different "ports" to distinguish between different endpoints. You can imagine a port number as a "sub-address". For successful connection you need to know an IP address and also the port number.
For example FTP protocol uses port 21. You can find more detailed list of commonly used ports on Wikipedia http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers
The common phrase "open some port" means the access to that particular port will be enabled on firewall (usually all ports are "closed" because of security).
For your website you need ports 80 and 443 to be opened
If your website is using the HTTP protocol, then you need port 80 to be open. If it is using HTTPS protocol, then you need port 443 to be open.
Try getting both the ports opened, that should solve your problem immediately.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I have installed a CentOS 6.5 web server, now it is connected to LAN and WAN, Joomla is installed (LAMP)
I'm not able to see the webpage from internet only from LAN
I've checked
/etc/resolv.conf
eth1 Internet IP
/etc/httpd/conf/httpd.conf
/etc/hosts
[public ip] [www.mywebsite.org.ec]
I have disabled iptables, but still no access.
Is there something else I can check?
SOLUTION:
There was something missing in the route table.
You have to set de WAN gateway as default instead of LAN Gateway
To see the web page from internet side your gateway router should direct requests for HTTP to your server. Check your NAT configuration for the gateway device. Also if there exists a firewall on that device, you should configure it to accept HTTP requests.