linux-kernel - Isse in Arp cache timeout

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: <869C2FE41C1E074D9858305AA6736A072F8A745A@SGSIMBX008.nsn-intra.net>
Date:	Wed, 30 Apr 2014 11:57:48 +0000
From:	"Agarwal, Rohit (NSN - IN/Bangalore)" <rohit.agarwal@....com>
To:	"davem@...emloft.net" <davem@...emloft.net>,
	"jiri@...nulli.us" <jiri@...nulli.us>,
	"hannes@...essinduktion.org" <hannes@...essinduktion.org>,
	"gaofeng@...fujitsu.com" <gaofeng@...fujitsu.com>,
	"vfalico@...hat.com" <vfalico@...hat.com>,
	"duanj.fnst@...fujitsu.com" <duanj.fnst@...fujitsu.com>,
	"noureddine@...stanetworks.com" <noureddine@...stanetworks.com>,
	"ebiederm@...ssion.com" <ebiederm@...ssion.com>,
	"hannes@...essinduktion.org" <hannes@...essinduktion.org>,
	"nicolas.dichtel@...nd.com" <nicolas.dichtel@...nd.com>,
	"tim.gardner@...onical.com" <tim.gardner@...onical.com>,
	"stephen@...workplumber.org" <stephen@...workplumber.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Wiebe, Wladislav (NSN - DE/Ulm)" <wladislav.wiebe@....com>
Subject: Isse in Arp cache timeout

Hi,

We are facing problem with Arp cache timeout. 

System being used is as below -
Board (having Octeon processor) is running Linux(3.10.34) with one of the Ethernet interface connected to NIC card which is then connected to a Windows PC. 
Default value for base_reachable_time_ms is set to 30000 on board. Traffic(ping) is send from PC to Board. 
"ip neigh" shows the arp being resolved & entry status as reachable. After some time (20-40 sec), the status changes to stale.

Now we change the value of base_reachable_time_ms to 100000. But resulting timeout does not change. The stale status is reached within same 20-40 sec.
This behavior remains forever. Even if we assign different values to base_reachable_time_ms, still no change in time out.

Only when system is restarted the new value is effective.

Can you please let us know if you have some idea about this issue and what may be the probable cause.

~Regards
Rohit Agarwal

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/