From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <019b4d8a18ccf5b5ee8588951200206f@hera.eonet.ne.jp> To: 9fans@9fans.net Date: Wed, 26 Mar 2008 20:19:45 +0900 From: kokamoto@hera.eonet.ne.jp In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Plan 9 system behind firewall Topicbox-Message-UUID: 815bc64e-ead3-11e9-9d60-3106f5b1d025 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