Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Aug 1999 01:26:53 -0400 (EDT)
From:      Mike Nowlin <mike@argos.org>
To:        George Chung <gchung@microsoft.com>
Cc:        "'freebsd-net@freebsd.org'" <freebsd-net@FreeBSD.ORG>
Subject:   Re: on dual-homed machine, how to specify outgoing interface to send multicast packets
Message-ID:  <Pine.LNX.4.05.9908190124210.22328-100000@jason.argos.org>
In-Reply-To: <C35556591D34D111BB5600805F1961B910ECC110@RED-MSG-47>

next in thread | previous in thread | raw e-mail | index | archive | help

> On a dual-homed machine, there is no "network" portion of the destination
> Class D address to make any kind of determination as to which outgoing
> interface to use.
> 
> So I make a call to
> 
> setsockopt(fd, IPPROTO_IP, IP_MULTICAST_IF, &inaddr, sizeof(struct
> in_addr));
> 
> I confirm that this call works. Plus I doublechecked by giving it a bogus
> inaddr, and it gave me errno 49 EADDRNOTAVAIL. However, when I try send a
> packet to "225.0.0.1", I get errno 65 EHOSTUNREACH.

First guess is that it's a routing problem...  Try pinging that address --
if you get a "route not available" (or similar message), that's probably
it.

(I'm too brain-fried right now to go into much more detail than that... :)
)

--mike



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.05.9908190124210.22328-100000>