[CoLoCo] changing subnet mask

[Jim Hutchinson]

On Wed, Sep 10, 2008 at 9:29 AM, Kevin Fries <kfries at cctus.com> wrote:

>
> Does this make sense so far?  I hope so.


Sort of...


>
> If I understand what you were trying to do, you did not want two network
> segments, but instead just wanted two physical WAP routers on the same
> network.  In order to do that, you need to go back to layer 2 of the OSI and
> realize that two WAP access points, with the same channel, and the same SSID
> will confuse the radio's in the client machines the same way that two
> computers with the same MAC address will confuse a wired network.  I think
> what you wanted was to leave the DHCP on, in the second WAP, and just create
> machines in a different range.  If I get what you wanted:


Well, what I wanted was two routers with DIFFERENT ssid and channel and
different subnets. Basically, I was trying to create two separate networks
that were not isolated on the LAN side. I wanted to be able to ssh between
them and use one computer to manage both routers. When my desktop is
connected to the "1" subnet, it cannot see the router or computers on the
"2" subnet. I was trying to figure out if a different subnet mask would
allow this to work.


>
> Router 1 -
>  Upstream -> Cable/DSL modem
>  Upstream Address -> assigned by the ISP
>  Local -> local network
>  Local Address -> Fixed at .1 or .254
>  DHCP Range -> 100 - 149
>  Channel -> 11
>  SSID -> MYNETWORK
>
> Router 2 -
>  Upstream -> Local Network
>  Upstream Address -> fixed at .3 or .252 (gateway = router 1)
>  Local -> Local Network
>  Local Address -> Fixed at .2 or .253
>  DHCP Range -> 150-200
>  Channel -> 9
>  SSID -> MYNETWORK


I think that is right but not sure what the "fixed at .1 or .254" or ".3 or
.252" lines mean. I have one router with a default gateway of
192.168.1.1and the other with
192.168.2.1. Both are serving DHCP and the .2 router is connected from a lan
port of the .1 into the WAN port of the .2. The ssids are different though.
This is working except I can't access computers on the .2 subnet or the
router from computers on the .1 network. That is what I'm trying to fix.


> Wireless clients can connect to either Router 1 or Router 2.  Either router
> still gets them into the same network.  Therefore, you can manage either
> router from either segment.  On router 2 you can allow management from the
> WAN (upstream) port which normally would not be a good idea, but is fine in
> this case because upstream is still your local network.


This only works upstream (i.e. from computers on the .2 network to computers
on the .1) but not vice versa. I can only ssh one way.


>
> If you want more detailed information, with lots of gobbly gook techno
> speak, look up OSI Model and Internet Protocol on Wikipedia.


I think the gobbly good techno speak so far is fine. No need for much more
until I wrap my brain around this :).


>
>
> Did this help?  Did I tell you what you were trying to figure out?


To a degree. I'm not there yet but thanks for trying.

-- 
Jim (Ubuntu geek extraordinaire)
----
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/ubuntu-us-co/attachments/20080914/d34dabd9/attachment.htm