eblot/pybootd
1
1
Fork 0
mirror of https://github.com/eblot/pybootd.git synced 2024-09-11 22:17:44 +03:00
Code Issues Projects Releases Wiki Activity

Update doc file

Browse Source
This commit is contained in:
Emmanuel Blot 2020-04-13 14:43:15 +02:00
parent f4d0ab63e9
commit 46b4d11beb
1 changed files with 16 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
README.rst
View File

@ -42,7 +42,7 @@ Permissions
- HTTP optional daemon may be run on any port. - HTTP optional daemon may be run on any port.
As these ports are within the server's range (<1024), the superuser privileges As these ports are within the server's range (<1024), the superuser privileges
are required on Unix hosts (Linux, Mac OS X, ...) to start up these daemons. are required on Unix hosts (Linux, macOS, ...) to start up these daemons.
Status Status
@ -56,16 +56,16 @@ Supported features
- Access control: - Access control:
1. None (any remote host can be served) 1. None (any remote host can be served)
2. MAC address ACL 2. MAC address ACL
3. UUID based ACL - requires PXE protocol 3. UUID based ACL - requires PXE protocol
4. HTTP forwarding - authorization is delegated to a remote server using 4. HTTP forwarding - authorization is delegated to a remote server using
simple HTTP GET requests simple HTTP GET requests
- Local or remote file serving: - Local or remote file serving:
- For example, it is possible to boot up a full Debian system directly from - For example, it is possible to boot up a full Debian system directly from
the Internet, without storing any file on the pybootd host machine the Internet, without storing any file on the pybootd host machine
- Network notification of client requests through UDP messages - Network notification of client requests through UDP messages
@ -111,6 +111,14 @@ Common errors
Try listening on all IPv4 interfaces with ``address = 0.0.0.0`` and use ACL Try listening on all IPv4 interfaces with ``address = 0.0.0.0`` and use ACL
to discard requests from network you do not want to serve. to discard requests from network you do not want to serve.
DHCP client keeps requesting an address but seems to receive none
Some stupid clients - such as the ones implemented in BIOS/UEFI from Intel
silently ignore proper network broadcast packets. They only consider global
broadcast packets. The Ethernet MAC of such clients should be added to
the ``[buggy_clients]`` section, so that global broadcast packets are
generated for these clients.
Configuration Configuration
------------- -------------