On 26/06/18 22:26, A. Dumas wrote:
> The Natural Philosopher  wrote:
>> On 23/06/18 20:55, A. Dumas wrote:
>>> The Natural Philosopher  wrote:
>>>> And what guarantee is there that its IP adress will stay te same next
>>>> time it reboots a DHCP request?
>>>
>>> Because the client’s MAC address won’t change and you’ve configured
your
>>> DHCP server (in your modem config interface) to assign a fixed IP address
>>> to it. Outside the dynamic DHCP range, obviously.
>>>
>>
>> Well actually first of all you didnt say "the client’s MAC address won’t
>> change and you’ve configured your DHCP server (in your modem config
>> interface) to assign a fixed IP address"
>>
>> (and its not a modem config interface, its a router config interface)
>>
>> And, secondly it doesnt have to be ouside your 'dynamic DHCP range'.
>>
>>   The mere fact that a MAC address is assigned to it will stop it being
>> assigned dynamically to anything else.
>>
>> Its all fairly academic. You still have st it up to be on a fixed IP
>> address and *mutatis mutandis* it makes little odds whether that is done
>> on the router or the Pi itself. It still isn't broadcast and so no one
>> knows where to find it unless you run a local name server OR everyone
>> has a common host table.
>
> I don’t think you understand what I’m rambling on about. Or I don’t
> understand your replies.
>
> 1. There’s a dhcp server. 2. There’s a client that needs a fixed IP
> address. 3a. You can fix the IP address on the client (e.g. in the hosts
> file). 3b. YOU CAN ALSO, ALTERNATIVELY, FIX THE IP ADDRESS ON THE SERVER.
> 4. If you go with option b, you leave the client on standard dhcp
> configuration. 5. Then you configure the dhcp server (on your modem or
> router or modem/router, whatever) to always assign the same IP address to
> your client. 6. So the IP address gets assigned by dhcp but it IS fixed. 7.
> The server recognises your client by its MAC address (or by its
> zeroconf/bonjour name but that will probably end badly). 8. So you add a
> rule “MAC address xxyyzz always gets IP address aabbcc” (the numbers
don’t
> have to be correlated, you just manually set it). 9. It’s best to use an IP
> address (set by you & assigned by dhcp!) outside the range the server uses
> for “free”/random dhcp. Not because the server would assign it twice (I
> hope..) but mainly because it might already be in use. Also looks more
> organised to keep the ranges separate. I mean you probably have some system
> for the fixed addresses.
>

Yes, but you don't understand MY point that there is still an entry that
has to be made somewhere - server side or router side is rather
irrelevant, and there is still no way for devices on the net to KNOW
where that machine is other than by setting up local DNS or using host
tables on all clients. Bonjour/avahi excepted which works I grant you
BUT no one seems to use it..




--
The lifetime of any political organisation is about three years before
its been subverted by the people it tried to warn you about.

Anon.

--- SoupGate-Win32 v1.05