TechnoSF ([EMAIL PROTECTED]) wrote:
> Yep, I was trying to avoid using the gateway (say 192.168.1.1) as a
> lan-wide (HTTP) fproxy and allow the windows clients (lets say the
> 192.168.2.0 network) to run freenet themselves in a P2P manner and
> have the gateway 'leek' the 192.168.2.0 traffic. In
Yep, I was trying to avoid using the gateway (say 192.168.1.1) as a lan-wide (HTTP)
fproxy and allow the windows clients (lets say the 192.168.2.0 network) to run freenet
themselves in a P2P manner and have the gateway 'leek' the 192.168.2.0 traffic. In
many respects to mirror an IP network whe
TechnoSF ([EMAIL PROTECTED]) wrote:
> I'm actually on Linux and Windows - Linux gateway, windows clients.
> I'm trying to configure a topology where Freenet sits on the gateway
> (with its single non-forwarding port, hopefuly bypassing the need for
> an upgraded to IPTABLES that I do not have the
[Unix version] Worked a treat Greg, thanks.
I'm actually on Linux and Windows - Linux gateway, windows clients. I'm trying to
configure a topology where Freenet sits on the gateway (with its single non-forwarding
port, hopefuly bypassing the need for an upgraded to IPTABLES that I do not have t
TechnoSF ([EMAIL PROTECTED]) wrote:
> So, Bob, Dwight har far did you get? After a couple of hours of trial
> and error, and a couple of searching the net, I think my node runs!
> Next, trying to figure out what its node key is...
The Windows installer creates myOwn.ref in the Freenet directory.
Me too... After watching Freenet for quite a while, I've now recently been in a
position to try it out. While by no means technically illiterate, I, as may others I
expect, will try and use Freenet (as other interesting projects) by installing first,
reading the degrees of documentation second
