[OpenIndiana-discuss] Sun Rays might just be back on modern OI
Till Wegmüller
toasterson at gmail.com
Mon Feb 4 11:01:48 UTC 2019
Hi Carsten
Afaik there was a package or config item that made it work. Something related to multiseat stuff.
We had that on the mailinglist a while back 2017? And found a workaround. But I can not remember what it was.
Can anybody of the involved offer their input?
Jim are you using lightdm?
Greetings
Till
Am 4. Februar 2019 09:01:56 MEZ schrieb Carsten Grzemba <grzemba at contac-dt.de>:
>
><signaturebeforequotedtext></signaturebeforequotedtext>
>On 03.02.19 18:51, Jim Klimov <jimklimov at cos.ru> wrote:
>>
>> On February 3, 2019 2:09:47 PM UTC, Gary Mills
><gary_mills at fastmail.fm> wrote:
>> >On Sun, Feb 03, 2019 at 10:54:37AM +0000, Jim Klimov wrote:
>> >
>> >> And on my side, I dug into why that venerable piece of software,
>> >> the Sun DHCP server which I've actually used and liked, just up
>and
>> >> died in illumos-gate some years back (ultimately leading to its
>> >> removal), and what can be done about it.
>> >
>> >> Thanks to andyf I revived the SUNWdhcpd for the setup I maintain
>> >> and had to recently update to modern OI releases, see
>> >> http://www.jimklimov.com/2019/02/long-live-sunwdhcpd.html for
>> >> details and caveats, and
>> >> https://github.com/jimklimov/illumos-gate/tree/revive-SUNWdhcpd
>for
>> >> equivalent codebase fix :)
>> >
>> >You don't need the Sun DHCP server to operate Sun Ray terminals. You
>> >can use the ISC DHCP server instead. Here's what I used to use in
>the
>> >ISC configuration file:
>> >
>> > # Sun Ray vendor options
>> > option space NewT;
>> > option NewT.AuthSrvr code 21 = ip-address;
>> > ...
>> > subnet 192.168.0.0 netmask 255.255.255.0 {
>> > range 192.168.0.129 192.168.0.158;
>> > option subnet-mask 255.255.255.0;
>> > option broadcast-address 192.168.0.255;
>> > option routers 192.168.0.1;
>> > default-lease-time 600;
>> > max-lease-time 7200;
>> > if option vendor-class-identifier = "SUNW.NewT.SUNW" {
>> > vendor-option-space NewT;
>> > option NewT.AuthSrvr 130.179.16.87;
>> > }
>> > }
>> >
>> >This configuration specifies a dynamic IP address for the Sun Ray
>> >terminal, and 130.179.16.87 as the IP address of the Sun Ray login
>> >server. There's more that can be specified, but this is the minimum.
>> >
>> >The ISC configuration for Sun Ray terminals is all documented in
>> >Sun documents, now presumably Oracle Solaris documents.
>>
>> I suspected something of the kind =D
>>
>> I mean, surely any standard DHCP server can send proper packets at
>proper time, and nowadays a DNS setup could suffice, but the first
>thing (AFAIK) people trying to install or update SRSS is not having a
>dependency package for it, which is not too hard to work around but
>does complicate things. Also SRSS wizards being able to configure the
>address range by telling the DHCP server to do so was nice.
>>
>> And there's guys like me (oh, maybe only me?) actually using it as a
>generic DHCP server for a multi-subnet LAN of varied devices, not just
>Sun Rays, just because it is nifty with the macros and we always did ;)
>>
>> Anyhow, I had fun and learned something new as I scratched my
>long-standing itch, and can delay migrating that config to lots of
>repetitive lines ix n ISC DHCP files for a few more years =)
>>
>> Cheers,
>> Jim
>>
>I am suprised because I got not response for this problem:
>https://openindiana.org/pipermail/openindiana-discuss/2019-January/022692.html
>
>I my experiance SunRay SS do not work with lightdm. Is there a
>workaround?
>
>Carsten
>_______________________________________________
>openindiana-discuss mailing list
>openindiana-discuss at openindiana.org
>https://openindiana.org/mailman/listinfo/openindiana-discuss
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
More information about the openindiana-discuss
mailing list