Context Navigation

Changes between Version 1 and Version 2 of Ticket #672, comment 7

v1	v2
3	3	> Please excuse my ignorance, but how may this situation legally happen that the client is receiving UDP packets it didn't ask for? Am I missing something? The only situation I could imagine is a broadcast, but that does not reproduce it for me.
4	4
5		When a udp packet is received it goes: driver->ethip->inetsrv(here is decided if it is addressed to one of local addresses, 255.255.255.255 being broadcast qualifies)->udp(here is decided if there exists a client listening for messages addressed to endpoint - local port + local address - where the message is addressed). By client i mean some application using udp server. Analogicaly ethip is client of driver, inetserv is client of ethip, udp is client of inetsrv. The problem is quite opposite - bug occurs when there does not exit a client to receive the message
	5	When a udp packet is received it goes: driver->ethip->inetsrv(here is decided if it is addressed to one of local addresses, 255.255.255.255 being broadcast qualifies)->udp(here is decided if there exists a client listening for messages addressed to endpoint - local port + local address - where the message is addressed). By client i mean some application using udp server. Analogicaly ethip is client of driver, inetserv is client of ethip, udp is client of inetsrv. The problem is quite opposite - bug occurs when there does not exist a client to receive the message