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: <C4AF677B-55AC-4CE0-9BFB-EBB2E0C3BF74@emagii.com>
Date:	Wed, 5 Nov 2014 07:48:01 +0100
From:	Ulf samuelsson <netdev@...gii.com>
To:	Netdev <netdev@...r.kernel.org>
Subject: How to make stack send broadcast ARP request when entry is STALE?

Have a problem with an HP router at a certain location, which
is configured to only answer to broadcast ARP requests.
That cannot be changed.

The first ARP request the kernel sends out, is a broadcast request,
which is fine, but after the reply, the kernel sends unicast requests,
which will not get any replies.

The ARP entry will after some time enter STALE state,
and if nothing is done it will time out, and be removed.
This process takes to long, and I have been told that it is
difficult to makes changes that will eventually remove it.

Have tried to change the state from STALE to INCOMPLETE, which failed,
and then tried to change the state to PROBE which also failed.

The stack is only sending out unicasts, and never broadcast.
Is there any way to get the stack to send out a broadcast ARP
without having to wait for the entry to be removed?

I think the recommended behaviour in IPv6 is to send out 3 unicasts
and if all fails, to send out broadcasts.

Anyone know any good literature on how the ARP + neigh state machine works
in the kernel.

I read in Herberts book about the Linux TCP/IP stack and it only discuss how to reply to 
ARP requests and not anything on how to generate ARP requests.

Best Regards
Ulf Samuelsson


--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ