Tag Info

Hot answers tagged

3

Your best option, without SSH access would be nmap's OS detection. It's not going to be totally reliable, but it's probably better than nothing, which seems to be your other option. Here's a page with a little run down on how the OS detection works, which should give you an idea of its limitations.


2

You can use nmap as mentioned by the previous response. sudo nmap -sV -T4 -O -F --version-light <your_server> NOTE: If you run a nmap against a server that you don't own, prepare to explain when a call from network security admin asking you what are you trying to do. In other words, don't do it if it is not your server.


2

Problem was in a route on web-server: For testing added route to 199.58.86.0/24 through ppp0 interface and page opened successfully.


1

There are a couple of ways you can tackle this one. The easiest way is to increase ephemeral range, but you already kinda did this and there are obviously limits how far you can go with this solution. Another solution would be round-robin DNS and adding multiple IP addresses to your load balancer nodes. Sometimes this is not easily applicable (you need to ...


1

What I see in your packet trace is congestion control reacting to packet loss. The client starts out sending an initial 9 segments followed by slow start, where it send two more segments each time it receives an ACK packet. The slow start algorithm continues until the first duplicate ACK from the server indicates that a packet has been lost. This happens ...


1

Linux has a weak host model and the network stack doesn't really care which interface an TCP/IP packet arrives on. If it is for a configured IP-address it will be accepted. That does not take into account ARP, firewall rules and routing.


1

From RFC 1812 : (e) { 127, } Internal host loopback address. Addresses of this form MUST NOT appear outside a host. The kernel uses net.ipv4.conf.<interface>.route_localnet to make 127.0.0.0/8 routable or not (actually consider source/destination IP addresses of this kind as martian packets or not). I completely disencourage you to ...


1

That's caused by a kernel bug. It was patched over a year ago in the distribution kernels, but you are not running the kernel provided by your distribution. Either switch to a distribution kernel or contact whoever built your kernel.



Only top voted, non community-wiki answers of a minimum length are eligible