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
Le 30/04/2014 13:57, Agarwal, Rohit (NSN - IN/Bangalore) a ?crit :
> 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.
Did you change only the default value
(/proc/sys/net/ipv[4|6]/neigh/default/base_reachable_time_ms) or the value of
the interface (/proc/sys/net/ipv[4|6]/neigh/mynetdev/base_reachable_time_ms)?
>
> Only when system is restarted the new value is effective.
In you change the default value, only interfaces that didn't have an IPv4 (or
an IPv6) address will "get" this new value, but all interfaces that already
have an IPv4 (or IPv6) address will keep the previous value, ie the one set in
their own entries.
Regards,
Nicolas
Hi Nicolas,
I use below command and change this value for all interface.
for d in $(/bin/ls /proc/sys/net/ipv4/neigh); do
echo 30000 > /proc/sys/net/ipv4/neigh/$d/base_reachable_time_ms
done
~Regards
Rohit Agarwal
-----Original Message-----
From: ext Nicolas Dichtel [mailto:[email protected]]
Sent: Wednesday, April 30, 2014 6:52 PM
To: Agarwal, Rohit (NSN - IN/Bangalore); [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Cc: [email protected]; Wiebe, Wladislav (NSN - DE/Ulm)
Subject: Re: Isse in Arp cache timeout
Le 30/04/2014 13:57, Agarwal, Rohit (NSN - IN/Bangalore) a ?crit :
> 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.
Did you change only the default value
(/proc/sys/net/ipv[4|6]/neigh/default/base_reachable_time_ms) or the value of
the interface (/proc/sys/net/ipv[4|6]/neigh/mynetdev/base_reachable_time_ms)?
>
> Only when system is restarted the new value is effective.
In you change the default value, only interfaces that didn't have an IPv4 (or
an IPv6) address will "get" this new value, but all interfaces that already
have an IPv4 (or IPv6) address will keep the previous value, ie the one set in
their own entries.
Regards,
Nicolas