Re: [Omuscd-general] [Omuscd-devel] Network address multicast issues - HELP! :)

[Wes W. <wes...@gm...>]

Thanks, I was having a problem with an interface driver, however, I am still
confused as to how I am supposed to get all my nodes listening to multicast
address 239.192.0.1:1334 since it is quasi-hard coded. I can't assign the
nodes addresses to the subnet, and the nodes consider the address
unreachable (and for seemingly good cause... there is no way to route to it
legally).

Sincerely,
Wes Wagner


On 6/16/07, g4sra <g4...@ya...> wrote:
>
> Wes Wagner wrote:
> > I have a 2.6.17 openmosix AMD64 kernel and a AMD64 build of omuscd.
> >
> > My issue is that it attempts to multicast to the default address of
> > 239.192.0.1:1334 <http://239.192.0.1:1334> - but that is unreachable.
> > My two nodes I am trying to connect up are connected by a layer 2 only
> > gigabit switch.
> >
> > What am I missing from an installation standpoint toget these systems
> > speaking with each other?
> >
> > Thanks -
> >
> > -Wes Wagner
> > ------------------------------------------------------------------------
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Omuscd-devel mailing list
> > Omu...@li...
> > https://lists.sourceforge.net/lists/listinfo/omuscd-devel
> >
> Hi Wes, I don't quite follow your email.
>
> If you mean "omuscd" is reporting that the multicast network
> (239.192.0.1) is unreachable -
> It can't figure out which network device interface (eth0, eth1, etc) it
> needs to use, this can happen if you do not have a default route
> configured. You can resolve this issue either by creating a default
> route ("route add default eth0", or whatever) or by specifying the
> network device interface for omuscd to use as an argument. If you choose
> the latter, remember that specifying any argument will turn off the
> debug defaults (and omuscd will detach from the console), probably not
> what you want, you must specify all options you want.
> eg "omuscd -n -p -l127 -i eth0"
>
> I will amend the FAQ to include this information - thanks for raising my
> awareness to it's omission.
> If this does not solve your problem, please raise it again.
>
> N.B the advantages of porting omuscd to 64bit (due to the nature of the
> beast) are insignificant, I  am currently prioritizing development of
> openMosix itself (on i386) over omuscd, which is well ahead of the game
> in functionality.
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Omuscd-general mailing list
> Omu...@li...
> https://lists.sourceforge.net/lists/listinfo/omuscd-general
>