lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <d39c36500708021301i6754cb6bh4ba1a2a85092ce3c@mail.gmail.com>
Date:	Thu, 2 Aug 2007 23:01:37 +0300
From:	"nano bug" <linnewbye@...il.com>
To:	netdev@...r.kernel.org
Subject: Fwd: source interface ping bug ?

---------- Forwarded message ----------
From: nano bug <linnewbye@...il.com>
Date: Aug 2, 2007 10:58 PM
Subject: Re: source interface ping bug ?
To: Patrick McHardy <kaber@...sh.net>


Hello,

Yes I'm running NAT, I have atached the output of the iptables -t nat
-vxnL command and the routing tables

On 7/30/07, Patrick McHardy <kaber@...sh.net> wrote:
> nano bug wrote:
> > [...]
> > using source interface :
> >
> > root@...kstar:~/iputils# ./ping -I eth2 87.248.113.14
> > PING 87.248.113.14 (87.248.113.14) from 86.106.19.75 eth2: 56(84) bytes of data.
> >>From 86.106.19.75 icmp_seq=1 Destination Host Unreachable
>
> > root@...kstar:~# tcpdump -i eth2 -vvv -n host 87.248.113.14 and host
> > 86.106.19.75
> > tcpdump: listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes
> > 01:19:24.292911 arp who-has 87.248.113.14 tell 86.106.19.75
>
>
> Are you using (or running) NAT locally? What do your routing tables look
> like?
>

Download attachment "route_tables" of type "application/octet-stream" (2032 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ