Thank you very much, Richard.
> A long delay when connecting to a server behind a firewall may be an
> attempt to connect to the secstore port.
I'm not running secstore yet at the target (Plan 9-2) auth server.
> Can you configure the firewall to open tcp port 5356?
Yes, I can.
I'll try this soon. I'm now in a very tough time schedules, because of
our comming new year, semester, here.
Our situation is as this figure. Plan 9-1 and Plan 9-2 have local ip
addresses,
say 192.168.1.xx for Plan 9-1, 192.168.50.xx for Plan 9-2. Both firewall
machines have global ip addresses.
real wall
___________ || other building
____________
| Plan 9-1 |==>Linux box's <=============>another firewall<=| Plan 9-2
|
| (Ken's fs, | firewall Univ LAN BB router
| venti+fossil+ |
| auth server, |
MZK-40g?? | cpu server, |
| cpu server, | other Debian
| terminals |
|terminals) | machines
|Debian, XP etc |
| Windows XP|
_____________
-----------
Now attempting to reach from Plan 9-1 domain terminal to Plan 9-2 system.
One correction of my last mail:
I can boot Plan 9 terminal in the Plan 9-1 domain using Plan 9-2 file/auth
server. It was just too long time than I can wait. 5.5 minutes from
boot the kernel to a factotum responce of Plan 9-2 server, and 5 more minutes
from it to get rio system (after type of password), total=10.5 minutes.
Yes, then, I judged it failed to bootup. After the success of bootup,
there is no problem, and I can use the Plan 9 teminal as usual way.
I cannot solve this tommorow, Friday maybe.
Kenji
