Hi,
can some of you help me to solve the following problem?
I'm using IEEE DIS protocol, that use UDP broadcast packets to send protcol
messages (PDUs).
The host that receive the messages has 2 network interfaces:
eth0 Link encap:Ethernet HWaddr 00:0C:29:8D:E3:19
inet addr:192.168.216.5 Bcast:192.168.216.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11706 errors:0 dropped:0 overruns:0 frame:0
TX packets:52495 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3693932 (3.5 Mb) TX bytes:19496318 (18.5 Mb)
Interrupt:10 Base address:0x1400
eth1 Link encap:Ethernet HWaddr 00:0C:29:8D:E3:23
inet addr:195.167.216.10 Bcast:195.167.216.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:44734 errors:0 dropped:0 overruns:0 frame:0
TX packets:255 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8840102 (8.4 Mb) TX bytes:37792 (36.9 Kb)
Interrupt:9 Base address:0x1480
I have bound a socket to the broacast address 192.168.216.255, that I use
for DIS messages (my code is c++ with qt 3.1.2 libraries, on a Red Hat ES 3
Linux, 2.4.21-4.EL kernel, Intel Platform).
The problem is that if a host on the network send a DIS packet to the
address 192.168.216.255, even if the socket is bound only to this address
(related to eth0 interface), I receive 2 messages, because the packet
arrives also to the eth1 interface even if this is not working in
promiscuous mode.
This results in a duplication of the packet read, a duplication of the ACKs
etc.....
I think that this is a strange behaviour of the OS.
The solution that I found is to set the SO_BINDTODEVICE option to receive
only packets on the eth0 interface, but I don't like this solution also
because this require administrative priviledges.
Can you tell me if this is a right behaviour of the system or it is a
kernel(?) bug?
Does it exist another solution to the problem?
Thank you very much.
Fulvio Carucci
Italy
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
