This is a multi-part message in MIME format.
------=_NextPart_000_0022_01C1567F.F0BAE4E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello Theo,
I'm testing out my NT Backhand Broadcaster and I think I may have =
uncovered some bugs in mod backhand. Here's what I have experienced.
1) If I am multicasting data from machine 1, and I specify accept for =
that multicast address and port on machine 2, but do not multicast to =
that IP from machine 2 then machine 2 never gets the multicast data from =
machine 1.
2) If I on machine 2 I multicast to the network, but DO NOT specify to =
accept that address on machine 2, it still gets accepted.
3) If there are no multicast directives the apache server will not serve =
any web pages. ( this could happen if everything were backhanded)
4) if there are no accept directives the apache server will not serve =
any web pages. (this could happen if we are only broadcasting our stats =
and not backhanding to others)
4) if multicasting on machine 2, to a multicast address and accepting =
only from that, or any other multicast address on machine 2. Machine 1 =
is broadcasting on the network segment, machine 2 still gets stats. =
(i.e. machines are on 192.168.0.x, machine 2 accepting stats from =
225.220.221.20:4555 machine 1 broadcasting to 192.168.0.255 machine 2 =
gets stats of machine 1 even though it should not accept!)
5) if machine 2 was receiving stats from machine 1, machine 1 went down, =
and it's hostname changed but IP address is still the same the old =
hostname will be displayed by backhand page.
I can reproduce these errors 100% of the time.
I have confirmed the data is actually getting to machine 2 by using a =
packet sniffer on machine 2.
Also, using the packet sniffer I have noticed packets from Linux / =
backhand are exactly the same as from my NT implementation with 2 =
exceptions. The TTL for broadcast packets is 128 from NT, 64 from =
linux. Packets from Linux have DF (Don't Fragment) flag set, packets =
from NT do not. Any idea how I can change these two items on NT so they =
perfectly match linux? I don't really think it matters too much because =
the packets are so small they will never be fragmented, and the TTL =
doesn't matter too much for broadcast (not multicast).
Thanks
Rob
------=_NextPart_000_0022_01C1567F.F0BAE4E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello Theo,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2> I'm testing out my =
NT Backhand=20
Broadcaster and I think I may have uncovered some bugs in mod =
backhand. =20
Here's what I have experienced.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>1) If I am multicasting data from =
machine 1, and I=20
specify accept for that multicast address and port on machine 2, but do =
not=20
multicast to that IP from machine 2 then machine 2 never gets the =
multicast data=20
from machine 1.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>2) If I on machine 2 I multicast to the =
network,=20
but DO NOT specify to accept that address on machine 2, it still gets=20
accepted.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>3) If there are no multicast directives =
the apache=20
server will not serve any web pages. ( this could happen if everything =
were=20
backhanded)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>4) if there are no accept directives =
the apache=20
server will not serve any web pages. (this could happen if we are only=20
broadcasting our stats and not backhanding to others)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>4) if multicasting on machine 2, to a =
multicast=20
address and accepting only from that, or any other multicast address on =
machine=20
2. Machine 1 is broadcasting on the network segment, machine 2 =
still gets=20
stats. (i.e. machines are on 192.168.0.x, machine 2 accepting =
stats from=20
225.220.221.20:4555 machine 1 broadcasting to 192.168.0.255 machine 2 =
gets stats=20
of machine 1 even though it should not accept!)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>5) if machine 2 was receiving stats =
from machine 1,=20
machine 1 went down, and it's hostname changed but IP address is still =
the same=20
the old hostname will be displayed by backhand page.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I can reproduce these errors 100% of =
the=20
time.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I have confirmed the data is actually =
getting to=20
machine 2 by using a packet sniffer on machine 2.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Also, using the packet sniffer I have =
noticed=20
packets from Linux / backhand are exactly the same as from my NT =
implementation=20
with 2 exceptions. The TTL for broadcast packets is 128 from NT, =
64 from=20
linux. Packets from Linux have DF (Don't Fragment) flag set, =
packets from=20
NT do not. Any idea how I can change these two items on NT so they =
perfectly match linux? I don't really think it matters too much =
because=20
the packets are so small they will never be fragmented, and the TTL =
doesn't=20
matter too much for broadcast (not multicast).</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Rob</FONT></DIV></BODY></HTML>
------=_NextPart_000_0022_01C1567F.F0BAE4E0--
------=_NextPart_000_0022_01C1567F.F0BAE4E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello Theo,
I'm testing out my NT Backhand Broadcaster and I think I may have =
uncovered some bugs in mod backhand. Here's what I have experienced.
1) If I am multicasting data from machine 1, and I specify accept for =
that multicast address and port on machine 2, but do not multicast to =
that IP from machine 2 then machine 2 never gets the multicast data from =
machine 1.
2) If I on machine 2 I multicast to the network, but DO NOT specify to =
accept that address on machine 2, it still gets accepted.
3) If there are no multicast directives the apache server will not serve =
any web pages. ( this could happen if everything were backhanded)
4) if there are no accept directives the apache server will not serve =
any web pages. (this could happen if we are only broadcasting our stats =
and not backhanding to others)
4) if multicasting on machine 2, to a multicast address and accepting =
only from that, or any other multicast address on machine 2. Machine 1 =
is broadcasting on the network segment, machine 2 still gets stats. =
(i.e. machines are on 192.168.0.x, machine 2 accepting stats from =
225.220.221.20:4555 machine 1 broadcasting to 192.168.0.255 machine 2 =
gets stats of machine 1 even though it should not accept!)
5) if machine 2 was receiving stats from machine 1, machine 1 went down, =
and it's hostname changed but IP address is still the same the old =
hostname will be displayed by backhand page.
I can reproduce these errors 100% of the time.
I have confirmed the data is actually getting to machine 2 by using a =
packet sniffer on machine 2.
Also, using the packet sniffer I have noticed packets from Linux / =
backhand are exactly the same as from my NT implementation with 2 =
exceptions. The TTL for broadcast packets is 128 from NT, 64 from =
linux. Packets from Linux have DF (Don't Fragment) flag set, packets =
from NT do not. Any idea how I can change these two items on NT so they =
perfectly match linux? I don't really think it matters too much because =
the packets are so small they will never be fragmented, and the TTL =
doesn't matter too much for broadcast (not multicast).
Thanks
Rob
------=_NextPart_000_0022_01C1567F.F0BAE4E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello Theo,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2> I'm testing out my =
NT Backhand=20
Broadcaster and I think I may have uncovered some bugs in mod =
backhand. =20
Here's what I have experienced.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>1) If I am multicasting data from =
machine 1, and I=20
specify accept for that multicast address and port on machine 2, but do =
not=20
multicast to that IP from machine 2 then machine 2 never gets the =
multicast data=20
from machine 1.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>2) If I on machine 2 I multicast to the =
network,=20
but DO NOT specify to accept that address on machine 2, it still gets=20
accepted.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>3) If there are no multicast directives =
the apache=20
server will not serve any web pages. ( this could happen if everything =
were=20
backhanded)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>4) if there are no accept directives =
the apache=20
server will not serve any web pages. (this could happen if we are only=20
broadcasting our stats and not backhanding to others)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>4) if multicasting on machine 2, to a =
multicast=20
address and accepting only from that, or any other multicast address on =
machine=20
2. Machine 1 is broadcasting on the network segment, machine 2 =
still gets=20
stats. (i.e. machines are on 192.168.0.x, machine 2 accepting =
stats from=20
225.220.221.20:4555 machine 1 broadcasting to 192.168.0.255 machine 2 =
gets stats=20
of machine 1 even though it should not accept!)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>5) if machine 2 was receiving stats =
from machine 1,=20
machine 1 went down, and it's hostname changed but IP address is still =
the same=20
the old hostname will be displayed by backhand page.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I can reproduce these errors 100% of =
the=20
time.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I have confirmed the data is actually =
getting to=20
machine 2 by using a packet sniffer on machine 2.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Also, using the packet sniffer I have =
noticed=20
packets from Linux / backhand are exactly the same as from my NT =
implementation=20
with 2 exceptions. The TTL for broadcast packets is 128 from NT, =
64 from=20
linux. Packets from Linux have DF (Don't Fragment) flag set, =
packets from=20
NT do not. Any idea how I can change these two items on NT so they =
perfectly match linux? I don't really think it matters too much =
because=20
the packets are so small they will never be fragmented, and the TTL =
doesn't=20
matter too much for broadcast (not multicast).</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Rob</FONT></DIV></BODY></HTML>
------=_NextPart_000_0022_01C1567F.F0BAE4E0--