On Sat, Jun 04, 2022 at 06:54:18PM +0200, Nicolas Cavallari wrote:
> On 23/05/2022 20:34, Kamil via Dnsmasq-discuss wrote:
> > Dear Nicolas,
> >
> > I've tried isc-dhcp-server without "authoritative" and it still work fine
> >
> >
> > If anything else fails, use tcpdump/wireshark.
> >
> >
On 23/05/2022 20:34, Kamil via Dnsmasq-discuss wrote:
Dear Nicolas,
I've tried isc-dhcp-server without "authoritative" and it still work fine
If anything else fails, use tcpdump/wireshark.
I've used tcpdump. I've attached full log in this message:
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
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 DHCP requests and log
"DHCP packet received on eth0
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 Dnsmasq-discuss wrote:
> > > On Sun, May 15, 2022 at 07:21:47AM +0200, Geert Stappers via
> > > Dnsmasq-discuss 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;
ddns-update-style none;
default-lease-time 600;
max-lease-time 3600;
On 15/05/2022 15:40, Kamil via Dnsmasq-discuss wrote:
>
> > PS. I've read in FAQ about 255.255.255.255 broadcast and invalid
> > firewall rules, but I don't have any firewall rules and I'm not changing
> > network config files when switching to isc-dhcp-server (which I use as a
> > benchmark)
> >
On 15/05/2022 15:40, Kamil via Dnsmasq-discuss wrote:
PS. I've read in FAQ about 255.255.255.255 broadcast and invalid
firewall rules, but I don't have any firewall rules and I'm not changing
network config files when switching to isc-dhcp-server (which I use as a
benchmark)
ISC dhcpd
On Sun, May 15, 2022 at 01:10:40AM +0200, Kamil via Dnsmasq-discuss wrote:
> > On Sat, May 14, 2022 at 11:27:34AM +0200, Geert Stappers via
> Dnsmasq-discuss wrote:
> > > On Sat, May 14, 2022 at 02:53:51AM +0200, Kamil via Dnsmasq-discuss
> wrote:
> ...
> > > > 1. I plug one device - it works.
>
On Sun, May 15, 2022 at 01:10:40AM +0200, Kamil via Dnsmasq-discuss wrote:
> On Sat, May 14, 2022 at 11:27:34AM +0200, Geert Stappers via Dnsmasq-discuss
> wrote:
> > On Sat, May 14, 2022 at 02:53:51AM +0200, Kamil via Dnsmasq-discuss wrote:
...
> > > 1. I plug one device - it works.
> > > 2.
Dear Geert and Simon,
I'm not native english speaker. I try to describe things the best I can.
I'm sorry if I failed to do it clearly enough.
On Sat, May 14, 2022 at 02:53:51AM +0200, Kamil via Dnsmasq-discuss wrote:
> > > On 11/05/2022 12:41, Kamil via Dnsmasq-discuss wrote:
> > > > Hi!
> > > >
On Sat, May 14, 2022 at 02:53:51AM +0200, Kamil via Dnsmasq-discuss wrote:
> > On 11/05/2022 12:41, Kamil via Dnsmasq-discuss wrote:
> > > Hi!
> > > I've configured Dnsmasq with the following config:
> > >
> > > interface=eth0
> > > bind-interfaces
> > > dhcp-option=3,192.168.6.1
> > >
> On 11/05/2022 12:41, Kamil via Dnsmasq-discuss wrote:
> > Hi!
> >
> > I've configured Dnsmasq with the following config:
> >
> > interface=eth0
> > bind-interfaces
> > dhcp-option=3,192.168.6.1
> > dhcp-option=6,8.8.8.8
> > set long-lasting records.
> >
On 11/05/2022 12:41, Kamil via Dnsmasq-discuss wrote:
Hi!
I've configured Dnsmasq with the following config:
interface=eth0
bind-interfaces
dhcp-option=3,192.168.6.1
dhcp-option=6,8.8.8.8
set long-lasting records.
dhcp-range=192.168.6.11,192.168.6.20,255.255.255.0,12h
Hi!
I've configured Dnsmasq with the following config:
interface=eth0
> bind-interfaces
> dhcp-option=3,192.168.6.1
> dhcp-option=6,8.8.8.8
> set long-lasting records.
> dhcp-range=192.168.6.11,192.168.6.20,255.255.255.0,12h
>
And most of the devices work just fine (here is the example syslog):
18 matches
Mail list logo
