From: Andor Demarteau <ademarte@students.cs.uu.nl>
To: blinux-list@redhat.com
Subject: Re: Speak-Freely Question.
Date: Thu, 9 Nov 2000 19:54:04 +0100 (MET) [thread overview]
Message-ID: <Pine.GSO.4.21.0011091952120.25284-100000@abeel.students.cs.uu.nl> (raw)
In-Reply-To: <20001109121032.A26997@tink.danley.com>
the 2076 and probably the 4076 ports are for the LWL (look whois
listening) services and are not needed by speakfrely itself.
The lowper-port of the 2 is the data-port, the upper-one is the
control-port.
Reflectors need a darn lot of bandwith btw, so keep that in mind.
The program itself works prefectly, it even does a good job wiht it's
windoz counterpart.
On Thu, 9 Nov 2000, Jim Danley wrote:
> Having just recently done this for my network, the details are still
> fresh in my mind.
>
> You need to allow UDP on ports 2074 and 2075 then TCP on port 2076.
> if you are planning to run or connect to a reflector, then allow UDP on
> ports 4074 and 4075 then TCP on port 4076.
>
> Jim
>
> On Thu, Nov 09, 2000 at 12:48:05PM -0500, Watson, Keith wrote:
> > Ok, here's the situ, My linux box is connected to a cable/dsl router (Great
> > firewall) But I cannot receive incoming packets from speakfreely. I need to
> > know what ports to open in order to pass the packets successfully.
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>
slainte leat freisin (cheers to you also),
-----------
Andor Demarteau E-mail: ademarte@students.cs.uu.nl
student computer science www: http://www.students.cs.uu.nl/~ademarte/
Utrecht University note: homepage is outdated, don't remind me!
-----------
Believe in yourself, know what you want, and make it happen!
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Watson, Keith
` Jim Danley
` Andor Demarteau [this message]
` rafal polonski
` Dave Mielke
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=Pine.GSO.4.21.0011091952120.25284-100000@abeel.students.cs.uu.nl \
--to=ademarte@students.cs.uu.nl \
--cc=blinux-list@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).