Hello Otto,

There seem to be some side effects to the -t option.
What does the -t option do? There is not much documentation on it.
We are not really sure if it is related but after setting the -t option we experience unexpected sunray recycles. This is what I could find in the /var/opt/SUNWut/log/messages file at the time of a recycle.

Jul 13 17:33:04 raywyse12 utauthd: [ID 402071 user.info] Worker6 NOTICE: DISCONNECT IEEE802.0003bad73d20,
pseudo.0003bad73d20 reauthenticatingDuplicateTID
Jul 13 17:33:04 raywyse12 utauthd: [ID 164252 user.info] Worker6 NOTICE: DESTROY pseudo.0003bad73d20 lifetime=3743805 Jul 13 17:33:04 raywyse12 utauthd: [ID 565422 user.info] Worker6 NOTICE: whichServer pseudo.0003bad73d20: Jul 13 17:33:04 raywyse12 utauthd: [ID 846524 user.info] Worker6 NOTICE: CLAIMED by StartSession.m2 NAME: pseudo.0003bad73d20 PARAMETERS: {terminalIPA=62.163.103.22, type=pseudo, fw=3.1_32.08,REV=2005.08.24.08.55,Boot:1.6; 2004.10.28-14:47:01-PDT, state=disconnected, cause=insert, doamgh=true, barrierLevel=310, rawId=0003bad73d20, MTU=1500, tokenSeq=1, firstServer=c2a5270c, namespace=IEEE802, id=0003bad73d20, clientRand=nvNVoZAh79zx4h77NnzZLQ/jv3YMBNzSfv78WSKOwJ0, realIP=c0a80370, startRes=1280x1024, useReal=false, event=insert, pn=64346, sn=0003bad73d20, rawType=pseudo, hw=SunRayP7, initState=1, _=1} Jul 13 17:33:04 raywyse12 utauthd: [ID 956065 user.info] Worker6 NOTICE: CONNECT IEEE802.0003bad73d20, pseudo.0003bad73d20, all connections allowed

Any suggestion of this is indeed related to the -t option?

Kind regards,

Ivar

Ivar Janmaat wrote:

Thanks Otto,

This seems to do the trick.
In our case we don't need the devices so it is an inexpensive way of setting up multiple sunrays on remote locations.
If VPN gets build into the Sunray this might change of course.

Kind regards,

Ivar

ottomeister wrote:

On 7/6/06, Ivar Janmaat <[EMAIL PROTECTED]> wrote:

Unfortunately there was no response on my former E-mail on this issue.
The issue is: Two sunrays behind a NAT router are interfering, which
makes this setup unusable for production sites.



Edit the 'utsvc' rc script on the server and add a '-t' argument to the
'utsessiond' startup command line.  I think you'll need to do a cold
restart ('utrestart -c') to put that change into effect.

There's no particular reason why utsessiond defaults to disallowing
concurrent DTU connections from the same IP address, so if someone
filed a bug it probably wouldn't be hard to have the  '-t' behaviour
become the default.

Some Sun Ray features, mostly to do with peripheral devices, won't
work behind this kind of NAT.  This is one of the reasons why we
recommend using a VPN tunnel rather than an IP-masquerading NAT.

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



_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users



_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to