From: yan cui <ccuiyyan@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 23:28:23 -0400 [thread overview]
Message-ID: <CAAVq3r=EaGORbtqAWxaYDwLLjw=ao5WdzY-9B=jmmsB3-dd2xw@mail.gmail.com> (raw)
In-Reply-To: <F76259F8-3274-4249-AD95-F3602842E65D@bitblocks.com>
[-- Attachment #1: Type: text/plain, Size: 6549 bytes --]
2014-05-26 23:02 GMT-04:00 Bakul Shah <bakul@bitblocks.com>:
> Does
>
> 9fs localhost
> ls /n/localhost
>
> work on your VM? If that works, and if you can ping in both directions,
>
these tests work on my system
> the other possibilities are
> a. firewall rules on the linux box or
> b. how you have set up your VM. If you are using it in the "bridge" mode,
> it should work (except for a.). If you are using using the virtualizer's
> (QEMU or VirtualBox or Parallels etc.) stack, you have to setup some port
> forwarding rules.
>
I used KVM, and use virt-manager to config the VM, do not use any advanced
options, just default. I will check the mode. Thanks!
>
> On May 26, 2014, at 7:37 PM, yan cui <ccuiyyan@gmail.com> wrote:
>
> sure.
>
> cat ndb
> ip=192.168.122.71 ipmask=255.255.255.0 ipgw=192.168.122.1
> sys=super
> dns=192.168.122.1
>
> cat netstat
> tcp 0 bootes Listen 564 0 ::
> tcp 1 bootes Listen 567 0 ::
> tcp 2 none Listen 110 0 ::
> tcp 3 none Listen 113 0 ::
> tcp 4 none Listen 143 0 ::
> tcp 5 none Listen 17005 0 ::
> tcp 6 none Listen 17006 0 ::
> tcp 7 none Listen 17007 0 ::
> tcp 8 none Listen 17009 0 ::
> tcp 9 none Listen 17010 0 ::
> tcp 10 none Listen 19 0 ::
> tcp 11 none Listen 21 0 ::
> tcp 12 none Listen 22 0 ::
> tcp 13 none Listen 23 0 ::
> tcp 14 none Listen 25 0 ::
> tcp 15 none Listen 513 0 ::
> tcp 16 none Listen 53 0 ::
> tcp 17 none Listen 565 0 ::
> tcp 18 none Listen 7 0 ::
> tcp 19 none Listen 9 0 ::
> tcp 20 none Listen 993 0 ::
> tcp 21 none Listen 995 0 ::
> tcp 22 network Closed 0 0 ::
> tcp 23 network Closed 0 0 ::
> tcp 24 network Closed 564 57021 192.168.122.1
> tcp 25 network Closed 39452 567 192.168.122.71
> tcp 26 network Closed 40392 567 192.168.122.71
> tcp 27 network Closed 567 57328 192.168.122.71
> tcp 28 network Closed 567 40392 192.168.122.71
> udp 0 network Closed 0 0 ::
>
>
>
> 2014-05-26 22:26 GMT-04:00 Skip Tavakkolian <skip.tavakkolian@gmail.com>:
>
>> can you supply the output from your cpu?
>> % cat /net/ndb
>> % netstat -n
>>
>>
>>
>> On Mon, May 26, 2014 at 7:18 PM, yan cui <ccuiyyan@gmail.com> wrote:
>>
>>> plan9 auth+cpu+file server runs on vm,
>>>
>>> $ telnet 192.168.122.71 564
>>> Trying 192.168.122.71...
>>> Connected to 192.168.122.71.
>>> Escape character is '^]'.
>>> Then, no response.
>>>
>>>
>>>
>>>
>>>
>>> 2014-05-26 21:51 GMT-04:00 Skip Tavakkolian <skip.tavakkolian@gmail.com>
>>> :
>>>
>>> the firewall here wont answer pings.
>>>>
>>>> you could check with netstat on your plan 9 and/or traceroute from your
>>>> linux system. btw, does your plan 9 cpu run in a vm? also does telnet on
>>>> the linux system behave the same way as your dial? e.g.
>>>> $ telnet <yourip> 564
>>>>
>>>>
>>>>
>>>> On Mon, May 26, 2014 at 6:30 PM, yan cui <ccuiyyan@gmail.com> wrote:
>>>>
>>>>> interesting.
>>>>> I also dial tcp!www.9netics.com!http, but failed. Actually,
>>>>> I cannot even ping it successfully. (other sites such as
>>>>> www.google.com can be pinged on my system.) By the way, if fossil
>>>>> uses another ip, how to find that?
>>>>>
>>>>>
>>>>> 2014-05-26 20:52 GMT-04:00 Skip Tavakkolian <
>>>>> skip.tavakkolian@gmail.com>:
>>>>>
>>>>> 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.
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Think big; Dream impossible; Make it happen.
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Think big; Dream impossible; Make it happen.
>>>
>>
>>
>
>
> --
> Think big; Dream impossible; Make it happen.
>
>
>
--
Think big; Dream impossible; Make it happen.
[-- Attachment #2: Type: text/html, Size: 10662 bytes --]
next prev parent reply other threads:[~2014-05-27 3:28 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
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 [this message]
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='CAAVq3r=EaGORbtqAWxaYDwLLjw=ao5WdzY-9B=jmmsB3-dd2xw@mail.gmail.com' \
--to=ccuiyyan@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).