On Fri, 5 May 2023 22:13:24 +0200, Geert Stappers wrote:
> It is too early to blame the IoT devices.
I don't blame them... They merely revealed there's something fishy.
> The original problem is most likely solvable with the original dhcpcd
> configuration in-place.
Strange that you keep
On Fri, May 05, 2023 at 08:47:14PM +0200, Johan Vromans wrote:
> On Fri, 05 May 2023 14:56:40 +, "Buck Horn" wrote:
>
> > Roy Marples's DHCP client daemon
> >dhcpcd
> > is not the same as ISC's DHCP server daemon
> >dhcpd.
> >
> > It would seem to me that Johan Vromans has been using
On Fri, 05 May 2023 14:56:40 +, "Buck Horn"
wrote:
> Roy Marples's DHCP client daemon
>dhcpcd
> is not the same as ISC's DHCP server daemon
>dhcpd.
>
> It would seem to me that Johan Vromans has been using the former:
> I think I recognise the syntax.
Yes, that's correct. The
uh...@fantomas.sk wrote:
you use dhcpd to configure other machines over network, not your own.
and, dnsmasq is not dhcpd. While it can act as dhcp server, the same applies
as above.
On 05.05.23 08:42, Ben Hendin wrote:
Apparently the syntax Johan has listed is not standard dhcpd.conf
syntax
On 05.05.2023 14:32:12, "Matus UHLAR - fantomas" wrote:
On 05.05.23 13:33, Johan Vromans wrote:
All docs tell me to set the static address in the /etc/dhcpcd.conf, this is
confusing.
I've now disabled dhcpcd and put the static address in
/etc/network/interfaces.
you use dhcpd to configure
uh...@fantomas.sk wrote:
> you use dhcpd to configure other machines over network, not your own.
>
> and, dnsmasq is not dhcpd. While it can act as dhcp server, the same applies
> as above.
Apparently the syntax Johan has listed is not standard dhcpd.conf
syntax (at least not that I could find in
On Fri, 5 May 2023 11:54:31 +0200, Johan Vromans wrote:
> do not run dhcpcd.
On 05.05.23 13:33, Johan Vromans wrote:
All docs tell me to set the static address in the /etc/dhcpcd.conf, this is
confusing.
I've now disabled dhcpcd and put the static address in
/etc/network/interfaces.
you
On Fri, 5 May 2023 11:54:31 +0200, Johan Vromans wrote:
> > do not run dhcpcd.
All docs tell me to set the static address in the /etc/dhcpcd.conf, this is
confusing.
I've now disabled dhcpcd and put the static address in
/etc/network/interfaces.
Thanks
Johan
On Fri, May 05, 2023 at 12:11:32PM +0200, Geert Stappers wrote:
> On Fri, May 05, 2023 at 11:54:31AM +0200, Johan Vromans wrote:
} } } } dhcpcd[449]: eth0 10 second defense failed for 192.168.1.10
} } } } and slowly the LAN collapses
> > > Set static IP on the interface and do not run dhcpcd.
On Fri, May 05, 2023 at 11:54:31AM +0200, Johan Vromans wrote:
> Hi Geoff,
>
> Thanks for your reply.
>
> > Set static IP on the interface and do not run dhcpcd. The problem is
> > with dhcpcd releasing the address, not with dnsmasq.
>
> I have this in my /etc/dhcpcd.conf:
>
> interface eth0
Hi Geoff,
Thanks for your reply.
> Set static IP on the interface and do not run dhcpcd. The problem is
> with dhcpcd releasing the address, not with dnsmasq.
I have this in my /etc/dhcpcd.conf:
interface eth0
static ip_address=192.168.1.10/24
static routers=192.168.1.1
I do not run
Hi Johan,
On 05/05/2023 08:40, Johan Vromans wrote:
> Hi,
>
> I have a number of IoT devices. Occasionally, when they try to set up the
> DHCP lease, some of them send wrong packets. The device effectively claims
> the IP address of the DHCP server. From the system log:
>
> May 4 05:39:59
Hi,
I have a number of IoT devices. Occasionally, when they try to set up the
DHCP lease, some of them send wrong packets. The device effectively claims
the IP address of the DHCP server. From the system log:
May 4 05:39:59 srv1 dhcpcd[449]: eth0: hardware address
xx:xx:xx:xx:xx::ce
13 matches
Mail list logo
