From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] HTTP forwarding with aux/trampoline
Date: Sun, 27 Sep 2009 16:32:24 -0400 [thread overview]
Message-ID: <fe41879c0909271332hb322102nfb75dc7bffd0208@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a0909271022n480f6f87jbba5f81d479804c0@mail.gmail.com>
> First, if you are not using hget to fetch the URL in question,
> use hget. That eliminates the browser.
I've tried with wget in the httpserver network. That's how I
got the 1666 bytes value.
> Second, if you run
>
> aux/listen1 tcp!*!80 rc -c 'sleep 1; cat /lib/words'
>
> can you use con -l tcp!yourserver!80 to get all of /lib/words?
No. I ran further test cases, and the outcome was that I get
all the data from:
aux/listen1 tcp!*!80 rc -c 'sleep 1; sed 170q /lib/words'
(and any amount of lines less than 170, from /lib/words)
but I get *no* output (using con(1) from outside the network)
with:
aux/listen1 tcp!*!80 rc -c 'sleep 1; sed 171q /lib/words'
(that is, the con(1) connection just waits and waits). With that
threshold, I found:
--rw-rw-r-- M 9714 akumar akumar 1447 Sep 27 12:52 tmp/170words
--rw-rw-r-- M 9714 akumar akumar 1454 Sep 27 12:53 tmp/171words
> Third, if you run hget on the machine where you normally
> run listen1, can you fetch the page normally?
I can get all of the data normally, *from* the httpserver, using
hget on the computer running listen1.
> I think Erik is right that you have MTU problems. I think that
> either the connection from 442 to listen1 or the connection
> from listen1 to your client machine has its device MTU set
> larger than some intermediate piece of network hardware
> allows, so that once the packets get too big they just start
> dropping on the floor, and for some reason the ICMP packets
> you'd need to do path MTU discovery on that connection are
> not getting through either. But you need to isolate the
> problem with a simpler test case first.
With the above test case of the first 171 lines of /lib/words,
I tried `{echo mtu 1492 > /n/ipifc/0/ctl}, as well as other MTU
settings (the default being 1514), but with none of them could
I send all (well, I didn't get *any* output from con(1), so I don't
think partial data was being sent either?) of the data out of the
network (it worked fine on the machine running listen1, itself,
of course).
Thanks,
ak
next prev parent reply other threads:[~2009-09-27 20:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 18:12 Akshat Kumar
2009-09-27 17:22 ` Russ Cox
2009-09-27 20:32 ` Akshat Kumar [this message]
[not found] <<fe41879c0909261112td0ee5e9s27959535cc94cbbd@mail.gmail.com>
2009-09-27 0:32 ` erik quanstrom
2009-09-27 2:24 ` Lyndon Nerenberg - VE6BBM/VE7TFX
[not found] <<fe41879c0909271332hb322102nfb75dc7bffd0208@mail.gmail.com>
2009-09-27 20:56 ` erik quanstrom
2009-09-28 0:52 ` Russ Cox
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=fe41879c0909271332hb322102nfb75dc7bffd0208@mail.gmail.com \
--to=akumar@mail.nanosouffle.net \
--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).