search for: hping3

...ReportedBy: Mitsuaki_Shiraishi at symantec.com Estimated Hours: 0.0 Iptables on Ubuntu 13.10 cannot block outbound packets sent by Nessus. [TESTED ENVIRONMENT] * Iptables v1.4.18 * Ubuntu 13.10 on x86_64 (Kali Linux 1.0.5 64bit may also be affected) * Nessus 5.2.4 * Nmap 6.40 * Hping3 3.0.0-alpha-2 * Local ip: 192.168.2.100 * Remote ip: 192.168.2.99 [FINDING] Iptables cannot block outbound packets sent by local Nessus daemon. Setting OUTPUT chain's policy DROP and appending rule that ACCEPT loopback interface should be block any outbound packets through eth1. However...

Am 15.05.2015 um 18:17 schrieb Gordon Messmer <gordon.messmer at gmail.com>: > On 05/15/2015 09:02 AM, Leon Fauster wrote: >> >> I have a public peer system (yy.yy.yy.yy) that is reachable >> via my home uplink (xx.xx.xx.xxx). >> >> 15:59:30.244199 IP xx.xx.xx.xxx.42958 > yy.yy.yy.yy.https: tcp 0 >> 15:59:30.281931 IP yy.yy.yy.yy.https >

...If you're getting no response, the most likely problems are either a bad route or a firewall rule somewhere along the path. The problem could exist at anywhere along the path, and they'll typically both look the same according to tests at your host. As Anthony pointed out, you can use hping3 in TCP traceroute mode to determine where along the path the problem probably exists. The first host to not respond should be the host with the problem. Hopefully you have access to a host that has access and a similar path to the host you can't reach. If so, the same hping3 command shou...

...he idea is to use eth2 for pinging only, the other two interfaces are used by another service and management access. If I do: ping -c 2 -I eth2 74.125.39.147 or fping -c 2 -I eth2 74.125.39.147 It binds to eth2 and sends its ICMP probes via that interface with the IP on that interface. If I do: hping3 -1 -c 2 -I eth2 74.125.39.147 -VD or [root at server ~]# hping3 -c 2 -I eth2 74.125.39.147 -VD DEBUG: if lo: Don't Match (but seems to be UP) DEBUG: if eth0: Don't Match (but seems to be UP) DEBUG: if eth1: Don't Match (but seems to be UP) DEBUG: if eth2: OK using eth2, addr: 172.16.6.6...

...^ I've discovered a workaround, removing the second brackets: nft> add rule filter output tcp flags & (syn | ack) == syn | ack counter log NFT CLI seems to accept it. I did not check if it works, but I've set a similar rule to block "Xmas scans" and, checked against a Hping3 scan (-UPF option), it seems to work fine: nft> add rule filter input tcp flags & (fin | syn | rst | psh | ack | urg) == fin | psh | urg log drop Since I've watched that erroneus syntax on other Nftables tutorials around the net, I guess it *did* work sometime in the past, but now it...

...x off'' on the domU fixes the checksumming problem. I see this behavior between domU''s using the same dom0 bridge on the same xen host. And I have tested between two Debian Squeeze domU''s + one domU with 2.6.38 kernel. Easiest way to reproduce seems to be with DNS (tried hping3 -2 ... but it DID send correct udp checksums even with tx-checksumming turned on). Sniffing on a server (not necessarily running a DNS server, but pointed to in the other domU''s resolv.conf): # tcpdump -nnpvvi eth0 port 53 tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture s...

Hi there, I am getting very low throughput (around 0.29Mbps) while running netperf benchmark for guest to guest communication on a single physical host. To analyse where the time is spent in hypervisor I wanna use profiling. Please help me choosing good profiler according to my requirments. Should it be better in my case, Xentrace, gprof, xenoprof  or Oprofile. Is it possible to use some vtune

Hi there, I am getting very low throughput (around 0.29Mbps) while running netperf benchmark for guest to guest communication on a single physical host. To analyse where the time is spent in hypervisor I wanna use profiling. Please help me choosing good profiler according to my requirments. Should it be better in my case, Xentrace, gprof, xenoprof  or Oprofile. Is it possible to use some vtune

I am experiencing poor network performance on Dom0. When i ping other hosts on the same LAN, packets are out of order, and they show response times ranging from < 1 ms to several seconds, and some packets get lost. For example, a typical ping result looks like this: 87 packets transmitted, 80 received, +3 errors, 8% packet loss, time 86038ms rtt min/avg/max/mdev =