I wasn’t able to verify on my test system(maybe you’ll have better success),
On the last step setting up using the YAST DHCP Server applet,
You have an “expert” option which might allow you to set up custom options.
Have you been able to try that?
Just a comment… It’s been a very long time since I’ve looked at the YAST DHCP Server applet, IMO although it supports many common configurations, to be complete it should really support <all> the most common DHCP options which it doesn’t… Things like… name resolution node type, pushing custom Host and LMHost config files, custom startup options like what the OP in this thread is configuring.
By not displaying all the most common/useful DHCP options, most openSUSE Users won’t be aware of the things they can do with DHCP. I’d also guess that modifying YAST to implement a complete set of DHCP options would be next to trivial because it wouldn’t require much more code than is now used to select existing options.
Actually you do not have that “expert Option” in openSuSE 13.1.'s yast2 dhcp-server applet.
And when I leave the Applet I get a message on the console:
Use of uninitialized value $key in concatenation (.) or string at
/usr/lib/YaST2/servers_non_y2/ag_dhcpd_conf line 268, <STDIN> line 2 (#1)
(W uninitialized) An undefined value was used as if it were already
defined. It was interpreted as a “” or a 0, but maybe it was a mistake.
To suppress this warning assign a defined value to your variables.
To help you figure out what was undefined, perl will try to tell you
the name of the variable (if any) that was undefined. In some cases
it cannot do this, so it also tells you what operation you used the
undefined value in. Note, however, that perl optimizes your program
anid the operation displayed in the warning may not necessarily appear
literally in your program. For example, “that $foo” is usually
optimized into "that " . $foo, and the warning will refer to the
concatenation (.) operator, even though there is no . in
your program.
However, it is leaving the dhcpd.conf intact.
But as soon as I select the “use ldap” in the Applet, the
I’m a bit unclear,
But have you tried to enter <both> the LDAP and your PXE options in Expert Mode?
Just out of curiosity, and I don’t know what are in your PXE images…
I can conceive of a PXE image pre-configured for network authentication (eg LDAP) in which case it probably wouldn’t be necessary for your PXE clients to use a DHCP LDAP option.
Just sayin’…
There might be more ways than one to skin a cat, you might want to break up each part of the bootup process into discrete steps, then consider what is required or desired at each step. Offhand, I would guess unless you need LDAP authentication to gain network access to your PXE images, it’s not needed as a DHCP option (although could be a convenience).
As I said before: THERE IS NO EXPERT MODE IN YAST2 DHCP-SERVER IN openSuSE 13.1.
The only PXE-related Thing I am doing in dhcp.conf is to define the filename.
And this filename should be defined depending on the pxe-system-type (code 93).
EVERYTHING works fine as lonmg as do not start YAST2 DHCP-SERVER to do the DHCP configuration.
But I want to start YAST2 DHCP-SERVER because this seems to be the only way to configure DHCP to store ist configuratin in LDAP rather than in dhcp.conf.
Unfortunately the YAST app does not not the options I use.
Sorry to say that but what you posted is off-topic.
On Wed 02 Jul 2014 05:06:01 PM CDT, Suworow wrote:
tsu2;2652095 Wrote:
> I’m a bit unclear,
> But have you tried to enter <both> the LDAP and your PXE options in
> Expert Mode?
>
> Just out of curiosity, and I don’t know what are in your PXE images…
> I can conceive of a PXE image pre-configured for network
> authentication (eg LDAP) in which case it probably wouldn’t be
> necessary for your PXE clients to use a DHCP LDAP option.
>
> Just sayin’…
> There might be more ways than one to skin a cat, you might want to
> break up each part of the bootup process into discrete steps, then
> consider what is required or desired at each step. Offhand, I would
> guess unless you need LDAP authentication to gain network access to
> your PXE images, it’s not needed as a DHCP option (although could be
> a convenience).
>
> TSU
As I said before: THERE IS NO EXPERT MODE IN YAST2 DHCP-SERVER IN
openSuSE 13.1.
The only PXE-related Thing I am doing in dhcp.conf is to define the
filename.
And this filename should be defined depending on the pxe-system-type
(code 93).
EVERYTHING works fine as lonmg as do not start YAST2 DHCP-SERVER to do
the DHCP configuration.
But I want to start YAST2 DHCP-SERVER because this seems to be the only
way to configure DHCP to store ist configuratin in LDAP rather than in
dhcp.conf.
Unfortunately the YAST app does not not the options I use.
Sorry to say that but what you posted is off-topic.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-17-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!