On Wed, Apr 12, 2023 at 02:03:22AM +0300, 0zl wrote:
> On 4/12/23 01:59, 0zl wrote:
> > Second I don't understand how this works exactly, I intend to create a
> > script that adds a permanent arp entry to make me more resilient to ARP
> > spoofing attacks, should I create the entry on arp add/old
Hello,
Apologies if this was clear but I'm having trouble understanding the
`--script-arp` entry in the man page. It says:
--script-arp
Enable the "arp" and "arp-old" functions in the
--dhcp-script and --dhcp-luascript.
Firstly when I tried to use I got no arp or
Replying to myself because I made a typo in this paragraph. I meant to
say: "should I create the ARP entry on the add/old action and remove on del"
Thank you!
On 4/12/23 01:59, 0zl wrote:
Second I don't understand how this works exactly, I intend to create a
script that adds a permanent arp
On 11/04/2023 17:21, web...@manfbraun.de wrote:
Hello!
I want to find out the response time from clients request up to
dnsmasq's response
(including the external answer!) to the client. But a look into the
logfile - thought, easy
to make a wrapper, because I am missing dnstap support -
On Tue, Apr 11, 2023 at 06:21:42PM +0200, web...@manfbraun.de wrote:
>
> Hello!
>
> I want to find out the response time from clients request up to dnsmasq's
> response
> (including the external answer!) to the client. But a look into the logfile -
> thought, easy
> to make a wrapper, because
Hello!
I want to find out the response time from clients request up to dnsmasq's
response
(including the external answer!) to the client. But a look into the logfile -
thought, easy
to make a wrapper, because I am missing dnstap support - wonders me.
For example, here a short excerpt, omitting
I think every incoming device tags dhcp requests with tag of that
interface name.
Therefore it should be possible:
dhcp-range=tag:eth1,192.168.1.50-192.168.1.100
dhcp-range=tag:eth2,10.0.0.100-10.0.0.150
If you enable --log-dhcp for extra details logged, it should log for
each query all tags
" looks like we need
--no-dhcpv4-interface and --no-dhcpv6-interface. That would certainly
solve your problem."
Just to clarify - you are stating that these options don't currently exist
and would need to be implemented in a future version?
I have blocked the request via ebtables on my device for
