From: Tim Moore <timothymoore@bigfoot.com>
To: Whit Blauvelt <whit@transpect.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.19 Realaudio masq problem
Date: Tue, 24 Apr 2001 18:01:05 -0700 [thread overview]
Message-ID: <3AE621D1.FE45602B@bigfoot.com> (raw)
In-Reply-To: <20010424201403.A1909@free.transpect.com>
I've been running masquerading unchanged from 2.2.13, currently 2.2.19 as:
real IP +
masq. 192.168.1.NNN
DSL <-> gateway <-> switch <-> client 1
server <-> client 2
...
<-> client n
There was some general slowness over the last few days (Bay Area, California
<-> US East Coast) including realaudio being unable to locate servers and/or
content. This one is working right now:
RealPlayer v 7.0.3.338
abit:~ > cat On24ram.asp
rtsp://rm.on24.com/media/news/04192001/palumbo_ted6.rm
--stop--
http://rm.on24.com/media/news/04192001/palumbo_ted6.rm
Try '# strace /usr/bin/X11/realplay On24ram.asp > log' and see where the
connect fails if you aren't getting specific error messages.
rgds,
tim.
Whit Blauvelt wrote:
>
> The Release Notes say "Fix problems with realaudio masquerading". Looked
> promising, since with 2.2.17 one masqueraded system (but not another) was
> having occassional problems with realaudio at some (but not all) sites.
>
> Compiled 2.2.19 with 'make oldconfig,' no to new options. Otherwise running
> with the same firewall and masquerading settings (and yes I built and
> installed ip_masq_raudio.o). Masquerading is otherwise working, but now
> neither masqueraded system can connect with realaudio - the realplay routine
> to find a way to make a connection automatically fails for both.
rgds,
tim.
--
next prev parent reply other threads:[~2001-04-25 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-25 1:14 2.2.19 Realaudio masq problem Whit Blauvelt
2001-04-25 1:01 ` Tim Moore [this message]
2001-04-25 18:38 ` Whit Blauvelt
2001-04-25 18:52 ` Dave Mielke
2001-04-25 20:56 ` Xavier Bestel
2001-04-25 23:12 ` Whit Blauvelt
2001-04-26 5:26 ` Xavier Bestel
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=3AE621D1.FE45602B@bigfoot.com \
--to=timothymoore@bigfoot.com \
--cc=linux-kernel@vger.kernel.org \
--cc=whit@transpect.com \
/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