On 5/15/2019 12:21 AM, Kevin Flynn wrote:
>
>
> On 5/14/19 3:15 PM, john doe wrote:
>> On 5/14/2019 6:42 PM, Kevin Flynn wrote:
>>>
>>> hostnames to clients. I've tried all the obvious methods, including
>>> /etc/ethers, dhcp-hostsfile entries, dhcp-ignore-names,
>>> dhcp-generate-names, tag sets,
On Tue, May 14, 2019 at 06:21:58PM -0400, Kevin Flynn wrote:
> On 5/14/19 3:15 PM, john doe wrote:
> > On 5/14/2019 6:42 PM, Kevin Flynn wrote:
> > >
> > > hostnames to clients. I've tried all the obvious methods, including
> > > /etc/ethers, dhcp-hostsfile entries, dhcp-ignore-names,
> > > dhcp-g
On 5/14/19 3:15 PM, john doe wrote:
On 5/14/2019 6:42 PM, Kevin Flynn wrote:
hostnames to clients. I've tried all the obvious methods, including
/etc/ethers, dhcp-hostsfile entries, dhcp-ignore-names,
dhcp-generate-names, tag sets, etc. with no luck.
>> ...
So in summary, is there any way
On 5/14/2019 6:42 PM, Kevin Flynn wrote:
>
> Hello everyone.
>
> I'm currently working on a small home network voip system, and I cannot
> for the life of me figure out how to get dnsmasq to send dhcp option 12
> hostnames to clients. I've tried all the obvious methods, including
> /etc/ethers, dhc
Hello everyone.
I'm currently working on a small home network voip system, and I cannot
for the life of me figure out how to get dnsmasq to send dhcp option 12
hostnames to clients. I've tried all the obvious methods, including
/etc/ethers, dhcp-hostsfile entries, dhcp-ignore-names,
dhcp-ge
Am 14.05.19 um 17:52 schrieb Roy Marples:
> On 14/05/2019 14:29, Oliver Freyermuth wrote:
>> Same here. In an automated deployment situation, client changes DUID in each
>> phase:
>> - PXE (if done via IPv6)
>> - Installation time (from ramdisk)
>> - Final OS after installation
>> This may improve
On 14/05/2019 14:29, Oliver Freyermuth wrote:
Same here. In an automated deployment situation, client changes DUID in each
phase:
- PXE (if done via IPv6)
- Installation time (from ramdisk)
- Final OS after installation
This may improve if newer versions of dhcpcd get packaged in installer ramdi
On 5/14/19 3:52 AM, Nicolas Cavallari wrote:
On 26/04/2019 22:03, Brian Haley wrote:
Currently, dhcp_release will only send a 'fake' release
when the address given is in the same subnet as an IP
on the interface that was given.
This doesn't work in an environment where dnsmasq is
managing lease
Am 11.05.19 um 19:42 schrieb Kevin Darbyshire-Bryant:
>
>
>> On 6 Apr 2019, at 12:01, Geert Stappers wrote:
>>
>> On Mon, Apr 01, 2019 at 01:02:20AM +0200, Pali Rohár wrote:
>>> On Tuesday 12 February 2019 13:41:43 Geert Stappers wrote:
On 06-02-2019 21:29, Pali Rohár wrote:
> On Friday
On 14/05/2019 04:54, Steve Lloyd wrote:
I am running dnsmasq on the lastest stretch on a rpi. For some reason
dnsmasq dies after about 20 minutes, I can restart it and it will last
another 20 minutes. Any insight on how to fix this would be much
appreciated. Here is the status after it dies
Hi Geert,
That is terribly helpful. Thanks a lot!
Although 'the whole world is not Linux', your explanation "Dnsmasq listens
on ports 53, 67 and 69. That requires
root privilege; Avoiding to run dnsmasq as root can be done with net
capabilities" seems a terrific candidate to go in the man page :
On 26/04/2019 22:03, Brian Haley wrote:
> Currently, dhcp_release will only send a 'fake' release
> when the address given is in the same subnet as an IP
> on the interface that was given.
>
> This doesn't work in an environment where dnsmasq is
> managing leases for remote subnets via a DHCP rela
12 matches
Mail list logo
