From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
"aderumier@odiso.com" <aderumier@odiso.com>,
"s.hanreich@proxmox.com" <s.hanreich@proxmox.com>
Subject: Re: [pve-devel] [PATCH dnsmasq 0/1] purge previous ip/mac lease of dhcp reply
Date: Fri, 17 Nov 2023 06:49:27 +0000 [thread overview]
Message-ID: <d1c2dfec90ef70a9ffc20bbe669ad837a99a5243.camel@groupe-cyllene.com> (raw)
In-Reply-To: <300e8e6526824d5c31aa7677bd030ade872572c3.camel@groupe-cyllene.com>
-------- Message initial --------
De: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
À: pve-devel@lists.proxmox.com <pve-devel@lists.proxmox.com>,
aderumier@odiso.com <aderumier@odiso.com>, s.hanreich@proxmox.com
<s.hanreich@proxmox.com>
Objet: Re: [pve-devel] [PATCH dnsmasq 0/1] purge previous ip/mac lease
of dhcp reply
Date: 16/11/2023 14:47:20
> > Maybe this [1][2] could be a less intrusive solution for this
> > issue?
>>Yes, dhcp release packet should be the way, but I don't known if can
>simply forge packet why any mac ?
>>>
>>I'll test it this afternoon to see if it's work.
mmm,It's not working, the dhcp release packet never reach the bridge
I have also try to forge the packet in python with scapy,
same bahviour.
from scapy.all import send, IP, UDP, BOOTP, DHCP, str2mac
import random
releaseMAC = '12:45:a3:ed:c8:36'
releaseIP='192.168.2.10'
serverIP='192.168.2.1'
releaseMACraw = str2mac(releaseMAC)
dhcp_release =
IP(dst=serverIP)/UDP(sport=68,dport=67)/BOOTP(chaddr=releaseMACraw,
ciaddr=releaseIP, xid=random.randint(0,
0xFFFFFFFF))/DHCP(options=[('message-type','release'), 'end'])
send(dhcp_release)
next prev parent reply other threads:[~2023-11-17 6:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 21:58 Alexandre Derumier
2023-11-15 21:58 ` [pve-devel] [PATCH dnsmasq 1/1] purge old ip-mac lease on dhcpreply Alexandre Derumier
2023-11-16 9:43 ` [pve-devel] [PATCH dnsmasq 0/1] purge previous ip/mac lease of dhcp reply Stefan Hanreich
2023-11-16 13:47 ` DERUMIER, Alexandre
2023-11-17 6:49 ` DERUMIER, Alexandre [this message]
2023-11-17 8:55 ` Wolfgang Bumiller
2023-11-17 9:19 ` DERUMIER, Alexandre
2023-11-17 9:42 ` DERUMIER, Alexandre
2023-11-17 10:46 ` DERUMIER, Alexandre
2023-11-17 10:49 ` Stefan Hanreich
2023-11-17 10:52 ` DERUMIER, Alexandre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d1c2dfec90ef70a9ffc20bbe669ad837a99a5243.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal