<div dir="ltr">well yes.... but something was wrong. So I got other instructions:<br> Connecting two (or more) SOHO broadband routers together<br><br>Note: The "primary" router can be an actual router, a software gateway like Microsoft Internet Connection Sharing, or a server connection that has the capability to supply more than one IP address using Dynamic Host Configuration Protocol (DHCP) server capability. No changes are made to the primary "router" configuration.<br>
<br>Step #1: Configure the IP address of the secondary router(s)<br><br> Configure the IP address of the secondary router(s) to be in the same subnet as the primary router, but out of the range of the DHCP server in the primary router. For instance, if the primary router's DHCP server assigns IP addresses 192.168.0.2 through 192.168.0.100 to computers or devices connecting to it, assign the secondary router 192.168.0.254 as it's IP address, 192.168.0.253 as the IP address for another router, etc. <br>
<br> Note: Do this first, as you will have to reboot the computer to connect to the router again for the remaining changes. <br><br>Step #2: Disable the DHCP server in the secondary router(s).<br><br> Consult the manual or user's guide for the secondary router(s) to locate the configuration area where the DHCP server can be disabled. <br>
<br>Step #3: Setup the wireless section<br><br> If configuring a secondary wireless router as a wi-fi access point, configure the router with the wireless settings you would normally use, if this secondary router were to be the primary router; channels, encryption, etc. Otherwise, you can skip this step. <br>
<br>Step #4: Connect the secondary router(s) to the primary router<br><br> Connect from the primary router's LAN port to one of the LAN ports on the secondary router. If there is no uplink port and neither of the routers have auto-sensing ports, use a cross-over cable. [You will not need a cross-over cable if one of the "routers" is a computer.] Leave the WAN port unconnected! <br>
<br><br><br></div><div class="gmail_extra"><br clear="all"><div>:-)~MIKE~(-:</div>
<br><br><div class="gmail_quote">On Sun, Aug 3, 2014 at 3:42 PM, sean <span dir="ltr"><<a href="mailto:sean.a.ritzler@gmail.com" target="_blank">sean.a.ritzler@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">Wasn't the previous solution to disable dhcp on the second router? Then of course it wouldn't give out the new addresses...</p><div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On Aug 3, 2014 3:33 PM, "Michael Havens" <<a href="mailto:bmike1@gmail.com" target="_blank">bmike1@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">well the deal is that I didn't want to run another cable from my router. My confusion isn't on getting it to work but rather the numbers that have been assigned from the second router. I was thinking that it might have to do with perhaps they had already been assigned ip addresses but the lfs computer was not previously assigned a number. Is it that the modem is handing out addresses until it gets to 192.168.0.125 and then the router takes over in giving addresses?<br>
</div><div class="gmail_extra"><br clear="all"><div>:-)~MIKE~(-:</div>
<br><br><div class="gmail_quote">On Sun, Aug 3, 2014 at 3:03 PM, Wayne Davis <span dir="ltr"><<a href="mailto:waydavis@centurylink.net" target="_blank">waydavis@centurylink.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<br>
<div>
<div>You DO NOT need to use another
router. One is sufficient and 200 feet of wire would not be a
problem. For stronger wireless, you COULD add another WIRED
access point to your network. In fact (I) do exactly that. I
have a AP near the front of the house, and another near the
back. I have about 30 "devices" on the network.... but ONE
router / DHCP box is quite sufficient for it all. Your issue
is more than likely multiple DHCP servers. For YOUR network,
that is probably not needed.<br>
<br>
<b> If you like, I will help you further via phone (MUCH MORE
EFFICIENT THAN TYPING) Private message me with your number.</b><br>
<br>
</div>
</div>
<br>
</div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div><br></div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div>
</div></div><br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div><br></div>