<div dir="ltr"><br><br><div class="gmail_quote">On Mon, Sep 15, 2008 at 11:51 AM, Kevin Fries <span dir="ltr"><<a href="mailto:kfries@cctus.com">kfries@cctus.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;"> <br> You can also try, though I have never seen this work in a wireless network, setting your desktop's netmask to /22 (<a href="http://255.255.252.0" target="_blank">255.255.252.0</a>).  Again, this is one of those areas where theory meets actuality in a ugly game of "but why won't this work, it should".  </blockquote> <div><br>Okay, I finally got around to try this and it's a no go. I set the <a href="http://192.168.1.1">192.168.1.1</a> router's subnet to <a href="http://255.255.252.0">255.255.252.0</a> and I can't ping router 2 on <a href="http://192.168.2.1">192.168.2.1</a> from a computer connected directly (wired) to router 1. Is this what you mean by "should but doesn't". The dd-wrt firmware is supposed to give you a semi-professional router. Do I need to change the subnet on my desktop too? That's not an option with dhcp so would I have to use a static ip on the desktop?<br> <br>Thanks.<br></div></div><br>-- <br>Jim (Ubuntu geek extraordinaire)<br>----<br>Please avoid sending me Word or PowerPoint attachments.<br>See <a href="http://www.gnu.org/philosophy/no-word-attachments.html">http://www.gnu.org/philosophy/no-word-attachments.html</a><br> </div>