# Bind at (225-239).0.0.1

**URL:** <https://forums.digi.com/t/bind-at-225-239-0-0-1/5769>\
**Category:** NET+OS\
**Created:** [February 27, 2004, 1:42pm UTC](https://forums.digi.com/t/bind-at-225-239-0-0-1/5769 "2004-02-27T13:42:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cassius1](https://avatars.discourse-cdn.com/v4/letter/c/e36b37/32.png) [@cassius1](https://forums.digi.com/u/cassius1)\
**Post date:** [February 27, 2004, 1:42pm UTC](https://forums.digi.com/t/bind-at-225-239-0-0-1/5769/1 "2004-02-27T13:42:28Z")

</div>

I have faced problems listening at sockets bound a multicast address. So, I decide to use your example application as model to test the multicast. This program is attached to this message. When I bind at multicast addresses 225.0.0.1, 226.0.0.1, …, 239.0.0.1, the tcp/ip stack don’t call the eth\_ioctl routine, and didn’t register the address at the rash table. Consequently, the Net50 isn’t able to receive any packet at this address. I follow the setsockopt routine, and it call eth\_ at arp\_mult\_add, after return from arp\_mult\_add. I wasn’t able to go futher, once I haven’t the sources. I am doing something wrong, I mean, doing a conceptual mistake? If not, someone could check this? Thansks,