(forced commit for more info on the previous change)

Browse Source

According to RFC 1112, which deals with multicasting, an application must
specify the interface on which it wished to send a multicast packet. In the
absence of such an interface, a default is selected.

Previous behavior in ip_output.c erroneously checked for a route to the
destination multicast address, rejecting the packet if none existed.

Applications got around this with a FAQ recommending a 224.0.0.0/29 route
to loopback. This worked because the multicast code in ip_output.c discards
route information if an interface was selected.

The previous commit skips the route check in the case where a multicast packet
is being send to an application-defined interface.

The only change in behavior, if no bugs were introduced, is the lack of
rejection of a multicast packet for which no route exists sent to an
application-defined interface.

MFC after:	2 weeks

...

This commit is contained in:

Daniel C. Sobral 2001-07-17 21:00:07 +00:00

parent 6c56da4a27

commit 7d90ae7b37

Notes: svn2git 2020-12-20 02:59:44 +00:00

svn path=/head/; revision=79836

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Show Stats Download Patch File Download Diff File Expand all files Collapse all files

Diff Content Not Available