Hi Cristian,
>>> When enabled in [Network] it will set up a dhcp server on the interface,
>>> listening
>>> on one of its statically configured IPv4 addresses and with a fixed size
>>> pool of
>>> leases determined from it.
>> Hi Tom,
>> before looking at the code, a couple of general questions:
El 26/05/14 22:38, Zbigniew Jędrzejewski-Szmek escribió:
On Mon, May 26, 2014 at 09:39:46PM +0200, Tom Gundersen wrote:
When enabled in [Network] it will set up a dhcp server on the interface,
listening
on one of its statically configured IPv4 addresses and with a fixed size pool of
leases dete
On Mon, May 26, 2014 at 09:39:46PM +0200, Tom Gundersen wrote:
> When enabled in [Network] it will set up a dhcp server on the interface,
> listening
> on one of its statically configured IPv4 addresses and with a fixed size pool
> of
> leases determined from it.
Hi Tom,
before looking at the cod
Make sure we don't hand out the same IP twice. We still don't
handle lease expiry.
---
src/libsystemd-network/dhcp-server-internal.h | 25 -
src/libsystemd-network/sd-dhcp-server.c | 136 --
src/libsystemd-network/test-dhcp-server.c | 59 +++
3 files
When enabled in [Network] it will set up a dhcp server on the interface,
listening
on one of its statically configured IPv4 addresses and with a fixed size pool of
leases determined from it.
Example:
[Match]
Name=ve-arch-tree
[Network]
Address=192.168.12.5/24
DHCPServer=yes
[Route]
Gateway=192
---
src/libsystemd-network/dhcp-server-internal.h | 3 +
src/libsystemd-network/sd-dhcp-server.c | 150 ++
2 files changed, 153 insertions(+)
diff --git a/src/libsystemd-network/dhcp-server-internal.h
b/src/libsystemd-network/dhcp-server-internal.h
index 58a9877..
---
src/libsystemd-network/sd-dhcp-server.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/src/libsystemd-network/sd-dhcp-server.c
b/src/libsystemd-network/sd-dhcp-server.c
index 44ca645..3ed93d8 100644
--- a/src/libsystemd-network/sd-dhcp-server.c
+++ b/src/libsystemd-network/sd-dh
---
src/libsystemd-network/sd-dhcp-server.c | 27 ++-
1 file changed, 26 insertions(+), 1 deletion(-)
diff --git a/src/libsystemd-network/sd-dhcp-server.c
b/src/libsystemd-network/sd-dhcp-server.c
index 3ed93d8..2d789be 100644
--- a/src/libsystemd-network/sd-dhcp-server.c
---
src/libsystemd-network/dhcp-server-internal.h | 5 +++
src/libsystemd-network/sd-dhcp-server.c | 30 --
src/libsystemd-network/test-dhcp-server.c | 57 +++
3 files changed, 88 insertions(+), 4 deletions(-)
diff --git a/src/libsystemd-network/dhcp
---
src/libsystemd-network/sd-dhcp-server.c | 36 +++
src/libsystemd-network/test-dhcp-server.c | 6 +++---
2 files changed, 35 insertions(+), 7 deletions(-)
diff --git a/src/libsystemd-network/sd-dhcp-server.c
b/src/libsystemd-network/sd-dhcp-server.c
index 01cd8b
---
src/libsystemd-network/dhcp-server-internal.h | 3 +
src/libsystemd-network/sd-dhcp-server.c | 135 +-
src/libsystemd-network/test-dhcp-server.c | 37 +++
src/systemd/sd-dhcp-server.h | 1 +
4 files changed, 171 insertions(+), 5 delet
---
src/libsystemd-network/sd-dhcp-server.c | 81 ++-
src/libsystemd-network/test-dhcp-server.c | 14 +++---
2 files changed, 86 insertions(+), 9 deletions(-)
diff --git a/src/libsystemd-network/sd-dhcp-server.c
b/src/libsystemd-network/sd-dhcp-server.c
index cea739
---
src/libsystemd-network/dhcp-server-internal.h | 1 +
src/libsystemd-network/sd-dhcp-server.c | 13 +
src/libsystemd-network/test-dhcp-server.c | 17 +
src/systemd/sd-dhcp-server.h | 1 +
4 files changed, 32 insertions(+)
diff --git a/sr
---
src/libsystemd-network/dhcp-server-internal.h | 1 +
src/libsystemd-network/sd-dhcp-server.c | 14 ++
2 files changed, 11 insertions(+), 4 deletions(-)
diff --git a/src/libsystemd-network/dhcp-server-internal.h
b/src/libsystemd-network/dhcp-server-internal.h
index cd480e7.
We would like to use the UDP socket, but we cannot as we need to specify
the MAC address manually.
---
src/libsystemd-network/dhcp-server-internal.h | 1 +
src/libsystemd-network/sd-dhcp-server.c | 11 +++
2 files changed, 12 insertions(+)
diff --git a/src/libsystemd-network/dhcp-s
We will (at least at first), restrict our focus to running the server
on at most one interface.
---
src/libsystemd-network/dhcp-server-internal.h | 2 ++
src/libsystemd-network/sd-dhcp-server.c | 22 +-
src/libsystemd-network/test-dhcp-server.c | 3 ++-
src/systemd/
Parse the maximum message size the client can accept and the client id, falling
back to
sane defaults if they are not set.
---
src/libsystemd-network/dhcp-server-internal.h | 15 +
src/libsystemd-network/sd-dhcp-server.c | 88 ++-
2 files changed, 101 insertions(
---
.gitignore| 1 +
Makefile.am | 12
src/libsystemd-network/dhcp-network.c | 1 +
src/libsystemd-network/dhcp-server-internal.h | 40
src/libsystemd-network/sd-dhcp-server.c | 92 +
This is the beginning of DHCPv4 server support in networkd.
The main usecase I'm targeting is to be able to hand out DHCP
leases to containers on the local machine.
I have attempted to keep the library as minimal as possible to
make reviewing easier, but we'd abviously need a few more
features be
For this to work nicely we need to use REUSEADDR so that more than one socket
can be open at the same time. Also, we request the ifindex to be appended
to incoming messages, so we know whence it came.
---
src/libsystemd-network/dhcp-network.c | 15 +--
1 file changed, 13 insertions(+),
Bind to UDP socket and listen for messages, discarding anything we receive.
---
src/libsystemd-network/dhcp-server-internal.h | 2 +
src/libsystemd-network/sd-dhcp-server.c | 89 +++
src/libsystemd-network/test-dhcp-server.c | 6 ++
src/systemd/sd-dhcp-server.h
On Mon, Feb 24, 2014 at 07:35:12PM +0100, Thomas Bächler wrote:
> Am 24.02.2014 17:10, schrieb Lennart Poettering:
> > On Fri, 21.02.14 11:55, Thomas Bächler ([email protected]) wrote:
> >
> >> Both systemd-analyze and systemd-run only access org.freedesktop.systemd1
> >> on the bus. This patch
Hi,
I have following problem - I want to run processes from ssh which outlive the
connection (think tmux or mosh) but I cannot get it to work. I believe that
the processes are killed when the slice is killed as even opening new PAM
session does not help and the process is still displayed in the
Hi, all
In a pure initramfs enviroment, I want to mount a filesystem and I put
an mount entry in /etc/fstab, so that fstab-generator could generate a
mount unit and systemd will mount it at some time.
I have a question about mount failure in such case:
How can I make sure that upon a mount failu
24 matches
Mail list logo
