From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] [GSOC] Dial between two computers
Date: Mon, 26 May 2014 17:52:27 -0700 [thread overview]
Message-ID: <CAJSxfmLu-mXFxdR1Wd35HgH56Q0tfqDqorgKBhRrNUobbpVm=A@mail.gmail.com> (raw)
In-Reply-To: <20140527001338.GO3763@iota.offblast.org>
[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]
works here (see below). i wonder if fossil is announcing on a different ip
than you're expecting?
% 9c dial.c
% 9l -o dial dial.o
% ./dial tcp!www.9netics.com!http
GET / HTTP/1.0
HTTP/1.1 200 OK
Server: Plan9
Date: Tue, 27 May 2014 00:50:46 GMT
ETag: "364d3v1b"
Content-Length: 2682
Last-Modified: Thu, 29 Aug 2013 22:51:43 GMT
Content-Type: text/html
Connection: close
<!DOCTYPE html>
<html>
...
On Mon, May 26, 2014 at 5:13 PM, Nick Owens <mischief@9.offblast.org> wrote:
> yan,
>
> did you try to use packet capture software like wireshark, or snoopy(8)
> on plan 9, to see the packets?
>
> running wireshark on linux, and snoopy on plan 9, will give you insight
> into if the packets reach the other side successfully.
>
> On Mon, May 26, 2014 at 08:06:21PM -0400, yan cui wrote:
> > Hi all,
> >
> > I used a program to dial from one system to another system, but
> > it gives a connection time out error. I have searched on Internet for a
> > long time and cannot get a solution. Could you please provide some
> > suggestions or hints? Basically, one system is Linux based system with rc
> > shell installed (we call it A). The other one is a auth+cpu+file server
> > (we call it B). On B, I have used fossil/conf command to listen
> tcp!*!564.
> > On A, I executed dial tcp!<B's ip address>!564, but it reports a time out
> > error after waiting some time. Results are the same when A is a plan9
> > terminal. By the way, I can ping A to B successfully. What could be the
> > possible problems?
> >
> >
> > Thanks, Yan
> >
> > --
> > Think big; Dream impossible; Make it happen.
>
[-- Attachment #2: Type: text/html, Size: 2396 bytes --]
next prev parent reply other threads:[~2014-05-27 0:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 0:06 yan cui
2014-05-27 0:08 ` yan cui
2014-05-27 0:13 ` Nick Owens
2014-05-27 0:52 ` Skip Tavakkolian [this message]
2014-05-27 1:30 ` yan cui
2014-05-27 1:51 ` Skip Tavakkolian
2014-05-27 2:18 ` yan cui
2014-05-27 2:26 ` Skip Tavakkolian
2014-05-27 2:37 ` yan cui
2014-05-27 3:02 ` Bakul Shah
2014-05-27 3:28 ` yan cui
2014-05-27 4:01 ` 有澤 健治
2014-05-27 3:49 ` yan cui
2014-05-27 4:01 ` Skip Tavakkolian
2014-05-27 16:03 ` yan cui
2014-05-27 1:20 ` yan cui
2014-05-27 12:38 ` erik quanstrom
2014-05-27 15:18 ` Skip Tavakkolian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJSxfmLu-mXFxdR1Wd35HgH56Q0tfqDqorgKBhRrNUobbpVm=A@mail.gmail.com' \
--to=skip.tavakkolian@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).