Detlef wrote: " So what you want is to bind to 192.168.2.1 only, and still get broadcasts as well as routed packets. Right now, I just hacked the code in net/ipv4/udp.c: udp_v4_mcast_next() to get the broadcasts even when not bound to INADDR_ANY, but I plan to introduce a specific sockopt for this behaviour. " I think that would make a lot of sense, a sockopt would not really damage anything that depends on the current behavior. I don't see this specific problem in any RFCs....so I don't think there really is an actual hard standard...it's kind of up in the air how any OS wants to implement it, it seems? I was digging around, it looks like I can get identical behavior to windows by binding to INADDR_ANY, and using setsockopt() to bind to the specific interface, like others have said. I'm able to receive all broadcasts to any ip, and sending outgoing packets still get tagged with the lan ip according to my packet sniffer. I might have to have it filter out packets from the same interface so it doesn't receive it's own packets...I think windows does this if binded to the lan IP, but I'd have to double check to confirm.... Am I incorrect in any of these assumptions? I would definitely support a patch though for this, it's going to be a fair amount of code to implement the proper workaround in wine. - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
