<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2448.0">
<TITLE>RE: [NTLUG:Discuss] Broadcast Storms</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Greg Edwards wrote:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Are both of your NIC settings on the same subnet? If both are on the</FONT>
<BR><FONT SIZE=2>> same subnet (ie 192.168.1.x) using the same broadcast address </FONT>
</P>
<P><FONT SIZE=2>Nope. We needed a machine to act as a router between different subnets. All we did to make it work is turn on packet forwarding and add several 'ifconfig eth0:xxx' statements. That part of it works great. However, after several good sugestions on this list and some research of our own, we're not so certain that this box is causing our problems. It is possible the errors/collisions/etc. we see reported from 'ifconfig eth0' are simply the result of *another* problem on the network.</FONT></P>
<P><FONT SIZE=2>> then there</FONT>
<BR><FONT SIZE=2>> could be a race condition trying to get control over the owner of the</FONT>
<BR><FONT SIZE=2>> response to a broardcast such as a clinet attemping to bind to an NIS</FONT>
<BR><FONT SIZE=2>> server.</FONT>
</P>
<P><FONT SIZE=2>That makes sense. Unfortunately that's not the case here.</FONT>
</P>
<P><FONT SIZE=2>--</FONT>
<BR><FONT SIZE=2>OSC, a subsidiary of Billing Concepts Corp., a NASDAQ listed Company, Symbol: "BILL"</FONT>
</P>
</BODY>
</HTML>