Send kea-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."
Today's Topics:
1. RE: Server hangs at startup - issue with lock file
(Chaigneau, Nicolas)
2. Possibility of disabling raw socket use in Kea ?
(Chaigneau, Nicolas)
3. Re: Possibility of disabling raw socket use in Kea ?
(Marcin Siodelski)
4. Re: Possibility of disabling raw socket use in Kea ?
(Tomek Mrugalski)
5. RE: Possibility of disabling raw socket use in Kea ?
(Chaigneau, Nicolas)
----------------------------------------------------------------------
Message: 1
Date: Mon, 22 Sep 2014 07:33:39 +0000
From: "Chaigneau, Nicolas" <[email protected]>
To: Tomek Mrugalski <[email protected]>, "[email protected]"
<[email protected]>
Subject: RE: Server hangs at startup - issue with lock file
Message-ID:
<ab94b0b675bdf14189cd5a861db36c8414197...@de-cm-mbx26.corp.capgemini.com>
Content-Type: text/plain; charset="us-ascii"
Hello,
So I've finally tested your fix with the tarball provided by Jeremy.
As far as I'm concerned, the problem is entirely fixed:
- The default location "${prefix}/var/run/kea" is correctly used
- The environment variable KEA_LOCKFILE_DIR is used when specified
- An error message is displayed when the directory doesn't exist "Unable to use
interprocess sync lockfile (No such file or directory): (...)"
(actually, it is displayed 25 times, not sure if that's what you intended. At
least we can't miss it ;)
Thanks.
Regards,
Nicolas.
> On 08.09.2014 08:45, Chaigneau, Nicolas wrote:
> > I'll test your fix, just tell me when it's available.
> The proposed code fix is on branch trac3591. To get it, you can use the
> following commands:
>
> git clone git://git.kea.isc.org/kea
> git checkout trac3591
>
> This code creates lockfile in the ${prefix}/var/run/kea directory.
> However, you can enforce different location by setting up KEA_LOCKFILE_DIR
> variable. That variable should point out to a writeable directory and must
> not end with a slash. Also, it can be set to a special value "none", which
> will disable logging lockfile altogether.
> That is not recommended if you plan to have several processes log to the same
> output file.
>
> Please do let me know if this works for you.
>
> The ticket #3591 (http://kea.isc.org/ticket/3591) will now undergo regular
> review process. One of the ISC engineers will handle this.
> However, feel free to comment on it if you have any comments or suggestions.
>
> Thanks for reporting this issue and for testing this fix, Tomek
>
>
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
------------------------------
Message: 2
Date: Mon, 22 Sep 2014 09:42:58 +0000
From: "Chaigneau, Nicolas" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Possibility of disabling raw socket use in Kea ?
Message-ID:
<ab94b0b675bdf14189cd5a861db36c8414197...@de-cm-mbx26.corp.capgemini.com>
Content-Type: text/plain; charset="us-ascii"
Hello,
With dhcpd, it was possible to disable usage of raw sockets, as described in:
https://kb.isc.org/article/AA-00379/0/How-DHCP-uses-raw-sockets.html
In our case, we have no need for raw sockets, since we won't handle direct
clients (all DHCP traffic incoming will be relayed).
More to the point, we need to be able to perform packet filtering beforehand
(through iptables), which is not feasible if the DHCP server uses raw sockets.
So my question is:
Is it possible to not use raw sockets with Kea ? (at build time and/or server
startup)
Thanks for your time.
Regards,
Nicolas.
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/kea-dev/attachments/20140922/d5173428/attachment-0001.html>
------------------------------
Message: 3
Date: Mon, 22 Sep 2014 12:13:19 +0200
From: Marcin Siodelski <[email protected]>
To: "Chaigneau, Nicolas" <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: Possibility of disabling raw socket use in Kea ?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
Hi,
The code in Kea is prepared to switch between the use of raw sockets and
regular datagram sockets. But, currently the selection is hardcoded and
there is no configuration parameter to control this selection by the
administrator. We're now going through some refactoring of the
configuration code, so once this is done we can easily implement the switch.
Marcin
On 22/09/14 11:42, Chaigneau, Nicolas wrote:
> Hello,
>
>
>
>
>
> With dhcpd, it was possible to disable usage of raw sockets, as
> described in:
>
>
>
> https://kb.isc.org/article/AA-00379/0/How-DHCP-uses-raw-sockets.html
>
>
>
>
>
> In our case, we have no need for raw sockets, since we won?t handle
> direct clients (all DHCP traffic incoming will be relayed).
>
> More to the point, we need to be able to perform packet filtering
> beforehand (through iptables), which is not feasible if the DHCP server
> uses raw sockets.
>
>
>
> So my question is:
>
>
>
> Is it possible to not use raw sockets with Kea ? (at build time and/or
> server startup)
>
>
>
>
>
>
>
> Thanks for your time.
>
>
>
>
>
> Regards,
>
> Nicolas.
>
>
>
>
>
> This message contains information that may be privileged or confidential
> and is the property of the Capgemini Group. It is intended only for the
> person to whom it is addressed. If you are not the intended recipient,
> you are not authorized to read, print, retain, copy, disseminate,
> distribute, or use this message or any part thereof. If you receive this
> message in error, please notify the sender immediately and delete all
> copies of this message.
>
>
> _______________________________________________
> kea-dev mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/kea-dev
>
------------------------------
Message: 4
Date: Mon, 22 Sep 2014 12:39:27 +0200
From: Tomek Mrugalski <[email protected]>
To: Marcin Siodelski <[email protected]>, "Chaigneau, Nicolas"
<[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: Possibility of disabling raw socket use in Kea ?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
On 22/09/14 12:13, Marcin Siodelski wrote:
> The code in Kea is prepared to switch between the use of raw sockets and
> regular datagram sockets. But, currently the selection is hardcoded and
> there is no configuration parameter to control this selection by the
> administrator. We're now going through some refactoring of the
> configuration code, so once this is done we can easily implement the switch.
For the time being, you can do an experiment. It requires a minor change
to the source code.
The specific socket handling objects are called PktFilterLPF (raw
sockets) PktFilterInet(udp sockets). They are initialized in
IfaceMgr::setMatchingPacketFilter in iface_mgr_linux.cc in src/lib/dhcp
directory. That is called from Dhcpv4Srv constructor, which is in turn
controlled by direct_response_desired flag. Its default value is set to
true. If you edit it (line 91 in src/lib/dhcp/dhcp4_srv.h) to false and
recompile, it is possible that the code will be able to successfully use
UDP sockets.
Disclaimer: It's a quick hack. I haven't done any experiments with this,
so it may break down. We can't apply it, as most people are interested
in direct traffic, so a proper switch (either compile time or run time)
is needed. That's something that we can't do immediately.
Tomek
------------------------------
Message: 5
Date: Mon, 22 Sep 2014 11:58:52 +0000
From: "Chaigneau, Nicolas" <[email protected]>
To: Tomek Mrugalski <[email protected]>, Marcin Siodelski
<[email protected]>, "[email protected]" <[email protected]>
Subject: RE: Possibility of disabling raw socket use in Kea ?
Message-ID:
<ab94b0b675bdf14189cd5a861db36c8414197...@de-cm-mbx26.corp.capgemini.com>
Content-Type: text/plain; charset="iso-8859-1"
Thanks.
I don't need it right away. Knowing that it is planned is good enough :)
Regards,
Nicolas.
>
> -----Message d'origine-----
> De : Tomek Mrugalski [mailto:[email protected]]
> Envoy? : lundi 22 septembre 2014 12:39
> ? : Marcin Siodelski; Chaigneau, Nicolas; [email protected]
> Objet : Re: Possibility of disabling raw socket use in Kea ?
>
> On 22/09/14 12:13, Marcin Siodelski wrote:
> > The code in Kea is prepared to switch between the use of raw sockets
> > and regular datagram sockets. But, currently the selection is
> > hardcoded and there is no configuration parameter to control this
> > selection by the administrator. We're now going through some
> > refactoring of the configuration code, so once this is done we can easily
> > implement the switch.
> For the time being, you can do an experiment. It requires a minor change to
> the source code.
>
> The specific socket handling objects are called PktFilterLPF (raw
> sockets) PktFilterInet(udp sockets). They are initialized in
> IfaceMgr::setMatchingPacketFilter in iface_mgr_linux.cc in src/lib/dhcp
> directory. That is called from Dhcpv4Srv constructor, which is in turn
> controlled by direct_response_desired flag. Its default value is set to true.
> If you edit it (line 91 in src/lib/dhcp/dhcp4_srv.h) to false and recompile,
> it is possible that the code will be able to successfully use UDP sockets.
>
> Disclaimer: It's a quick hack. I haven't done any experiments with this, so
> it may break down. We can't apply it, as most people are interested in direct
> traffic, so a proper switch (either compile time or run time) is needed.
> That's something that we can't do immediately.
>
> Tomek
>
>
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
------------------------------
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
End of kea-dev Digest, Vol 6, Issue 15
**************************************
