Tag Info

New answers tagged

2

According to the man page, firewalk looks to need the following flags in order to properly scan when you are one hop from your gateway (as seen in your pretty Gliffy picture). firewalk -d 49152 -r 192.168.1.2 192.168.3.11


1

Correct me if I am wrong, but it sounds like you are running an authoritative DNS server for your client's domain, and people will need to be able to query this server from the public Internet. For security, authoritative DNS servers at least have the following settings: Queries for other domains should be ignored or refused There should be rate limiting ...


0

It depends, normally you should limit the IP ranges which are allowed to query your DNS server. The reason being that if you allow any IP to query your DNS server using UDP, it might be abused for performing DNS amplification attacks if you are an open resolver.


0

Seems like there is something blocking your egress traffic. Are you configured to use a proxy, such as a web-protection proxy? Try sending HTTP/TLS packets through it with ProxyChains -- https://github.com/rofl0r/proxychains-ng/ -- but using only connection-oriented and non-pinging Nmap flags (i.e., -Pn -sT). Does the traceroute (i.e., --traceroute) Nmap ...


1

This is a known issue with TCP Connect (-sT) scans in Nmap 6.40 through 6.47. It's really a "problem" with Linux itself, as I mentioned in an answer to the same question at StackOverflow, which allows a process to connect to itself by using the same source and destination port. Nmap used to have a workaround to detect the situation, but it got removed in a ...



Top 50 recent answers are included