Would putting a NetRestrict file on the clients do any good?

Jason

Derrick Brashear wrote:
> at the moment serverprefs is as good as you can get. you want a split
> horizon vlserver; at the moment there is no such animal
>
> Derrick
>
>
> On Sep 10, 2009, at 22:28, "Ryan C. Underwood"
> <nemesis-lists@iceq...> wrote:
>
>>
>> Yeah, I had to fix up all that junk with vos
>> changeloc/remsite/addsite/release on all the affected volumes, then fs
>> setserverprefs the bogus ip to 64000 and fs flushv on all the clients,
>> but I think it's all good now unless there's a hidden gotcha I missed
>> somewhere.  At least I seem to be able to access the RW and RO versions
>> of whatever I tested.
>>
>> By the way, how do I set it up such that the external server IPs will
>> never attempt to be contacted by internal clients?  Is it sufficient to
>> do it with fs setserverprefs in the startup scripts?  Is there a better
>> way?
>>
>> Ryan
>>
>> On Thu, Sep 10, 2009 at 09:17:49PM -0400, Derrick Brashear wrote:
>>> make sure vos listvl -server (the bogus address) returns nothing, or
>>> you
>>> aren't done
>>>
>>> Derrick
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@open...
> https://lists.openafs.org/mailman/listinfo/openafs-info
>

_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@open...
https://lists.openafs.org/mailman/listinfo/openafs-info