From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] communication between v2 and v3
Date: Thu, 20 Jul 2000 17:32:56 +0100 [thread overview]
Message-ID: <200007201632.MAA12423@cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 408 bytes --]
try this.
echo flush >'#a/arp/data' on v2 cpu/terminal
arp flush (i think) on a v2 file server console
and things might spring to life.
by changing the card you changed the MAC address
and thus the IP to MAC translation
but v2 systems will still retain the original translation until
you tell it otherwise. they will be sending to the card
that's now truly on the ether (out in the air).
[-- Attachment #2: Type: message/rfc822, Size: 2086 bytes --]
To: cse.psu.edu!9fans
Subject: [9fans] communication between v2 and v3
Date: Thu, 20 Jul 2000 10:52:42 -0400 (EDT)
Message-ID: <20000720142348.498.qmail@nx.aichi-u.ac.jp>
Hello,
I am in trouble.
I swapped my ether card from ne2000 to 3c905b.
The machine is standalone Plan9v3 terminal.
The result is weird.
The machine can communicate with UNIX using telnet --- not weird.
The machine turned unable to communicate with Plan9v2 servers
both on il and tcp --- weird!.
Plan9v2 servers are working as they have been --- not weird.
Snoopy can catch their packets at both end, that is, packets can
reach
the target mutually.
Their conversations suggest that v2 and v3 cannot synchronize.
All my v2 servers are running with 10M ether card,
and machines are connected using 10/100 switching HUB.
Suggestion welcome.
Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp
next reply other threads:[~2000-07-20 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-20 16:32 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-21 6:23 forsyth
2000-07-21 10:01 ` arisawa
2000-07-21 1:19 [9fans] setup? Colin DeVilbiss
2000-07-21 6:14 ` [9fans] communication between v2 and v3 arisawa
2000-07-20 14:52 arisawa
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=200007201632.MAA12423@cse.psu.edu \
--to=forsyth@vitanuova.com \
--cc=9fans@cse.psu.edu \
/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).