On Tue, 27 Feb 2024 at 05:10, Brady Johnson wrote:
>
> We tried several changes to the client nmstate configuration. Setting "ipv4:
> dhcp: false" caused a configuration error in nmstate. We have created a bug
> for that and the nmstate team is working on it.
I didn't see it here
Right, but for this use case we didnt want the server to assign an IP to
the client.
Thanks,
*Brady Johnson*
Principal Software Engineer
Telco Verification Ecosystems Engineering
brady.john...@redhat.com
On Tue, Feb 27, 2024 at 4:40 PM Paul Wouters wrote:
> On Tue, 27 Feb 2024, Brady
On Tue, 27 Feb 2024, Brady Johnson via Swan-dev wrote:
We tried several changes to the client nmstate configuration. Setting "ipv4: dhcp:
false" caused a configuration error in nmstate.
We have created a bug for that and the nmstate team is working on it.
Then, we tried with the same client
We tried several changes to the client nmstate configuration. Setting
"ipv4: dhcp: false" caused a configuration error in nmstate. We have
created a bug for that and the nmstate team is working on it.
Then, we tried with the same client nmstate configuration, but added
"leftmodecfgclient: false"
