<div class="gmail_quote">On Tue, Jun 2, 2009 at 11:15 PM, Brian Pitts <span dir="ltr"><<a href="mailto:brian@polibyte.com">brian@polibyte.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Marc Ferguson wrote:<br>
> My guess is it's my router. Before we moved into our new home, the Cable<br>
> modem and my router both had the same IP scheme (192.168.1.x). We've<br>
> moved into a town house and we have DSL with AT&T. When I did the<br>
> initial setup, my modem as the IP Address of 192.168.1.254, but my<br>
> router has an internet port of 192.168.1.2, but a lan port as 10.0.0.1.<br>
> The router is also acting as a DCHP, so the other computers have a<br>
> 10.0.0.x scheme.<br>
><br>
> I found that extremely odd. So; I tried to give the lan port a<br>
> 192.168.1.x scheme and it killed everything. I could no longer gain<br>
> access to the router. I had to reset it and start over. I think there's<br>
> a serious lag with the router having to convert 10.0.0.x packets to<br>
> 192.168.0.x packets in Linux. Can anyone shed some light? Thanks.<br>
<br>
</div>First off, this isn't the problem. You can see this by plugging your<br>
"clone machine" directly into your modem.<br>
<br>
However, being behind two layers of NAT is a pain. You need to put your<br>
modem in bridge mode. Search the ALE archive for extensive discussion of<br>
this.<br>
<font color="#888888"><br>
--<br>
All the best,<br>
Brian Pitts<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
</font></blockquote></div><br>Thanks.<br clear="all"><br>-- <br>Marc F.<br><br>"When life gives me lemons... I make Linuxaide, hmm good stuff!"<br><br>