Bernd Eckenfels wrote: > > In article <47ed01bd0705021052t1a33a667uaf52a65c523eb5db@xxxxxxxxxxxxxx> you wrote: > > This doesn't seem right at all. If I bind a socket to my lan > > ip(192.168.0.8), I'm not getting broadcasts on 255.255.255.255. > > 255.255.255.255 is not 192.168.0.8. If you bind a socket to an address, you > only get packets to that address. I guess you want to bind to an interface > instead. Sometimes you don't want to bind to an interface, but to a stack. If you bind to the interface, you don't get packets that came in through another interface, but are routed to that stack. > > > I wrote a test program, binding to lan IP works on windows. Was > > something changed recently, or has it been like this for a while? > > It's causing some network games to not run properly. > > This never worked for Linux. FWIW, it worked in Linux 1.0 (long time ago). Detlef -- Detlef Vollmann vollmann engineering gmbh Linux and C++ for Embedded Systems http://www.vollmann.ch/ Linux for PXA270 Colibri module: http://www.vollmann.ch/en/colibri/ - 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
