> Yes, provided they are compatible builds. There are two freenet's
> maintained by the freenetproject; stable and unstable. They are seperate
> networks that do not communicate with each other.
Btoh nodes are running NV 0.5, PV STABLE-1.50, BN 5074, CVS
1.90.2.50.2.101
> When you say "Each node has different routing tables so I'd like to be able
> to use the nodes together to increase the available search path within a
> couple hops or so", are you saying these two nodes are on different tcp/ip
> networks, or one node is from stable and another from unstable?
different TCP/IP networks
> > > > give me their node's reference but I keep getting complaints that the
> > > > ref does not contain an estimator fieldset. Is there a way to
> > > > generate complete files that have all the required information?
> > > > Each node has different routing tables so I'd like to be able to use
> > > > the nodes together to increase the available search path within a
> > > > couple hops or so.
> > > >
> > > > } a.b.c.d A.B.C.D {
> > > > a's routes } =-> nodeA <--> nodeB <-= { b's routes
> > > > } {
nodeA and nodeB are two different freenet nodes operating at separate IP
numbers nodeA has a set of routes, a's routes and nodeB has a set of
routes b's routes. I would like nodeA and nodeB to have a persitent
connection between each other in order to be able to use each other's
routes.
I'm getting way too many RNF/DNFs so any way to expand the available
routing would be a welcome thing either node. about 60% of the time it
doesn't even get off the originating node. I've tried putting each
other's node's ref into the seedfile but the nodes don't seem to want to
use them. As I said earlier the windows version just complains that there
are no estimator fieldsets for the noderef and won't import it.
On the freebsd node (at the other IP number) the only way I've gotten it
to use the other node is by making it the only entiry in the seedfile.
This had the disadvantage that not only was is restricted to whereever the
windows node could get to its available freenet routes, but to my
shock, it wasn't learning about visitors as many freenet docs have
suggested the node should be able to. Nodes would connect and it even
made outbound connections but it's list of available routes under the node
status subsection still reported only one host in the routing table.
I've ruled out firewall issues on both sides becuase both sides can
negotiate outbound connections and receive inbound connections. I've also
double check in the environment and the node are reporting the correct
WAN-side router IP numbers and access ports.
_______________________________________________
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]
