Well, if nothing else, perhaps "rxbind" is your friend
It lists both the public and private IPs.
# ls /afs/ourdomain.com/
ls: /afs/ourdomain.com/: Permission denied
Back to the drawing board...
___
OpenAFS-devel mailing list
OpenAFS-devel@openafs.o
I disabled openafs-client from autostarting at boot.
To /etc/openvpn/openvpn.conf, I added
route-up "/etc/init.d/openafs-client start"
down-pre "/etc/init.d/openafs-client stop"
df shows...
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 8064432 23437
On Sun, 26 Nov 2006, Erik Osterman wrote:
It would appear that openvpn is started before openafs-client. In addition,
I've restarted the openafs-client several times after reboot with no avail.
openvpn 0:off 1:off 2:off 3:off 4:on5:off 6:off
openafs-client 0:off 1:off
It would appear that openvpn is started before openafs-client. In
addition, I've restarted the openafs-client several times after reboot
with no avail.
openvpn 0:off 1:off 2:off 3:off 4:on5:off 6:off
openafs-client 0:off 1:off 2:on3:on4:on5:on6:off
rc
Did the vpn net come up after OpenAFS was started?
On Sun, 26 Nov 2006, Erik Osterman wrote:
Thank you all for the thoughtful responses I've been receiving. kstart seemed
like the most secure solution, but ultimately, we've decided to go the
OpenVPN route since other parts of our application w
For what it's worth...
The following commands are run on the client server (10.0.0.6).
# ifconfig
tun0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.0.0.6 P-t-P:10.0.0.5 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICA
Thank you all for the thoughtful responses I've been receiving. kstart
seemed like the most secure solution, but ultimately, we've decided to
go the OpenVPN route since other parts of our application would benefit
from this private/secured network. We can always move to kstart once our
architec
Erik Osterman <[EMAIL PROTECTED]> writes:
> I have a question I've seen asked many times before. My problem is, I
> haven't been able to find a solution that works for us.
> Scenario: a cluster of VMs assigned dynamic IPs from shared networks,
> where each VM is a closed system running daemons th
Erik Osterman wrote:
I have a question I've seen asked many times before. My problem is, I
haven't been able to find a solution that works for us.
I'm not sure this should go to openafs-devel, but I'll leave that for
others to decide.
One solution I've seen is to wrap the process with an a
I have a question I've seen asked many times before. My problem is, I
haven't been able to find a solution that works for us.
Scenario: a cluster of VMs assigned dynamic IPs from shared networks,
where each VM is a closed system running daemons that need access to a
private OpenAFS cell. We a
10 matches
Mail list logo
