vyos-1x.git/data/templates/dhcp-client, branch current-merge-commit-handlingVyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
https://git.amelek.net/vyos/vyos-1x.git/atom?h=current-merge-commit-handling2024-04-01T12:04:50+00:00dhcpv6-client: T2590: fix vyos-hostsd update for nameserver and search domains2024-04-01T12:04:50+00:00Christian Breunigchristian@breunig.cc2024-04-01T12:04:50+00:00urn:sha1:ece425f0191762638b7c967097accd8739e9103d
After migrating from ISC DHCLIENT for IPv6 to wide-dhcp-client the logic which
was present to update /etc/resolv.conf with the DHCP specified nameservers and
also the search domain list was no longer present.
This commit adds a per interface rendered script to inform vyos-hostsd about
the received IPv6 nameservers and search domains.
op-mode: T6175: "renew dhcp interface <name>" does not check for DHCP interface2024-03-28T06:36:22+00:00Christian Breunigchristian@breunig.cc2024-03-28T06:36:22+00:00urn:sha1:7dbaa25a199a781aaa9f269741547e576410cb11
The current op-mode script simply calls sudo systemctl restart "dhclient@$4.service"
with no additional information about a client interface at all.
This results in useless dhclient processes
root 47812 4.7 0.0 5848 3584 ? Ss 00:30 0:00 /sbin/dhclient -4 -d
root 48121 0.0 0.0 4188 3072 ? S 00:30 0:00 \_ /bin/sh /sbin/dhclient-script
root 48148 50.0 0.2 18776 11264 ? R 00:30 0:00 \_ python3 -
Which also assign client leases to all local interfaces, if we receive one
valid DHCPOFFER
vyos@vyos:~$ show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address MAC VRF MTU S/L Description
----------- ----------------- ----------------- ------- ----- ----- -------------
eth0 - 00:50:56:bf:c5:6d default 1500 u/u
eth0.10 172.16.33.102/24 00:50:56:bf:c5:6d default 1500 u/u
eth1 172.16.33.131/24 00:50:56:b3:38:c5 default 1500 u/u
172.16.33.102/24 and 172.16.33.131/24 are stray DHCP addresses.
This commit moved the renew command to the DHCP op-mode script to properly
validate if the interface we request a renew for, has actually a dhcp address
configured. In additional this exposes the renew feature to the API.
dhcp-client: T5760: add CLI option to pass user-class parameter2023-11-19T20:47:31+00:00Christian Breunigchristian@breunig.cc2023-11-19T20:47:31+00:00urn:sha1:260645d0c6ff078cc89601f3a586195902f9c18e
Example:
set interfaces ethernet eth0 dhcp-options user-class VyOS
or
set interfaces ethernet eth0 dhcp-options user-class 56:79:4f:53
dhcp-client: T5760: add constraints for dhclient string options2023-11-19T20:43:15+00:00Christian Breunigchristian@breunig.cc2023-11-19T20:43:15+00:00urn:sha1:bed1cd01904ef89b5d31bd47de0f230214900f16
The string data type specifies either an NVT ASCII string enclosed in double
quotes, or a series of octets specified in hexadecimal, separated by colons.
For example:
set interfaces ethernet eth0 dhcp-options client-id CLIENT-FOO
or
set interfaces ethernet eth0 dhcp-options client-id 43:4c:49:45:54:2d:46:4f:4f
As of now there was no input validation performed.
Revert: dhcp: T5428: always release lease from default VRF2023-08-17T11:10:38+00:00Christian Breunigchristian@breunig.cc2023-08-17T11:07:22+00:00urn:sha1:1a69e9bb4b4e81a6191cb3d48e36542c36a6b763
This reverts commit 9afcea251bdc895ffd49cb11f455fd636fdf817b
A DHCP relese must also be originated from the VRF where the dhclient program is
running, else the RELEASE message can not be send through the interface towards
the DHCP server.
The reason it did not work in the past was because of https://vyos.dev/T5476
dhcp: T5428: always release lease from default VRF2023-08-07T21:05:12+00:00Christian Breunigchristian@breunig.cc2023-08-07T20:53:49+00:00urn:sha1:9afcea251bdc895ffd49cb11f455fd636fdf817b
Otherwise packet can be received in a VRF that was already deleted.
Image of the following CLI commands:
del interface ethernet eth0 address dhcp
del interface ethernet eth0 vrf red
del vrf name red
VRF could be deleted even if dhclient release was not yet completely
processed.
dhcpv6: T5428: client renewal fails when running inside VRF2023-08-05T07:28:35+00:00Christian Breunigchristian@breunig.cc2023-08-05T07:02:59+00:00urn:sha1:8a15595e1ac3d9e3e15f40f8b2256768f8d71f0cdhcp: T5428: remove hardcoded path to client runtime directories2023-08-05T07:28:03+00:00Christian Breunigchristian@breunig.cc2023-08-05T07:01:10+00:00urn:sha1:96132f582ef698b84d08e5ff207e508ed0f9c5f7dhcp: T5428: client renewal fails when running inside VRF2023-08-04T18:13:29+00:00Christian Breunigchristian@breunig.cc2023-08-04T18:13:29+00:00urn:sha1:782e400d6f276a8a4ee51c92f02e01e7695f55fb
vyos@vyos# run show vrf MGMT processes
2282 sshd
There is no dhclient process running in given VRF. dhclient complains it can
not send out packets via the given interface (as it's not bound to that VRF)
Aug 02 20:29:54 dhclient[1686]: send_packet: Network is unreachable
Aug 02 20:29:54 dhclient[1686]: send_packet: please consult README file regarding broadcast address.
Aug 02 20:29:54 dhclient[1686]: dhclient.c:3001: Failed to send 300 byte long packet over fallback interface.
dhcpv6-pd: T5387: add support for no-release flag2023-07-31T11:58:24+00:001vivy1vivy@tutanota.com2023-07-23T17:31:00+00:00urn:sha1:1d86092328ef43368fcb0bf348c14a01466e5892
When no-release is specified, dhcp6c client will not release allocated address or prefix on client exit.
vyos.ifconfig: dhcpv6: T5387: re-use options_file for no release flag [WIP]
* Todo: render Jinja2 template and fill it
vyos.ifconfig: dhcpv6: T5387: finish options_file and no release flag in cli
vyos.ifconfig: dhcpv6: T5387: fix missing/wrong end tag
vyos.ifconfig: dhcpv6: T5387: fix options, no var for -n
dhcpv6-client: T5387: fix missing / from filepaths