| 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
| ||
|
Message-ID: <20090604145347.GA27692@miyuki> Date: Thu, 4 Jun 2009 16:53:47 +0200 From: Philipp Reh <sefi@...-f-i.de> To: linux-kernel@...r.kernel.org Subject: When does Linux drop UDP packets? Dear list, I have the following setting in which a client that resides on the same physical network as a server wants to receive any UDP packet that arrives on any of its interfaces sent by that server. The code sets the broadcast flag, calls bind to INADDR_ANY and uses recvfrom from there on. Let's say the server resides in the subnet 192.168.6.255 and the client in 192.168.3.255. The server uses its real IP as the packet's sender ip (192.168.6.5). Now the first problem I've encountered is the following: If the client removes its default route and doesn't have any route pointing into the subnet the server is in, the packets get discarded (still tcpdump sees them). The second problem is that if the server uses the broadcast address as its sender address (255.255.255.255), the packets get always discarded (again, tcpdump sees them). Now if the server fakes its sender address to be in the client's subnet, every packet arrives again. So my real question is: When does Linux discard packets and how can I prevent it from doing that? As I'm not yet subscribed to the list, please CC me directly. Cheers, Philipp -- 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/
Powered by blists - more mailing lists