Re: FW: [H] trying to setup a second WAP

2007-01-08 Thread j maccraw
Just a follow up, this link talks about this kind of
setup with the 
exception that they suggest slave router use DHCP to
get address from 
master. This IMHO, lacking a DHCP address reservation
for slave router, 
  would make it hard to know what address to connect
to slave router on 
from subnet 1 hence my suggestion to use static ip
from subnet 1 for 
slave's WAN port.

http://www.grc.com/nat/nats.htm



__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


Re: FW: [H] trying to setup a second WAP

2007-01-08 Thread j maccraw
Netmask's and routing are my achilies heel, so that
may not be right but 
essentially you've opened the subnet from a class c to
class B which is 
likely why you have routing working.

Could be you are missing a gateway setting on slave
router if you can't 
get out from subnet 2. Or you may still need a static
route so the 
subnet 1 can access subnet 2 clients which is why you
could not access 
slave router from a subnet 1 machine.

I'd use 2 subnets like this, 192.168.1.0 &
192.168.2.0.
1. Master router
   a. WAN, DHCP (assuming cable, otherwise PPOE for
DSL)
   b. LAN, 192.168.1.1/24
   c. LAN, DHCP, 192.168.1.100, "x" clients (whatever
you need on master)
   d. static route, 192.168.2.0/24 gateway 192.168.1.2

2. Slave router
   a. WAN, static 192.168.1.2/24
   b. WAN, gateway 192.168.1.1
   c. LAN, 192.168.2.1/24
   d. LAN, gateway 192.168.2.1 <- *may not need this*
   e. LAN, DHCP, 192.168.2.100, "y" clients (whatever
you need on slave)


So slave router would be on subnet 1 acting as gateway
& DHCP host for 
it's clients on subnet 2 that would gateway though it
to subnet 1 when 
they accessed IP outside of 192.168.2.0.

Been awhile, but I think this is how I had my VOIP
router setup on 
subnet 2 when I added VOIP last year.

Chris Klein wrote:
> So change the subnet on the master router to
255.255.252.0 but leave the IP
> as 192.168.1.1   and then the secondary router will
be 255.255.255.0 and
> 192.168.2.1?
> 
> 
> 
> 
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
Behalf Of j maccraw
> Sent: Sunday, January 07, 2007 9:57 PM
> To: The Hardware List
> Subject: Re: [H] trying to setup a second WAP
> 
> Likely then what you need is 255.255.252.0 mask if
the
> slave is 
> 192.168.2.1 & master 192.168.1.1.
> 
> If their same subnet, then you have a kludge by
> ignoring some of the 
> network bits.
> 
> 
> 
> Gary VanderMolen wrote:
>> In order to see both routers (and modem) config
> screens,
>> I had to set the subnet mask of the first router to
> 255.255.0.0.
>> Gary VanderMolen
>>
>>
>> ----- Original Message - 
>> From: "Chris Klein" <[EMAIL PROTECTED]>
>> To: "'The Hardware List'"
> 
>> Sent: Saturday, January 06, 2007 11:46 PM
>> Subject: FW: [H] trying to setup a second WAP
>>
>>
>>> It actually appears to be working now.  The first
> Linksys is giving out a
>>> 192.168.1.x IP address, and I can get to the
> internet.  I can open up the
>>> config properties for the first
router(192.168.1.1.
>  However, I can't reach
>>> the 192.168.2.1 router to make config changes. 
Are
> you able to reach yours?
>>
>>
> 
> __
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam
protection around 
> http://mail.yahoo.com 
> 
> 
> 

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


FW: [H] trying to setup a second WAP

2007-01-07 Thread Chris Klein

So change the subnet on the master router to 255.255.252.0 but leave the IP
as 192.168.1.1   and then the secondary router will be 255.255.255.0 and
192.168.2.1?




-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of j maccraw
Sent: Sunday, January 07, 2007 9:57 PM
To: The Hardware List
Subject: Re: [H] trying to setup a second WAP

Likely then what you need is 255.255.252.0 mask if the
slave is 
192.168.2.1 & master 192.168.1.1.

If their same subnet, then you have a kludge by
ignoring some of the 
network bits.



Gary VanderMolen wrote:
> In order to see both routers (and modem) config
screens,
> I had to set the subnet mask of the first router to
255.255.0.0.
> 
> Gary VanderMolen
> 
> 
> - Original Message - 
> From: "Chris Klein" <[EMAIL PROTECTED]>
> To: "'The Hardware List'"

> Sent: Saturday, January 06, 2007 11:46 PM
> Subject: FW: [H] trying to setup a second WAP
> 
> 
>> It actually appears to be working now.  The first
Linksys is giving out a
>> 192.168.1.x IP address, and I can get to the
internet.  I can open up the
>> config properties for the first router(192.168.1.1.
 However, I can't reach
>> the 192.168.2.1 router to make config changes.  Are
you able to reach yours?
> 
> 
> 

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 



Re: FW: [H] trying to setup a second WAP

2007-01-07 Thread j maccraw
I would assume the firewall on the slaved router would
filter the IANA 
subnet, but if it's getting IANA IP via DHCP though
it's WAN port from 
LAN port of master router then you'd think it would
just work.

Say that 3 time fast!

Also, I'd put the GS on the border with DD-WRT before
I'd put the older 
G version there. I'd definitely run DD-WRT on both
though with the 
internal slave running a static IP from the master's
subnet & leave 
slave's DHCP running serving a second subnet for it's
wireless clients.

Of course, here I would disable both DHCP servers
since I run a Win2K DC 
hosting DHCP & DNS which work together keeping my
local domain DNS straight.


Chris Klein wrote:
> H...didn't think about that.  And all of my
devices will get an IP
> address assigned to them from the first/main router,
correct?  I won't
> really have any devices plugged into the second one,
it's mainly just for
> wireless.
> 
> 
> I just tired it and it's not working.  Do you have
Linksys products at your
> house?  If so I have some specific
questions...nothing I try is working
> 
> -Original Message-
> [mailto:[EMAIL PROTECTED] On
Behalf Of Gary VanderMolen
> 
> You need to plug the cable from the WRT54G into a
LAN (not WAN)
> port on the secondary router. I have a similar setup
in my house.
> In essence that turns the WRT54GS into a switch
rather than a router.


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


FW: [H] trying to setup a second WAP

2007-01-06 Thread Chris Klein

It actually appears to be working now.  The first Linksys is giving out a
192.168.1.x IP address, and I can get to the internet.  I can open up the
config properties for the first router(192.168.1.1.  However, I can't reach
the 192.168.2.1 router to make config changes.  Are you able to reach yours?


Thanks again,

Chris




FW: [H] trying to setup a second WAP

2007-01-06 Thread Chris Klein

H...didn't think about that.  And all of my devices will get an IP
address assigned to them from the first/main router, correct?  I won't
really have any devices plugged into the second one, it's mainly just for
wireless.


I just tired it and it's not working.  Do you have Linksys products at your
house?  If so I have some specific questions...nothing I try is working

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gary VanderMolen
Sent: Sunday, January 07, 2007 1:39 AM
To: The Hardware List
Subject: Re: [H] trying to setup a second WAP

You need to plug the cable from the WRT54G into a LAN (not WAN)
port on the secondary router. I have a similar setup in my house.
In essence that turns the WRT54GS into a switch rather than a router.

Gary VanderMolen


- Original Message - 
>I have a WRT54G connected to my cable modem.  It provides WPA2 Wireless G
> access to several devices in my apartment, along with a cat 5 connection
to
> my main computer.
> 
> I'm connecting a Linksys WRT54GS, to the 54G.  I want the 54GS to provide
> WEP wireless to 2 devices in my apartment that do not support WPA2.  They
> are basically PVRs for all intents and purposes.
> 
> I have a cable from the wan port of the 54GS, connected to port #2 on the
> 54G.  
> 
> I've set the IP address for the 54GS to 192.168.2.1
> 
> The IP address of my main router has always been 192.168.1.1
> 
> I turned off DHCP on the 54GS, figuring all devices that connect will get
an
> IP address from router #1.
> 
> However, I can't see the new 54GS at all.  I can't ping it, I can't reach
> it.  Any help here on what I'm missing?