netdev - Re: REDIRECT in nat OUTPUT

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 13 Jul 2008 18:12:36 +0300
From:	Denys Fedoryshchenko <denys@...p.net.lb>
To:	Krzysztof Oledzki <olel@....pl>
Cc:	Evgeniy Polyakov <johnpol@....mipt.ru>, netdev@...r.kernel.org,
	netfilter-devel@...r.kernel.org,
	David Miller <davem@...emloft.net>,
	Eric Dumazet <dada1@...mosbay.com>
Subject: Re: REDIRECT in nat OUTPUT

On Sunday 13 July 2008, Krzysztof Oledzki wrote:
> > No, seems it has performance issues without redirect(and conntrack unloaded too) even, iperf results on loopback is very unstable.
> >
> > Actually i dont understand, how on idle machine with Xeon processor iperf over loopback (tcp) can be ~100Mbps?
> > I think it is a bug.
> 
> Something is wrong here as:
> 
> root@...-t:~# iperf -c 127.1
> ------------------------------------------------------------
> Client connecting to 127.1, TCP port 5001
> TCP window size: 49.2 KByte (default)
> ------------------------------------------------------------
> [  3] local 127.0.0.1 port 36419 connected with 127.0.0.1 port 5001
> [  3]  0.0-10.0 sec  7.10 GBytes  6.10 Gbits/sec
> 
> # uname -r
> 2.6.24.7-o4
> 
> # grep "model name" /proc/cpuinfo|uniq
> model name      : Intel(R) Xeon(R) CPU           X5460  @ 3.16GHz
> 
> Best regards,
> 
>  			Krzysztof Olędzki
Probably we have to do .config diff, cause i can catch instability from 2.6.17 till latest rc
Mine is http://www.nuclearcat.com/config-lo.txt


-- 
------
Technical Manager
Virtual ISP S.A.L.
Lebanon
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html