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: <f7aa79a4-81d9-5b6d-3a27-0d681e5619ae@oracle.com>
Date:   Mon, 17 Jul 2017 11:28:02 -0700
From:   Rao Shoaib <rao.shoaib@...cle.com>
To:     netdev@...r.kernel.org
Subject: What is the correct behavior ipv4/ipv6

I am looking at a system which is configured for IPv6 only but sits in a 
network that serves both IPv4 and IPv6. When an IPv4 packet with a 
destination  broadcast address is sent out (in this case DHCP) the 
system accepts it and since it does not have any route to the sender it 
prints the Martian message.

Sure, we can turn off the Martian message and maybe the system should be 
in an IPv6 only network.

The question that is being asked is that why is the system accepting an 
IPv4 broadcast packet in the first place ?  Is this behavior incorrect 
and should I submit a patch ?

Thanks,

Shoaib

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ