Dozy Netgear config question

I've just been lent a netgear DG834 to play with, but through haste to
configure it as a temporary replacement for the router I usually use for
secondary nat (quickest way to try it out) I am at a total loss over how
to persuade it to change LAN IP/subnet.

I try to tell it that I require it to live at (say) 10.96.98.10
255.255.255.0 and the javascript autoresponse (which actually I think I
should look at as it might give a clue) is '192.168.0.1' / 'Invalid IP
please try again'

Now, I *know* it's currently invalid as there's nothing it can talk to on
that range (until I change it at the NIC end) but the usual is to demand a
reboot and off we go. This one just isn't having that.

Sorry to stump up with a question that almost certainly has an obvious
answer but my time's currently chock full of expensive RL bother and I've
little left to spend on what I enjoy. Hence the rapid 'help' plea

Thanks if someone points out what I'm missing. Please don't drop it too
heavily on my foot <g>

Dave J.

In article <f0u7kn$s9d$(E-Mail Removed)>, Dave J. says...
> I've just been lent a netgear DG834 to play with, but through haste to
> configure it as a temporary replacement for the router I usually use for
> secondary nat (quickest way to try it out) I am at a total loss over how
> to persuade it to change LAN IP/subnet.
>
> I try to tell it that I require it to live at (say) 10.96.98.10
> 255.255.255.0 and the javascript autoresponse (which actually I think I
> should look at as it might give a clue) is '192.168.0.1' / 'Invalid IP
> please try again'
>
> Now, I *know* it's currently invalid as there's nothing it can talk to on
> that range (until I change it at the NIC end) but the usual is to demand a
> reboot and off we go. This one just isn't having that.
>
> Sorry to stump up with a question that almost certainly has an obvious
> answer but my time's currently chock full of expensive RL bother and I've
> little left to spend on what I enjoy. Hence the rapid 'help' plea
>
> Thanks if someone points out what I'm missing. Please don't drop it too
> heavily on my foot <g>
>
Log into Router. Go to LAN IP Setup on the left hand side menu. It's
all in there - set IP address for router, set start/end IPs for DHCP
etc etc.



--
Conor

Light travels faster than sound. This is why some people appear bright
until you hear them speak.........

In MsgID<(E-Mail Removed)> on Sat, 28 Apr 2007
10:17:36 +0100, in uk.comp.home-networking, 'Conor' wrote:

>> Thanks if someone points out what I'm missing. Please don't drop it too
>> heavily on my foot <g>
>>
>Log into Router. Go to LAN IP Setup on the left hand side menu. It's
>all in there - set IP address for router, set start/end IPs for DHCP
>etc etc.

[Apologies for long post, but this has me very very curious]

Thanks Conor, I had got that far, and I had tried to set it to a
legitimate address, from the 10.* range I mentioned. Trouble was that it
kept telling me this *wasn't* a legitimate IP for no apparent reason.

The way I got around it (at about 3am when I should have been fast asleep)
*seemed* to be to turn off NAT altogether, then set the WAN address type
to static IP and set that in the 10.* range. It was then happy for me to
change the LAN subnet and management IP to the one I wanted, and instead
of the 'invalid IP' JS refusal, I got a more sensible 'you will need to
reconfigure your NIC' warning.

Then, I could reconfigure the PC, reconnect, turn NAT back on, change the
WAN IP and subnet to the one I really wanted (a /30 as it's just an a<->b
linkup) and all has been fine since. I've yet to actually *test* the damn
thing as the RL hassles persist (car repair, ex clamped so must get MOT +
tax within a week to retrieve £120 deposit) so it'll have to wait until
the evening. However I'm embarrassed enough at asking such a superficially
stupid question that I'm replying here and now.

I don't know if I carry enough credibility around here for people to
believe me when I say I tried to do it in an apparently sensible way, and
was totally barred from doing so by the router firmware. The only cure, as
above, being no NAT, 'classic' routing, and static WAN IP from the subnet
of 10.n.0.0 /16. It then let me configure the LAN range to the one I
wanted. Before that it wouldn't accept anything but 192.168.*.*

I suspect the change of WAN IP may have been incidental, I think the key
was disabling NAT. ?? Maybe not.. Will experiment this evening and will
update here for the sake of anyone doing a future archive search.

Anyone else got a clue for me? I'm very curious as I honestly do have a
good enough grasp of networking to know I wasn't asking anything
unintelligent from the firmware, and I do know it was refusing me point
blank. Maybe it's unusual for people to switch from the 192.168 range to a
10.n.n.0 range ? (Netgear DG834)

Reason I'm looking at it is that the computing department of a friend's
workplace had written it off and he asked me to find out why, their
general competency level would get them flamed to hell around here and *I*
would make a better job of configuring their network + servers from what
he's told me. Wish I could for that matter, I'm desperately seeking work
right now.

Thanks for any further hints. Purely academic given I've got around the
problem, but it resembles a coding error in the management software.
Unless I'm missing something else. [Cue sarky replies ] Very puzzling.

Could it be connected with my use of Opera rather than IE as my interface
to it? [WTF happened to straightforward Telnet!]

Heh, final funny detail, it didn't care at all when its WAN subnet
overlapped its LAN subnet, it would have apparently still routed between
the two.. That's not supposed to be viable at all, though I guess when
there's only two ports and assumptions are made by the manufacturers it
may actually seem to work. Dunno, another experiment for later, how
confused can I make it :-)

Cheers

Dave J.