>> and build a 'gateway' static node with an internal (for intranet) address and a public (for world) address?
> This is not currently implemented. What you want is a node that only transmits its reference to internal nodes, but to external nodes appears transient. nope, I'm thinking about a gateway/router node that is static both for internal and external nodes. but it should uses different references because for internal it's 192.168.x.x and for external it has a public IP. in this way, this node is a junction-ring for LAN and Internet. I'm thinking about a LAN-freenet with some gateway/router-nodes (with a public IP and a LAN IP) and several static (192.168.x.y) nodes. > How do you want to define internal versus external nodes? IP address ranges would be the simplest thing. Yes, I think it could be inserted as a list in the configuration of gateway nodes... but in this way it's a _static_ list... What about 2 routing tables for these 'special' nodes? (one for internet nodes and one for LAN nodes?) It could be useful for university-lab, business-lan, or other big lan like WAN or other situation where is not possible for every nodes to reach, or be visible from, the external world. regards. _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
