On Sat, 23 Jun 2018 11:10:32 +0200, A. Dumas wrote:
> On 23/06/2018 09:20, Jan Panteltje wrote:
>> On a sunny day (22 Jun 2018 19:49:51 GMT) A. Dumas wrote:
>>> Perhaps, but don't fix the ip address on the client, leave it on
>>> dhcp and use your router to assign a fixed address. 99.3% of routers
>>> currently on the market can do that.
>>
>> For some, that is possibly the best solution, yes,
>> I have a bunch of computers, sensors, including some raspis, on the
>> LAN.
>> The LAN is on 24/7 while the cable modem ('router') is not.
>
> I guess that can be a valid reason. For most people the LAN would
> crumble anyway when the modem/router shuts down, I think (direct cables
> to modem/router, wifi from modem/router).
>
i simply disabled DHCP on my router & rung my own DHCP server instead (in
my case this is needed as I have a number of devices that require
specific option that the Router DHCP server does not).
I use DNSmasq on a Fedora file server but this could easily be handled by
a PI
fixed IP addresses are normally allocated by MAC address but there is a
range off addresses outside the normal DHCP scope that can be assigned
manually when more appropriate
--
I'm sorry, but my karma just ran over your dogma.
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | FidoUsenet Gateway (3:770/3)
|