Forgot to say about my router. My router is in the same network with the
other computers,
it is working only as firewall to the internet. So for the multicasting
inside my network this is the usual workstation.
Mike Mestnik wrote:
--- Oleg Butorin [EMAIL PROTECTED] wrote:
Mike Mestnik wrote:
Mike Mestnik wrote:
I'm not an expert on MC, but I'd think 224.0.0.1 would be routed to
your
default route. Then the pkt would get multicasted and you would receve
multiple responces.
Yes, but I received responces from the systems where multicasting
disabled in the kernel.
--- Oleg Butorin [EMAIL PROTECTED] wrote:
Mike Mestnik wrote:
I'm not an expert on MC, but I'd think 224.0.0.1 would be routed to
your
default route. Then the pkt would get multicasted and you would
receve
multiple responces.
Yes, but I received responces
Please read Multicast-HOWTO.gz! Especially:
...
1.1. What is Multicast.
Multicast is... a need. Well, at least in some scenarios. If you have
information (a lot of information, usually) that should be transmitted
to various (but usually not all) hosts over an internet, then
Multicast is the
--- Oleg Butorin [EMAIL PROTECTED] wrote:
Mike Mestnik wrote:
I'm not an expert on MC, but I'd think 224.0.0.1 would be routed to
your
default route. Then the pkt would get multicasted and you would receve
multiple responces.
Yes, but I received responces from the systems where
Theodore Knab wrote:
Actually, this set of find commands will work better:
find /proc/net -name '*cast* -print -exec cat {} ';'
find /proc/sys -name '*cast* -print -exec cat {} ';'
Thank you for the answer.
I didn't find anything. And the question is: why it is working, when it
is disabled in the
Mike Mestnik wrote:
I'm not an expert on MC, but I'd think 224.0.0.1 would be routed to your
default route. Then the pkt would get multicasted and you would receve
multiple responces.
Yes, but I received responces from the systems where multicasting
disabled in the kernel.
IIRC kernel level
Hello all,
I have two linux debian systems, one with kernel 2.2.18, another with 2.4.20.
Both kernels have option IP: multicasting DISABLED. However
multicasting is working and both systems answered if I ping 224.0.0.1,
and multicast programs are working! The question is: why this option
IP:
Check to see if the kernel switches are on (1) or off (0):
find /proc/net -name '*cast*
find /proc/sys -name '*cast*'
On 15/10/04 15:20 +0400, Oleg Butorin wrote:
Hello all,
I have two linux debian systems, one with kernel 2.2.18, another with
2.4.20.
Both kernels have option IP:
Actually, this set of find commands will work better:
find /proc/net -name '*cast* -print -exec cat {} ';'
find /proc/sys -name '*cast* -print -exec cat {} ';'
On 15/10/04 10:36 -0400, Theodore Knab wrote:
Check to see if the kernel switches are on (1) or off (0):
find /proc/net -name
I'm not an expert on MC, but I'd think 224.0.0.1 would be routed to your
default route. Then the pkt would get multicasted and you would receve
multiple responces.
IIRC kernel level MC support is only for if you want to be on Mbone, not
if you want to use it as a client/server.
--- Oleg Butorin
11 matches
Mail list logo
