[EMAIL PROTECTED] wrote:
"Stoyan Angelov" <[EMAIL PROTECTED]> wrote:
i want to try the new DHCP options added in SRSS 3.1alpha, however
i don't know how to appropriately define them in the dhcpd.conf. i
use an external ISC DHCP server to drive my sunrays that are behind
cable modems.
i guess option 66 (tftp) should be defined like this:
option tftp-server-name code 66 = text;
option tftp-server-name "sunray.mydomain.net";
is this correct ?
Depending on your version of the ISC DHCP server this option might
already be defined as one of the built-in options. 'man dhcp-options'
here shows it as:
option tftp-server-name text;
If it's not already built in then your definition should work,
although I'd probably just set it to "sunray" and use the DHCP
domain-name option to tell the DTU that it should do lookups in the
"mydomain.net" domain.
Otto thank you for your answer! i did as you said and everything looks
good. i guess the real test will be when the new firmware is released -
it should update "the new way".
then sunray.mydomain.net cat resolve to multiple
ip-addresses in the DNS server.
Yes. You also need to provide the DHCP option (code 6,
"domain-name-servers") that tells the Sun Ray where to find your
DNS server so that it can look up the "sunray.mydomain.net" TFTP
server name.
where can i find the codes for options sunray-config-servers and
sunray-servers?
option sunray-config-servers code ?? = text;
option sunray-config-servers "sunray.mydomain.net";
option sunray-servers code ?? = text;
option sunray-servers "sunray.mydomain.net";
"sunray-config-servers" and "sunray-servers" aren't DHCP options.
They're the firmware's default DNS hostnames for a TFTP server and
a Sun Ray server. If DHCP provides the IP of a DNS server but does
not provide a tftp-server-name option then the firmware will look
up "sunray-config-servers" to get the IPs of TFTP servers that
might be able to supply a Sun Ray parameter file. If that doesn't
result in the firmware being told where to find a Sun Ray server
then the firmware will do a DNS lookup for "sunray-servers" and
will try to contact a Sun Ray auth daemon on those IPs. If DHCP
provided a domain-name option then, as you'd expect, these lookups
will be relative to that domain.
if all the DTU's are upgraded to the 3.1 firmware can i completely
remove the SUNW-NewT option space with all the old options from the
dhcpd.conf?
There are still some parameters that can only be set through DHCP,
so I wouldn't delete the SUNW vendor options yet. By the time we
get to 3.1 FCS it's likely that there'll be parameter-file
equivalents of all of the SUNW vendor options so at that point you
should be able to delete all of the SUNW option definitions *provided
that* you have some sort of strategy for getting new DTUs loaded with
3.1 firmware. Brand new ones will come from the factory with 3.0
firmware for a while, and if you pull spares out of a cupboard or buy
units from Ebay there's no telling what version of firmware they'll
contain. Maybe you'd keep one small private subnet running with a
DHCP server that delivers the SUNW vendor options, and plug new DTUs
into that subnet in order to get them laoded with 3.1 firmware.
this is great - in my case i do not directly manage the DHCP server that
the terminals use (it is managed by the guys that provision the cable
modems), so upgrading firmware will be easier. great job!
greetings,
Stoyan
OttoM.
__
ottomeister
Disclaimer: These are my opinions. I do not speak for my employer.
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
