How to avoid subnet with JWNR2010v5

> [...] I don't need to be reminded that an Ethernet cable has two ends.

   So you say, but I still don't see where you revealed where the two
ends of your "the LAN cable" actually go.  I have what might be called a
"the LAN cable" here, too, but you have no idea what mine might connect
to what.

> 8. I've tried to change the IP address for the Netgear box from
> 192.168.1.1 to 192.168.1.253,
> ERROR: I cannot change any setting at all, I just a get a "403
> Forbidden" frame.

   Any "403" error from these gizmos is evidence of a firmware defect.

> downgraded firmware to v54 -- everything works as expected now!

   As it says in the guide, "What could go wrong?"  (You seem to have
expanded the envelope a little on that one.)

> So you say, but I still don't see where you revealed where the two

> ends of your "the LAN cable" actually go. I have what might be called a

> "the LAN cable" here, too, but you have no idea what mine might connect

> to what.

there is a difference between asking for more information and mocking the poster.

you can always ask to be explicit, but if you treat people like idiots they will never like it, whether they are idiots or not.

I had a LAN cable going from either the WAN port or a LAN port of the Netgear (depending on the try, as I explained) and it was going to the LAN port of my main router.

that was evident based on what I said the behavior was on LAN/LAN connections (that is, wired clients were getting the IP address from the DHCP of the main router, etc).

there aren't other ports I could have used on the main router, are there?

if I used its WAN port I would have probably bricked my entire working network.

also, bringing this up again AFTER I've reported that the issue was a badly designed firmware is kind of unnecessary, so I guess you really need to have the last word.

> Any "403" error from these gizmos is evidence of a firmware defect.

and this should be evident how?

the user manual does not say anything about that.

how should I know that Netgear ships products with faulty DEFAULT firmware?

I thought there was some error on the basic HTTP authentication side that was due to not having reset the password, or stuff like that, and I was going through an endless cycle of resetting the router and changing the password, hoping it would fix itself.

also, how should I know that most Netgear products share this bug, or anything else?

if I don't see a page or thread specific to my model, I treat information with a pinch of salt.

why wouldn't Netgear provide a guide like this, since having it as an easy setup is out of the question?

I have read a lot of threads to get a picture as complete as it could be, yet you pulled my leg in your FIRST sentence talking about psychics... wow.

> As it says in the guide, "What could go wrong?" (You seem to have

> expanded the envelope a little on that one.)

was that a rethorical question?

I appreciate your deside to help others, but you have a really mean behavior that really stands in the way for (some) folks to be as appreciative as they can be.

believe it or not, I'm no moron and I'm technically proficient, yet I could not foresee that the ONLY way to fix this was to DOWNGRADE the firmware.

if I had the proper firmware on, I probably wouldn't have come here for help and would have made it on my own, no guide needed.

if lots of people have the same issues, maybe the guide isn't as informative as it could be?

for example, it does not say that the Netgear router REFUSES to update the firmware (I had downloaded the v54 IMG file on my laptop) if it's not connected to the WAN, or on the other hand that the Netgear REFUSES to change its IP address if the WAN address has been assigned and it's overlapping, even though that would change with a reboot.

so, again, there might be other steps in your guide to be added, talking about possible firmware updates, or WHEN to connect or disconnect the WAN/LAN or LAN/LAN cables.

bottom line: chill out and thanks for the limited help.