Here is the nmstate pull request to fix the dhcp issue. https://github.com/nmstate/nmstate/pull/2556
I requested to see if it is possible to see the configuration Libreswan generates or if nmstate directly communicates with Libreswan via Whack messages. I'll report back with more info about that. Thanks, *Brady Johnson* Principal Software Engineer Telco Verification Ecosystems Engineering brady.john...@redhat.com On Tue, Feb 27, 2024 at 9:34 PM Andrew Cagney <andrew.cag...@gmail.com> wrote: > On Tue, 27 Feb 2024 at 05:10, Brady Johnson <brady...@redhat.com> 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 https://github.com/nmstate/nmstate/issues ? I'd > like to track it, i filed > https://github.com/nmstate/nmstate/issues/2568 > > Is there an easy way to display what nmstate generated? > > > Then, we tried with the same client nmstate configuration, but added > "leftmodecfgclient: false" and this allowed us to establish the tunnel. > > > > So, apparently, the "ipv4: dhcp: true" nmstate configuration causes the > client to request IP addresses and DNS. And setting "leftmodecfgclient: > false" overrides that in the nmstate configuration. > > Yes. I suspect it is adding leftmodecfgclient=true to the generated > config file > >
_______________________________________________ Swan-dev mailing list Swan-dev@lists.libreswan.org https://lists.libreswan.org/mailman/listinfo/swan-dev