subnet masks

I am not a linux user, but I need help. I have 2 routers, a linksys
HPNA router and my DSL modem with a built in router. I want to use the
DSL modem as a router, and the linksys HPNA router as a bridge between
ethernet and HPNA (it can), except the linksys router needs a IP
address. My lan is currently using 192.168.1.*, and I have the
linksys's lan side perminently set to 192.168.1.254, but I want to set
it to 192.168.2.1 so I dont run into a chance of DHCP overlaping into
that IP. If I set the linksys as 192.168.2.1, I can only access it if
my comptuer's IP is 192.168.2.* but then my dsl modem doesnt give me
internet access. All of these routers/modems are on the same physical
ethernet network. I have a feeling this has something to do with subnet
masks, so which subnet mask should I use for 192.168.1.* and
192.168.2.* computers to talk?

On 7 Mar 2005 18:16:23 -0800, (E-Mail Removed) <(E-Mail Removed)> wrote:
> I am not a linux user, but I need help. I have 2 routers, a linksys
> HPNA router and my DSL modem with a built in router. I want to use the
> DSL modem as a router, and the linksys HPNA router as a bridge between
> ethernet and HPNA (it can), except the linksys router needs a IP
> address. My lan is currently using 192.168.1.*, and I have the
> linksys's lan side perminently set to 192.168.1.254, but I want to set
> it to 192.168.2.1 so I dont run into a chance of DHCP overlaping into
> that IP. If I set the linksys as 192.168.2.1, I can only access it if
> my comptuer's IP is 192.168.2.* but then my dsl modem doesnt give me
> internet access. All of these routers/modems are on the same physical
> ethernet network. I have a feeling this has something to do with subnet
> masks, so which subnet mask should I use for 192.168.1.* and
> 192.168.2.* computers to talk?

I guess you need to check if your dsl modem/router is, or can be, set to a
broader netmask than 255.255.255.0 on its LAN side (many are limited to
253 clients). Otherwise (as you discovered) the modem/router will ignore
any IPs outside of its 192.168.1.0/24 network. But even if the modem had
a netmask 255.255.0.0, it could be that your 192.168.2.* client PCs do not
have any route to the 192.168.1.* IP of the modem/router (if their
netmask is 255.255.255.0).

For example, a netmask 255.255.254.0 could cover an range between
192.168.0.0 network IP and 192.168.1.255 broadcast.

A netmask 255.255.252.0 could cover an range between 192.168.0.0 network
IP and 192.168.3.255 broadcast.