From owner-freebsd-net Wed Aug 18 23:23: 1 1999 Delivered-To: freebsd-net@freebsd.org Received: from inet-vrs-02.microsoft.com (mail2.microsoft.com [131.107.3.124]) by hub.freebsd.org (Postfix) with SMTP id 8CFE3150BD for ; Wed, 18 Aug 1999 23:22:57 -0700 (PDT) (envelope-from gchung@microsoft.com) Received: from 157.54.9.104 by inet-vrs-02.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 18 Aug 1999 23:21:28 -0700 (Pacific Daylight Time) Received: by INET-IMC-02 with Internet Mail Service (5.5.2448.0) id ; Wed, 18 Aug 1999 23:21:28 -0700 Message-ID: From: George Chung To: George Chung , 'Mike Nowlin' Cc: "'freebsd-net@freebsd.org'" Subject: RE: on dual-homed machine, how to specify outgoing interface to s end multicast packets Date: Wed, 18 Aug 1999 23:21:25 -0700 X-Mailer: Internet Mail Service (5.5.2448.0) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org After some digging, I tried the following and it seemed to work, although I can't say that I know exactly what's going on: route add -net 225.0.0.1 -netmask 0xF0000000 -interface 10.100.100.100 Is it the case that since this is a "fake" network with no actual router, that I need to manually add entries to the routing table? How do I do this automagically? TIA, George -----Original Message----- From: George Chung [mailto:gchung@microsoft.com] Sent: Wednesday, August 18, 1999 10:47 PM To: 'Mike Nowlin' Cc: 'freebsd-net@freebsd.org' Subject: RE: on dual-homed machine, how to specify outgoing interface to s end multicast packets you're right, I can't ping the address. so how do I fix that?! :-) -----Original Message----- From: Mike Nowlin [mailto:mike@argos.org] Sent: Wednesday, August 18, 1999 10:27 PM To: George Chung Cc: 'freebsd-net@freebsd.org' Subject: Re: on dual-homed machine, how to specify outgoing interface to send multicast packets > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message