On Mon, May 23, 2022 at 08:37:41PM +0200, Kamil via Dnsmasq-discuss wrote:
> On 20/05/2022 19:19, Simon Kelley wrote:
> >
> > I have a theory:
> >
> > In the logs, it takes between 7 and 9 seconds after carrier detect on
> > eth0 (I guess that's when you plug the RTMU86 in?) before eth0 is
> >
On 18/05/2022 09:39, Nicolas Cavallari <
nicolas.cavall...@green-communications.fr> wrote
> On 11/05/2022 13:41, Kamil via Dnsmasq-discuss wrote:
> >
> > But when I used isc-dhcp-server with following config:
> >
> > subnet 192.168.6.0 netmask 255.255.255.0 {
> > interface eth0;
On 20/05/2022 19:19, Simon Kelley wrote:
>
> I have a theory:
>
> In the logs, it takes between 7 and 9 seconds after carrier detect on
> eth0 (I guess that's when you plug the RTMU86 in?) before eth0 is
> allocated IP address 192.168.6.1. Until the address is allocated,
> dnsmasq will ignore
On Wed, May 18, 2022 at 10:14, Geert Stappers via Dnsmasq-discuss <
dnsmasq-discuss@lists.thekelleys.org.uk> wrote:
> On Tue, May 17, 2022 at 11:16:28AM +0200, Kamil via Dnsmasq-discuss wrote:
> > On Mon, May 16, 2022 at 04:56:25PM +0100, Simon Kelley wrote:
> > > On 15/05/2022 15:40, Kamil via
Hi,
as usual, get rid of systemd-resolved first.
- I would suggest dnf remove systemd-resolved. Minimal action is
systemctl disable --now systemd-resolved
- Then rm /etc/resolv.conf symlink
- create own /etc/resolv.conf
nameserver 127.0.0.1
nameserver 192.168.178.1
search mydomain.lan.
-
