No subject


Thu May 3 16:06:15 ADT 2007


share network segment basically. So you maybe able to get a MAC address for
the box and provide that information to Eastlink so they can investigate it.
Though they should be able to trace it by the DHCP responses themselves.

For you solution, you could just change the network mask from
255.255.255.255 to one that only responses to 24.x.x.x. I will let you
google how to determine the network mask.

On Feb 1, 2008 10:48 AM, Gerald <linux at zdoit.airpost.net> wrote:

> Greg Hamilton wrote:
> . . . .
> > If you're worried about DNS, run named in cache mode and point it at
> whatever
> > DNS server you want. resolv.conf can then point to 127.0.0.1 and you
> should
> > be well.
> >
> > Best regards,
> >
> > Greg
>
> Greg,
>
> That's a good idea. Thanks
>
> --
> Gerald
> _______________________________________________
> nSLUG mailing list
> nSLUG at nslug.ns.ca
> http://nslug.ns.ca/cgi-bin/mailman/listinfo/nslug
>



-- 
Mark Lane, CET <lmlane at gmail.com>

------=_Part_597_24806443.1201962941356
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I quickly glanced over this thread and I think the problem is outside your house. It appears that when asking for an IP address that sometimes the router is going to a 10.6.x.x address instead of 24.x.x.x address that Eastlink uses. <br>
<br>It have seen this with services that require a login before giving out a public IP like Bell Sympatico but most cable companies don&#39;t do this. That suggests that your router is getting a response from an alternate DHCP server than Eastlink&#39;s. <br>
<br>Either someone has set up a system or device incorrectly, maliciously or it&#39;s some internet worm running on a hacked Windows box. I expect you could hack a Windows Box if you gave it false network addresses fairly easily. <br>
<br>From what I know of cable networks, everyone in a given area is on same share network segment basically. So you maybe able to get a MAC address for the box and provide that information to Eastlink so they can investigate it. Though they should be able to trace it by the DHCP responses themselves.<br>
<br>For you solution, you could just change the network mask from <a href="http://255.255.255.255">255.255.255.255</a> to one that only responses to 24.x.x.x. I will let you google how to determine the network mask.<br><br>
<div class="gmail_quote">On Feb 1, 2008 10:48 AM, Gerald &lt;<a href="mailto:linux at zdoit.airpost.net">linux at zdoit.airpost.net</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Greg Hamilton wrote:<br>. . . .<br><div class="Ih2E3d">&gt; If you&#39;re worried about DNS, run named in cache mode and point it at whatever<br>&gt; DNS server you want. resolv.conf can then point to <a href="http://127.0.0.1" target="_blank">127.0.0.1</a> and you should<br>
&gt; be well.<br>&gt;<br>&gt; Best regards,<br>&gt;<br>&gt; Greg<br><br></div>Greg,<br><br>That&#39;s a good idea. Thanks<br><br>--<br><font color="#888888">Gerald<br></font><div><div></div><div class="Wj3C7c">_______________________________________________<br>
nSLUG mailing list<br><a href="mailto:nSLUG at nslug.ns.ca">nSLUG at nslug.ns.ca</a><br><a href="http://nslug.ns.ca/cgi-bin/mailman/listinfo/nslug" target="_blank">http://nslug.ns.ca/cgi-bin/mailman/listinfo/nslug</a><br></div>
</div></blockquote></div><br><br clear="all"><br>-- <br>Mark Lane, CET &lt;<a href="mailto:lmlane at gmail.com">lmlane at gmail.com</a>&gt;<br>

------=_Part_597_24806443.1201962941356--


More information about the nSLUG mailing list