| raw e-mail | index | archive | help
<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF=
-8">
</head>
<body>
<p>Hi,</p>
<p>Currently our ifreq interface supports nv(9) lists via
ifreq_nv_req. This allows network interface drivers to implement
their configuration using nvlists (for example: if_ovpn, if_pf*).</=
p>
<p>There is a problem: an interface that is implemented entirely via
nv(9) cannot be configured during the cloning phase (via
if_clone_create). if_clone_create converts the ifreq struct to
ifdrv and only copies ifr_data to params, so the ifru_nv field is
lost during cloning.</p>
I am interested in implementing a solution to this issue and am
considering two possible approaches:<br>
<ol>
<li>Extend the ifdrv struct to include the ifreq_nv_req struct,
and verify/make sure that other implemented modules are not
affected.</li>
<li>Introduce a new ioctl, SIOCIFCREATENV, to handle the nv part
separately, which would be more complicated but potentially less
disruptive to existing modules.</li>
</ol>
<p>Which one do you think would be more suitable, or do you have any
alternative suggestions?</p>
<pre class=3D"moz-signature" cols=3D"72">--
spmzt</pre>
</body>
</html>
--------------2bAdYUe6PGLfaMo7XtZQGDVk--
--------------9wq08ZILA4WavKoVBVGxosl0--
--------------Z03Ryq1ePNoYkxD83Gq2uVD0
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature.asc"
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQSqt7cppfvJ816gj0lUwVnUeMwagAUCaO9Q/wAKCRBUwVnUeMwa
gB51AQDir1XteA1qK5Lyyn4p0qyHZKh7o7kPddWI2O2wQEoh/AEA/3A9iWHGa0wQ
y7euY9mFO+wv1erHQr83iWVvBdLKywU=
=yj0d
-----END PGP SIGNATURE-----
--------------Z03Ryq1ePNoYkxD83Gq2uVD0--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?>