From owner-freebsd-net Wed Aug 18 22:30:13 1999 Delivered-To: freebsd-net@freebsd.org Received: from jason.argos.org (a1-3a123.neo.rr.com [24.93.180.123]) by hub.freebsd.org (Postfix) with ESMTP id 79D8914EA4 for ; Wed, 18 Aug 1999 22:30:05 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id BAA22334; Thu, 19 Aug 1999 01:26:53 -0400 Date: Thu, 19 Aug 1999 01:26:53 -0400 (EDT) From: Mike Nowlin To: George Chung Cc: "'freebsd-net@freebsd.org'" Subject: Re: on dual-homed machine, how to specify outgoing interface to send multicast packets In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 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