

tsafa wrote:asrun, Ants uses two port number. x and x+1 you can set it to what ever number you want. The defult is 4567 and 4566 . I think you might also be looking at that part in setting at "open http service" leave that off for now. That is if you want to set up a webpage and publish it anonymously through ants. You can try that down the road if you want. It is very easy and i have written instruction on how to do that. The main thing is to get into the IRC chanel. There you will find people like me that will be happy to help you further.
If you are connecting from USA please use IRC.US.AZZURRA.ORG as default IRC server in Settings tab. The chanel is #ants-peers. All this should come up by defult.
AussieMatt wrote:Asuran are you running a old version of Ants that irc channel and server is Default for old versions .The latest version is 0.2.9 ; you should use the autoinstaller version on Grwen's website to get up to date.
But if you cant use those ports you can change them in the connection pannel and then forward the ports if you can.
I would be getting another ISP or are you behind a school network if you can only access those ports.
gwren wrote:I'm going to answer ya...
Your open ports are ok, you can connect... but you need help.
First: you don't need to care about your ants port, you are natted so you cannot receive incoming connection, facus instead on other nodes port.
As you cannot connect to irc, it is mandatory for you using a trusted peer, your trusted peer MUST be a node running ants on any of your free ports... so you can ask in the channel if someone with a permanent ants can act as a gateway for you, he simply have to run ants on 80 port instead of 4567, and you simply have to put his ip in trusted peers with port 80. It's a bit tricky but it works...

gwren wrote:LOL som many? Emule opens 50/100 ports and three ports are many?
Anyway let's answer:
4567 -> Main connection listener
4568 -> server that gives back a few ips of nodes with free connection slots
XXXX -> You irc outgoing connection.
Only if you activate HTTP Service on port 80 and you want a proxy on port 8080
1)8080 -> MUST BE FIREWALLED
2)80 -> MUST BE FIREWALLED (It's your webserver port)
These two ports are opened only locally, they must not be port opened to the net! You need a webserver on port 2) and you use the proxy at 8080 to access any othe webserver on ants...
Ants I found was crap when I first used it. It used nothing more than the IRC network and the only it really could be secure is if you only traded amongst friends. Any retard could enter the channel. I find the program nothing new and it basically to me another way of accessing IRC.
Now if you are interested in trading amongst friends you can form your own groups with programs like Exosee or WASTE.
Their are negative sides to each of these programs though. WASTE needs a central Server but has ecryption. Exosee has no Ecryption but not so a strong need for a central server.
I had trouble connecting to other people in WASTE especially people with routers. However I found Exosee a breeze to setup and use but NO ecryption. But you are trading amongst friends. So it should be ok?
If I have anything wrong please correct me Smile

gwren wrote:mmm... I suppose I should laugh...![]()
Have I said LISTEN PORTS? I said PORTS!
Asuran wrote:Also what do the 3 different ports stand for in the settings? Usually programs work just fine with one listen port.
Project description
Abstract
The main problems of the 2-nd generation p2p nets (as well as the 1-st one) are two: the complete lack of privacy and data protection and the lack of structured queries. Doing queries over the net we can see who's connected and what he's sharing. This is not acceptable if we care about our privacy... furthermore we usually have many problems in finding what we are looking for: queries support in common p2p system is usually not-stuctured and exact text-matching based, so we cannot exploit SQL-like features (join and so on...) over the net data-set. This project tries to resolve both the problems.
The privacy problem
It faces the privacy one breaking the ebsence of p2p... I mean a connection is not anymore point 2 point in the strict sense... the peers are virtual peers over a virtual net, so when we are requiring a resource over the net, our request is routed through many points utill it reach our peer. The peers are not anymore identified by ip... the have a unique ID produced hashing infos from their time and their location (this yields a unique hash). So a client now knows only the ips of its neighbours (the other peers directly connected to it), but it doesn't know their ID, as only the same node knows its ID. So what about routing, how can a node route a message if it doesn't know where the destination is? Simple... a node will know which are the "best" direction to route a message to, but it will not know where precisely another node is. The routing protocol has been developed over studies on ants behaviour... ants do not know the precise location of their hive, they simply follow a track... the same happends in this system. So the more messages follow a track the more that track will be "strong", if a track produces many failures it'll fade out and it won't be followed anymore. This way we can achieve privacy over our identity, but what about the informations sent? They have to route through many peers so how can we protect 'em? The protection is realized at 2 levels... low level (against man-in-the-middle extern to our net) by crypting communication between each couple of directly linked points of the net, high level (against internal threats) crypting the communication between the two end points. At both level the security is granted using a DH-KA and DES or AES (negotiated at the beginning).
The queries problem
Another solution has been found for the query problem. Each query is distributed (in a non deterministic and sequential way) over a part of the net. It is processed by each node it passes and at last it is returned to the source following the shortest path. Each node can process operations more complex than the simple text-matching: we can support pseudo high level SQL-queries over the data-set reppresented by our partial explored net.
Efficiency issues
We talked about a wide spread net that comprises very etherogeneous kind of nodes (lan connection as well as 56k) how can we support efficiency? The routing protocol is studied to find the best path to route a message... but if the path is not present we cannot find it. So we have to create a well structured net with a sufficient number of "routing point" (I mean pseudo server point with high speed connection and high connectivity (about 30 peers connected). The peers don't need to know the address of these points... we can structure the service creating few (hidden) routing points and many access points. At the startup one can choose if becoming an access point or a simple peer, every group of people can also create their own net with routing points and simple peers (a very scalable system). Computer simulation over the routing protocol have shown its efficiency over both the cases: with or without many routing points... in practice the virtual net is a sort of neural network that learns during its life and distributes the traffic in the best way.
About the IRC based connection system
Is there any threat due to the IRC based connection system? Is it dangerous that my IP appears on IRC? NO! Because ANts Net and IRC net are two distinct nets and the first has nothing to do with the sencond. I mean, when you log on IRC starting your ants client you usually join a chat room. In the chatroom you'll find other peers, each peers in the channel runs a particular server at port 4568, this is called the address server. The address server is a sort of crawler that roams around the ANts net collecting the IPs of every node that has free slots for new peers that want to access the ANts net. So each node of the ANts net will manage a list of these IPs with free slots. Through IRC (by a simple message) you can obtain the address of a peer running the server and already connected to the net. Once you have the address of the address server you can query that peer for IPs you can connect to. Once you are connected to the ANts net you'll crawl the net too for addresses with free slot (I mean your address server), and other peers will crawl through your node. This cause no threat because giving back your address to a query does not give any info to other peers about your location or about the ID you are using. Also if you are the only peer connected to another, the other cannot know if you are the only peer connected or if other peers without free slots are connected to you (same as for normal queries... noone knows who really answers queries).
Network architecture: WASTE uses a distributed architecture that allows for nodes to connect in a partial mesh type network. Nodes on the network can broadcast and route traffic. Nodes that are not publicly accessible or on slow links can choose not to route traffic. This network is built such that all services utilize the network, so firewall issues become moot.
Users browsing this forum: No registered users and 1 guest