On Sat, Feb 01, 2003 at 02:59:58AM -0500, [EMAIL PROTECTED] wrote:
> >> I have a strange setup, where my ISP only allows one port for
> >> incoming traffic. However, that one port happens to be < 1024, so
> >> only root can bind to that port. I would not like to run freenet as
> >> root, as you can probably imagine. Is there a way for freenet to
> >> announce one port, but bind to another? Thanks.
> >
> > Just forward the port. You can use firewall rules for this.
> 
> I tried that already. What happens is, I tell Freenet that my port
> is some high number, say 12345. I then forward all traffic destined
> for my one available incoming port, say, 100, to 12345. However, the
> Freenet client keeps announcing that it is listening on port 12345,
> which is wrong. At least, that's what I think is happening. Any other
> suggestions?
Yuck.
Okay, I'll code support for it if you promise to make a $20 donation on
delivery :) It's pretty obscure stuff.

-- 
Matthew Toseland
[EMAIL PROTECTED][EMAIL PROTECTED]
Full time freenet hacker.
http://freenetproject.org/
Freenet Distribution Node (temporary) at http://amphibian.dyndns.org:8889/JpabimWi840/
ICTHUS.

Attachment: msg02777/pgp00000.pgp
Description: PGP signature

Reply via email to