Hello.
I have a question about configuring routed on a machine so that I can use it
for multicast routing. I have been looking at various information I found
on the Web and one of the things that it said needed to be done before
starting mrouted was to setup the route for the multicast address. On a
Linux page, it gave this command:
route add -net 224.0.0.0 netmask 240.0.0.0 dev eth0
Now, given that I am trying to do this on an imaginary, internal network (
192.168.0.*), and that I am trying to configure this with QNX 4.25 and
TCP/IP v.5.0, I was trying to figure out how to convert this to the QNX4
route command. The “dev eth0” command doesn’t appear to be translateable to
the QNX4 worlds, so how would one add an entry so that the mrouted daemon
will be able to run?
TIA.
Rodney Lott
route add -net 224.0.0.0 netmask 240.0.0.0 dev eth0
Now, given that I am trying to do this on an imaginary, internal network (
192.168.0.*), and that I am trying to configure this with QNX 4.25 and
TCP/IP v.5.0, I was trying to figure out how to convert this to the QNX4
route command. The “dev eth0” command doesn’t appear to be translateable
to
the QNX4 worlds, so how would one add an entry so that the mrouted daemon
will be able to run?
The route command should be the same, except interface names under QNX4 (and
other *NIX’s) are sometimes different. In this case eth0 should be en0 (or
en1 most likely). Do and ifconfig -a to show all your interfaces, and their
appropriate names.
\
Cheers,
Adam
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
Hi, Adam.
The QNX4 interface naming convention for network interfaces is not what I am
failing to understand -
it is the equivalent of the “dev” option in the Linux route command. The
route command under QNX4
is not exactly the same - it doesn’t use the dev specifier ( as I mentioned
previously ).
When I issue the command:
route add -net 224.0.0.0 -netmask 255.255.255.0 dev en1
I get the following error message: “dev: bad value” ( since dev is NOT a
valid option ).
So, since my initial viewing of the documentation didn’t indicate to me what
was the equivalent to the
“dev” option, then I would like to know what the equivalent way to do this
under QNX since it lacks
this option.
Thanks.
Rodney
“Adam Mallory” <amalloryNOSPAM@NOSPAMqnx.com> wrote in message
news:ajtrr1$r2e$1@nntp.qnx.com…
route add -net 224.0.0.0 netmask 240.0.0.0 dev eth0
Now, given that I am trying to do this on an imaginary, internal network
(
192.168.0.*), and that I am trying to configure this with QNX 4.25 and
TCP/IP v.5.0, I was trying to figure out how to convert this to the QNX4
route command. The “dev eth0” command doesn’t appear to be
translateable
to
the QNX4 worlds, so how would one add an entry so that the mrouted
daemon
will be able to run?
The route command should be the same, except interface names under QNX4
(and
other *NIX’s) are sometimes different. In this case eth0 should be en0
(or
en1 most likely). Do and ifconfig -a to show all your interfaces, and
their
appropriate names.
\
Cheers,
Adam
QNX Software Systems Ltd.
[ > amallory@qnx.com > ]
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net
The QNX4 interface naming convention for network interfaces is not what I
am
failing to understand -
it is the equivalent of the “dev” option in the Linux route command. The
route command under QNX4
is not exactly the same - it doesn’t use the dev specifier ( as I
mentioned
previously ).
Sorry, you post had the example with eth0 in it, and I was quickly skimming.
So, since my initial viewing of the documentation didn’t indicate to me
what
was the equivalent to the
“dev” option, then I would like to know what the equivalent way to do this
under QNX since it lacks
this option.
Actually, this is a BSDism (ie. the lack of dev option). You should be able
to specify the IP of the interface you wish to route multicast to instead.
As an alternative, you could also just setup a default route to that
interface, and multicast should just work (since it’ll go out the default
w/o any specific routes set). Of course this would only work if you have 1
multicast interface.
\
Cheers,
Adam
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
“Adam Mallory” <amalloryNOSPAM@NOSPAMqnx.com> wrote in message
news:aju17j$4b7$1@nntp.qnx.com…
Sorry, you post had the example with eth0 in it, and I was quickly
skimming.
No problems!
Actually, this is a BSDism (ie. the lack of dev option). You should be
able
to specify the IP of the interface you wish to route multicast to instead.
As an alternative, you could also just setup a default route to that
interface, and multicast should just work (since it’ll go out the default
w/o any specific routes set). Of course this would only work if you have
1
multicast interface.
Ok, I will try those things out.
Thanks, Adam.
Rodney