Archived from groups: alt.internet.wireless,comp.networks,comp.os.ms-windows.networking,comp.home.automation,comp.dcom.lans.ethernet (
More info?)
"wkearney99" <wkearney99@hotmail.com> wrote in
news:z8GdnYUWLu_iSkPdRVn-sQ@speakeasy.net:
>> I have a cable modem going into a wireless router with a printer port
>> and 4 ethernet ports.
>
>
> Many homes today have this. I've got one here. Actually I have more
> than two but for the sake of discussion...
>
>> can I just hookup another non wireless router to one of the ports on
>> the wireless router to increase the number of ports...
>
>
> Don't bother with this unless you already have the other unit. Just
> plug a switch in the dlink and cascade other devices off it. Just be
> sure not to cascade more than three levels deep.
>
>> I have the house wired for internet and need another 20 ports or so..
>> Sorry about not know all the terminolgy here..
>
> Get yourself a pair of 16 port switches. Or four 8 port switches.
> Just try to avoid daisy-chaining them as there are some ethernet
> latency issues that have to be avoided.
>
> If you try chaining another 'router' off the wireless unit you
> introduce several rather complex issues. There are some situations
> where you'd want the wireless set up as what's referred to as a DMZ.
> This is where the wireless network is considered not-secure and is
> isolated from the internal network. Setting up something like this is
> less-than-trivial (for most folks) and introduces a number of
> complicating factors. Namely the devices running on the wireless
> segment won't be able to see the stuff on the wired-side without some
> extra configuration efforts on both sides. I do this here, my
> wireless devices all speak IPsec and the wired router is specifically
> configured to recognize and pass their traffic to the wired-side. I
> wouldn't recommend this for most homeowners as it requires all the
> wireless devices to have IPsec loaded and be configured properly.
>
> The real trouble you run into is the home router devices have
> different levels of features. Most don't have the option to be
> configured for more sophisticated setups.
>
> I run things:
>
> ISP DSL into a DSL modem
> DSL modem into a NAT router
> switches off the NAT router
> IPSec vpn server on wired network
> wifi home router off a switch port
> various wifi devices with IPsec VPN.
>
> The wifi home router is configured to pass the IPsec VPN traffic to a
> specific IP address on the internal wired network. The outside NAT
> router is also configured for it (to allow connecting to the home
> network from work or travel). The internal network runs in one of the
> 192.168.0.0/24 subnet. The wifi network runs in another. The home
> NAT router has a special static route setup to handle using the IPsec
> server to speak back TO the wifi devices. Again, most people aren't
> going to take this many steps.
>
> When you try to chain one home router off another you end up with,
> essentially, double routing of NAT traffic. This can make for
> doubly-complicated setups for devices on the other side. The issue
> being the wired devices won't be able to "see" the wifi devices
> without extra static route setups. There's also the possibility that
> both devices might balk at trying to do so as many are hard-coded to
> use only non-routable networks.
>
> In short, your easiest solution might be to just hang a switch or two
> off the wifi router.
>
> -Bill Kearney
>
You can take a righteous router, switch or hub turn one vertical and
grease it up and stick it up you know where. <g>
Duane
Facebook
Twitter
Instagram