netdev - Re: [RFC patch net-next] ipv4: use bcast as dst address in case IFF

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 8 Jan 2013 22:51:47 +0100 (CET)
From:	Jan Engelhardt <jengelh@...i.de>
To:	Stephen Hemminger <stephen.hemminger@...tta.com>
cc:	Jiri Pirko <jiri@...nulli.us>, davem@...emloft.net,
	edumazet@...gle.com, kuznet@....inr.ac.ru, jmorris@...ei.org,
	yoshfuji@...ux-ipv6.org, kaber@...sh.net, netdev@...r.kernel.org,
	pavlix@...lix.net
Subject: Re: [RFC patch net-next] ipv4: use bcast as dst address in case
 IFF_NOARP is set


On Tuesday 2013-01-08 20:10, Stephen Hemminger wrote:
>> 
>>Also, what is the issue with sending all packets to broadcast when
>>NOARP is set? In my opinion, it only makes sense.
>
>It looks like NOARP devices are point-to-point and don't really have
>any concept of broadcast.

PTP links usually are NOARP, but NOARP does not necessarily imply
a PTP link.
--
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