LAN help please.

[wiltshirejohn]

I'm running a Netgear DG834G, hardwired to this machine. It also talks nicely (wireless) to the laptop downstairs.

I'm trying to set up a security cam through a wireless access point to talk to the Netgear.  The access point is supplied with a default IP address of 192.168.2.1 and subnet mask of 255.255.255.0

I've tried changing the LAN settings in the Netgear setup pages but it won't play ball.

e.g. I've set the DHCP Server ending address to 192.168.2.nn  in order to include the new device but then get the error message:

"DHCP Server starting or ending address not in LAN IP Address Subnet."

Any ideas how I can get access to this so-called access point??   

Regards - wiltshirejohn

[Rik]

Unfortunately, I'm no longer using an 834, so I can't go and burrow, but it sounds as if it wants you to change a second range, for the LAN, to match the DHCP. I'll see i I can find a manual.

[Rik]

It does look as if you need to make two changes, after which you'll need to make a fresh connection to the router. From the manual:

Configuring LAN IP Settings

The LAN IP Setup menu allows configuration of LAN IP services such as DHCP and RIP. These
features can be found under the Advanced heading in the Main Menu of the browser interface.
The router is shipped preconfigured to use private IP addresses on the LAN side, and to act as a
DHCP server. The router's default LAN IP configuration is:

• LAN IP addresses—192.168.0.1
• Subnet mask—255.255.255.0

These addresses are part of the Internet Engineering Task Force (IETF)-designated private address
range for use in private networks, and should be suitable in most applications. If your network has
a requirement to use a different IP addressing scheme, you can make those changes in this menu.

The LAN TCP/IP Setup parameters are:
• IP Address
This is the LAN IP address of the router.
• IP Subnet Mask
This is the LAN Subnet Mask of the router. Combined with the IP address, the IP Subnet Mask
allows a device to know which other addresses are local to it, and which must be reached
through a gateway or router.
• RIP Direction
RIP (Router Information Protocol) allows a router to exchange routing information with other
routers. The RIP Direction selection controls how the Router sends and receives RIP packets.
Both is the default.
— When set to Both or Out Only, the router will broadcast its routing table periodically.
— When set to Both or In Only, it will incorporate the RIP information that it receives.
— When set to None, it will not send any RIP packets and will ignore any RIP packets
received.

• RIP Version
This controls the format and the broadcasting method of the RIP packets that the router sends.
It recognizes both formats when receiving. By default, this is set for RIP-1.
— RIP-1 is universally supported. RIP-1 is probably adequate for most networks, unless you
have an unusual network setup.
— RIP-2 carries more information. Both RIP-2B and RIP-2M send the routing data in RIP-2
format.
— RIP-2B uses subnet broadcasting.
— RIP-2M uses multicasting.

DHCP

By default, the router will function as a DHCP (Dynamic Host Configuration Protocol) server,
allowing it to assign IP, DNS server, and default gateway addresses to all computers connected to
the router's LAN. The assigned default gateway address is the LAN address of the router. IP
addresses will be assigned to the attached PCs from a pool of addresses specified in this menu.
Each pool address is tested before it is assigned to avoid duplicate addresses on the LAN.

For most applications, the default DHCP and TCP/IP settings of the router are satisfactory. See "IP
Configuration by DHCP"on page B-9 for an explanation of DHCP and information about how to
assign IP addresses for your network.

Use Router as DHCP server

If another device on your network will be the DHCP server, or if you will manually configure the
network settings of all of your computers, clear the 'Use router as DHCP server' check box.
Otherwise, leave it selected.

Specify the pool of IP addresses to be assigned by setting the Starting IP Address and Ending IP
Address. These addresses should be part of the same IP address subnet as the router's LAN IP
address. Using the default addressing scheme, you should define a range between 192.168.0.2 and
192.168.0.254, although you may want to save part of the range for devices with fixed addresses.

[Sebby]

I'm running a Netgear DG834G, hardwired to this machine. It also talks nicely (wireless) to the laptop downstairs.

I'm trying to set up a security cam through a wireless access point to talk to the Netgear.  The access point is supplied with a default IP address of 192.168.2.1 and subnet mask of 255.255.255.0

I've tried changing the LAN settings in the Netgear setup pages but it won't play ball.

e.g. I've set the DHCP Server ending address to 192.168.2.nn  in order to include the new device but then get the error message:

"DHCP Server starting or ending address not in LAN IP Address Subnet."

Any ideas how I can get access to this so-called access point??   

Regards - wiltshirejohn

I'm not sure whether you assign static IPs to your PCs, but that doesn't matter too much. If you do, enable the DHCP server on the Netgear to issue IP address from, say, 192.168.0.4 onwards (assuming that your PCs are 192.168.0.2 and 192.168.0.3). Then, set the wireless access point to get an IP address automatically. The access point will then get an IP in the correct range and so will the camera.

If you don't use static IPs for the PCs, do the same as above, though you could set the DHCP server to issue IPs from 192.168.0.2 onwards.

[wiltshirejohn]

Then, set the wireless access point to get an IP address automatically.

Thanks Sebby - if I could communicate with the bl**dy thing I would set it so. At the moment, as far as the network sees, it just does not exist.

Regards - wiltshirejohn

[Sebby]

Ah, I see your problem. In that case, plug it directly into your PC, and set the IP statically on the PC to 192.168.2.x (anything in that range) then you should be able to access it and change it to automatically get an IP. Then reset the PC's settings and you should be away.

[wiltshirejohn]

It does look as if you need to make two changes, after which you'll need to make a fresh connection to the router. From the manual:

Snip....

Thank Rik. I'll study this a bit later - I'm being called to peel the spuds for dinner tonight. (Yep - we got priorities around here too..)

I guessed that further changes would be needed,  but where and what

Regards - wiltshirejohn

[Rik]

Well, between Sebby's approach and mine, you might get somewhere, John, but the spuds are far more important.

[wiltshirejohn]

Ah, I see your problem. In that case, plug it directly into your PC, and set the IP statically on the PC to 192.168.2.x (anything in that range) then you should be able to access it and change it to automatically get an IP. Then reset the PC's settings and you should be away.

Thanks Sebby. I'll probably give that a shot tomorrow. From the sound of the weather forecast we'll be housebound tomorrow.

Regards - wiltshirejohn

[wiltshirejohn]

Well, between Sebby's approach and mine, you might get somewhere, John, but the spuds are far more important.

Help - I've just been yelled at for a second time - that means trouble - gotta go...

[Rik]

The second yell... That's serious.

[Sebby]

I hope you don't get in too much trouble, John.

[wiltshirejohn]

Thanks Sebby. I'll probably give that a shot tomorrow. From the sound of the weather forecast we'll be housebound tomorrow.

Regards - wiltshirejohn

    There we were - all hatches battened etc..   and it was all a bit of a disappointment really.  I know those on the coast copped it but it wasn't too bad here.

    Anyway, I used Sebby's approach. Bingo! I can now reach the configuration page for the access point using an ethernet cable plugged into the router. All I have to do now is work out all the other settings, modes of operation etc. to get the router and access point to talk to each other wirelessly 

Thanks for the tip Sebby and thanks to Rick for the manual pages - off to do a little light reading now.

    Regards - wiltshirejohn

[Rik]

Glad you're getting there, John.

[Sebby]

I'm glad you're getting there, John. If you need any further help, just let us know.

[wiltshirejohn]

I've dug a little deeper on the Netgear site and it seems that the 834G cannot be used in the configuration that I had planned. i.e. acting as a bridge (to the access point with camera) plus having a wireless client (the laptop).

PLAN B:    The motherboard in my rig is the Asus P5B deluxe and it has it's own built-in wireless adapter.
I shall be firing this up and (hopefully) set up a second wireless network on a different channel.

If that doesn't work look for a red glow on the horizon just South of Chippenham .... no seriously -  plan C will mean festooning the place in cat5, which is what I wanted to avoid in the first place.

Anyways - off to look at the latest can o' worms, the Mikrotek wireless adapter on the motherboard.

Regards - wiltshirejohn

[Rik]

I wonder if it would be easier just to get a different camera?

[plugwash]

I've dug a little deeper on the Netgear site and it seems that the 834G cannot be used in the configuration that I had planned. i.e. acting as a bridge (to the access point with camera) plus having a wireless client (the laptop).

It may not be able to with the factory firmware but I would be very suprised if it can't do it with openwrt.

edit: unfortunately the openwrt guys claim support for the DG834G is still a work in progress so I don't know whether it will work well enough on your router to do what you want.

[wiltshirejohn]

It may not be able to with the factory firmware but I would be very suprised if it can't do it with openwrt.

edit: unfortunately the openwrt guys claim support for the DG834G is still a work in progress so I don't know whether it will work well enough on your router to do what you want.

Thanks plugwash, I've bookmarked the openwrt site and will keep an eye on it. I'm not a code jockey myself so I'm a little reluctant to start flashing firmware that's still classed W.I.P.

    Regards - wiltshirejohn

[Rik]

Very wise, John - routers aren't brilliant as doorstops.

[wiltshirejohn]

I wonder if it would be easier just to get a different camera?

Yup, it certainly would Rick. But....  these damn things ought to work together an' little ol' pig-headed me is gonna keep on trying.


    Regards - wiltshirejohn

[Rik]

Could you not re-assign the IP range for the LAN?

[wiltshirejohn]

Plan B worked 

The standalone access point is set in access point mode on channel 6 with DHCP enabled on a different subnet set to the router. My desktop is set as client to this AP.

The only downside to the present arrangement is that the laptop (client of the router) cannot be used to monitor the camera.  Yes I know I could "tune it in" to the new network but "She Who Must Be Obeyed" doesn't want me messin'  with her toy

Now all I have to do is sort out the motion detect alarms and so forth.

Many thanks to all who have offered help on this little problem.


Regards - wiltshirejohn

[Rik]

Sounds like you're working with one arm tied behind you back, John.

[Sebby]

I'm glad you've virtually got it sorted, John.