ReadyNAS 102 DHCP server?

no app that I know of. DHCP is actually done by routers 99% of the time except in enterprise.
So yes, this is possible via SSH I don't remember if the package is called dhcp-server or dhcpd in Debian but it is definitely there. Now the fact is I don't really see any use of doing it there, it would be more complicated to administer than a standard router interface and this is not supported by Netgear so...

Could you tell more about what you want to do, maybe there is a better solution ?

Hi, thanks for the reply. I have a Squeezebox Touch connected to the NAS.

Point is, I share the wifi with the neighbours and the router is in their room. So when I want the SB to connect to Mysqueezebox.com, it does so via wifi and when I want the SB to connect to the NAS, it does so via ethernet. But when I want to switch from or to either my NAS or Mysqueezebox.com, I have to manually switch network first in the SB, which is a bit annoying. I'd rather have them on the same network, so they'll connect automatically.

So I got myself a wireless repeater/LAN switch with DHCP server funtionality, but it can only work as either repeater or DHCP server but not both.

First I tried connecting the NAS and the SB to the repeater via ethernet cable and set the repeater up as wireless repeater, so the SB could connect to the NAS via LAN through the repeater switch and to Mysqueezebox.com via the repeater being connected to the neighbours wifi.

This would sometimes work but the SB would often lose connection with the NAS or Mysqueezebox.com saying it couldn't resolve a proper IP adress for the SB. (maybe because of some IP conflicts with the wifi router of the neighbours?)

So now I have the repeater solely set up as DHCP server and as so far have not had the SB lose connection with the NAS, but when I want to connect to Mysqueezebox.com I have to manually switch to the wifi network of the neigbours on the SB first by going through some menus, which is doable, but not very convenient.

I was just wondering if I could get some DHCP server working on the NAS, I could then have the SB connect to the wifi via ethernet through the repeater, thus not having to switch between wifi and ethernet on the SB constantly. I hope this makes sense. Sorry for the lengthy explanation.

But thanks in advance.

Kind regards,

Laszlo

Not sure why the SB had trouble resolving its address. But if you can cable it and the NAS to the WiFi repeater, that should work (not using the capability of the SB at all).

If you want more security, you could connect your own router to the WiFi repeater's lan port, and connect all your own equipment to your own router.

Hi StephenB, thanks for replying(on both threads)

could it be possible that my SB lost connection because I hadn't entered the right DNS address?

The SB will fill it in automatically as being the same address as the Gateway address, but when I look at "Network connection details" on my Win7 laptop, I see two DNS server addresses, which are quite different from the Gateway address:

213.46.228.196
62.179.104.196

Any idea which one to choose?

thanks,

Laszlo

There are several possible causes for the SB issue

(a) weak signal caused the WiFi connection between the SB and the extender to drop
(b) weak signal caused the WiFi connection connection between the extender and the router to drop
(c) A disruption in the ISP's internet service, which had nothing to do with your local network at all.
(d) If you are assigning static addresses, an address conflict would result in not having an IP address at all, or creating confusion in the router/switches on how to route traffic

To answer your question -

If you are using DHCP/automatic addresses, the router supplies the DNS addresses to use.
Some supply their internal address (e.g. the gateway address) as the DNS server. They then forward DNS requests to the ISP server.

Others pass through the DNS addresses they get from the ISP. It sounds like your router does it that way. If you are configuring static addresses, I generally wouldn't use the gateway address if the router is not supplying that to other (automatic) devices. So I wouldn't use the gateway address in your case.

Your ISP is supplying two addresses, to provide failover. You can use either one, or you can use a public DNS service such as google's. If you want to try google, use 8.8.8.8 and 8.8.4.4.

You do need to ensure that the actual IP address you are assigning is not used by the neighbors. Generally there is a setting for the number of automatically assigned addresses. If it is set to 32, then you could safely use addresses above that range - for instance, 192.168.1.40 and above. Don't use .255.

Or if you have configuration access to the router via wifi, look for a reserved reservation feature. That is a safer approach than assigning static addresses - especially for mobile devices and laptops.