Linksys Routers problem with 255.255.254.0

Hello-

I work for a local ISP here in town. We recently changed our DHCP block
from a class C (255.255.255.0) to a C+1 (255.255.254.0). When the DHCP
migration started we slowly were seeing a few (5-10 out of 250)
customers having a problem with the new pool.

After some debate, we seem to have found that *some* of the Linksys
routers are having problems with being located in a different class C
from the Default Gateway, or are have a problem the the class C+1 block
all together. (I haven't been able to test which one of these theories
is correct because I don't have a router (other than the one in service)
that will hand out class C+1).

The model number that we have had the most problem with is the BEFSR41
(ver 2), but I have also had trouble with D-link DI-701 and BEFW11S4
(ver 4).

I have tried firmware upgrades and resets to no avail. Linksys claims
that these are small business and residential gateways and they don't
support the C+1 block (I think he was smoking crack or talking about the
LAN side) because if they adhere to the standard the WAN side should be
able to support a class A address, which it can because I tested it with
a 10.0.0.1 number and it worked, but I wasn't able the get the default
gateway out of the same class C block, ie if the 10.0.0.1 had a
dfgateway of 10.0.0.254 it was working, but I wasn't able to put the
default gateway at 10.0.1.254 to see if it would break because of some
configuration limitations of the router I was testing with. I did try
to assign the router statically out of the DHCP pool (I know this is a
no no, but...) and the router wouldn't accept the 255.255.254.0 netmask
saying it was an invalid netmask. I can't believe they did this!

Basically, I'm band-aiding the situation at this point by assigning some
static ip's out of a small block until I can come up with a *good* solution.

Has anyone heard of this problem, or experienced anything similar to
this. Any advice or comments would be appreciated.

Thanks

Ben

From: "Ben Wehrspann" <(E-Mail Removed)>

| Hello-
|
| I work for a local ISP here in town. We recently changed our DHCP block
| from a class C (255.255.255.0) to a C+1 (255.255.254.0). When the DHCP
| migration started we slowly were seeing a few (5-10 out of 250)
| customers having a problem with the new pool.
|
| After some debate, we seem to have found that *some* of the Linksys
| routers are having problems with being located in a different class C
| from the Default Gateway, or are have a problem the the class C+1 block
| all together. (I haven't been able to test which one of these theories
| is correct because I don't have a router (other than the one in service)
| that will hand out class C+1).
|
| The model number that we have had the most problem with is the BEFSR41
| (ver 2), but I have also had trouble with D-link DI-701 and BEFW11S4
| (ver 4).
|
| I have tried firmware upgrades and resets to no avail. Linksys claims
| that these are small business and residential gateways and they don't
| support the C+1 block (I think he was smoking crack or talking about the
| LAN side) because if they adhere to the standard the WAN side should be
| able to support a class A address, which it can because I tested it with
| a 10.0.0.1 number and it worked, but I wasn't able the get the default
| gateway out of the same class C block, ie if the 10.0.0.1 had a
| dfgateway of 10.0.0.254 it was working, but I wasn't able to put the
| default gateway at 10.0.1.254 to see if it would break because of some
| configuration limitations of the router I was testing with. I did try
| to assign the router statically out of the DHCP pool (I know this is a
| no no, but...) and the router wouldn't accept the 255.255.254.0 netmask
| saying it was an invalid netmask. I can't believe they did this!
|
| Basically, I'm band-aiding the situation at this point by assigning some
| static ip's out of a small block until I can come up with a *good* solution.
|
| Has anyone heard of this problem, or experienced anything similar to
| this. Any advice or comments would be appreciated.
|
| Thanks
|
| Ben

I don't think 255.255.254.0 is a proper sub-net mask.

I really don' think this is a Router issue at all. It is a TCP/IP issue and I suggest
reposting this in;
comp.protocols.tcp-ip


--
Dave
http://www.claymania.com/removal-trojan-adware.html
http://www.ik-cs.com/got-a-virus.htm