Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 Aug 1999 23:21:25 -0700
From:      George Chung <gchung@microsoft.com>
To:        George Chung <gchung@microsoft.com>, 'Mike Nowlin' <mike@argos.org>
Cc:        "'freebsd-net@freebsd.org'" <freebsd-net@FreeBSD.ORG>
Subject:   RE: on dual-homed machine, how to specify outgoing interface to s end multicast packets
Message-ID:  <C35556591D34D111BB5600805F1961B910ECC112@RED-MSG-47>

next in thread | raw e-mail | index | archive | help
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




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