|
804
|
1 <html><body bgcolor="#000000"><font color="white"> |
|
|
2 <pre> |
|
|
3 <b>DESCRIPTION:</b> |
|
|
4 |
|
884
|
5 peer2anonet is an autoconfiguration utility for |
|
|
6 setting up core services on AnoNet2. Enjoy :-). |
|
804
|
7 |
|
|
8 <b>DEPENDS ON:</b> |
|
|
9 |
|
884
|
10 quicktun, bird, bash for now. it also installs |
|
|
11 some cool shit that you'll use later. |
|
804
|
12 |
|
|
13 <b>AUTHOR:</b> |
|
|
14 |
|
|
15 d3v11 from <a href="http://www.d3v11.ano/">www.d3v11.ano</a>, somtimes, maybe, dunno. |
|
|
16 |
|
884
|
17 <b>REPORT BULLSHIT TO:</b> |
|
804
|
18 |
|
884
|
19 /relayhell/d3v11 |
|
804
|
20 |
|
884
|
21 d3v11@d3v11.ano |
|
804
|
22 |
|
|
23 <b>USAGE:</b> |
|
|
24 |
|
884
|
25 ./contrib/peer2anonet/peer2anonet --help |
|
|
26 ./contrib/peer2anonet/peer2anonet --rtfm |
|
804
|
27 |
|
884
|
28 <b>TORIFY:</b> |
|
804
|
29 |
|
884
|
30 --install-* flags should be compatible with Tor: |
|
804
|
31 |
|
884
|
32 export http_proxy='http://127.0.0.1:8118/' |
|
|
33 ./contrib/peer2anonet/peer2anonet --install-* |
|
804
|
34 |
|
901
|
35 You can use torify or usewithtor on most options |
|
|
36 but setting http_proxy is more reliable. |
|
|
37 |
|
884
|
38 torify ./contrib/peer2anonet/peer2anonet --install-* |
|
804
|
39 |
|
884
|
40 usewithtor ./contrib/peer2anonet/peer2anonet --install-* |
|
878
|
41 |
|
884
|
42 <b>CONFIGURE:</b> |
|
804
|
43 |
|
884
|
44 I highly recommend that before you use peer2anonet |
|
|
45 you ./configure resdb with tinydns support. |
|
804
|
46 |
|
884
|
47 ./contrib/peer2anonet/peer2anonet --configure |
|
877
|
48 |
|
884
|
49 <b>EXAMPLES:</b> |
|
877
|
50 |
|
884
|
51 Enter your AnoNet subnet: 1.1.5.0 |
|
|
52 Enter your AnoNet router: 1.1.5.1 |
|
|
53 Enter your peering ip: 1.1.5.2 |
|
|
54 Enter your AnoNet asn: 1150 |
|
877
|
55 |
|
884
|
56 <b>CONFIGURE PEER:</b> |
|
804
|
57 |
|
884
|
58 ./contrib/peer2anonet/peer2anonet --configure-peer |
|
804
|
59 |
|
884
|
60 <b>KEY PAIRS:</b> |
|
804
|
61 |
|
884
|
62 before running peer2anonet to configure peers |
|
|
63 you can use quicktun to generate keypairs: |
|
804
|
64 |
|
884
|
65 quicktun.keypair < /dev/random |
|
|
66 |
|
|
67 <b>EXAMPLES:</b> |
|
804
|
68 |
|
884
|
69 Enter your peer's name: d3v11 |
|
|
70 Enter your peer's remote ip: 11.11.55.1 |
|
|
71 Enter your peer's peering ip: 1.1.5.2 |
|
|
72 Enter your peer's remote port: 21150 |
|
|
73 Enter your local port: 61150 |
|
|
74 Enter your peer's asn: 1150 |
|
|
75 Enter your peer's public key: * see KEY PAIRS above * |
|
|
76 Enter your private key: * see KEY PAIRS above * |
|
804
|
77 |
|
884
|
78 <b>/SERVICE/$PEER/RUN CHANGES:</b> |
|
804
|
79 |
|
884
|
80 peer2anonet exports the /service/$PEER/run file to |
|
|
81 /etc/peer2anonet/peers/$PEER/run. If you need to |
|
|
82 create customizations for peerings then make |
|
|
83 adjustments to that file. |
|
804
|
84 |
|
884
|
85 <b>CONFIGURATION FILES:</b> |
|
804
|
86 |
|
884
|
87 If /etc/peer2anonet/bird.conf exists, then |
|
|
88 peer2anonet will not create a new bird. Instead |
|
|
89 it will use this bird.conf and append new protocols |
|
|
90 to it. |
|
804
|
91 |
|
884
|
92 /etc/peer2anonet/peers/$PEER/* contains: |
|
804
|
93 |
|
884
|
94 asn local_port peering_ip pubkey |
|
|
95 remote_ip remote_port run seckey |
|
804
|
96 |
|
884
|
97 In the event you want to reconfigure a peer's tunnel |
|
|
98 you can alter the run file and do `--update', rm run |
|
|
99 and modify the above files then use `--update', or |
|
|
100 reconfigure the peering tunnel altogether with |
|
|
101 --configure-peer and choose that peer's name. If you |
|
|
102 think this is absurd then you're probably right! I |
|
|
103 plan on doing something with these files later. |
|
804
|
104 |
|
884
|
105 <b>CONFIGURE DNS:</b> |
|
804
|
106 |
|
884
|
107 If you did not ./configure resdb with tinydns support |
|
|
108 then you need to do that before using this function. |
|
804
|
109 |
|
884
|
110 also before using you will need to have installed |
|
|
111 daemontools, djbdns, and ucspi-tcp. peer2anonet |
|
|
112 can do this for you with --install-* options. |
|
804
|
113 |
|
884
|
114 ./contrib/peer2anonet/peer2anonet --configure-dns |
|
|
115 |
|
|
116 <b>UPDATE DNS:</b> |
|
804
|
117 |
|
884
|
118 After a successful `--configure-dns', you can now |
|
|
119 enjoy to use `--update-dns' to bring your AnoNet |
|
|
120 domains up to speed. |
|
804
|
121 |
|
901
|
122 <b>SETUP QMAIL:</b> |
|
|
123 |
|
906
|
124 <b>WARN:</b> |
|
|
125 |
|
|
126 You should patch or firewall off qmail from |
|
|
127 reaching IcannNet so someone cannot harvest |
|
|
128 your IP with the mailerdaemon response. |
|
|
129 |
|
901
|
130 If you did not ./configure resdb with tinydns support |
|
|
131 then you need to do that before using this function. |
|
|
132 |
|
|
133 also before using you will need to have installed |
|
|
134 daemontools, djbdns, and ucspi-tcp. peer2anonet |
|
|
135 can do this for you with --install-* options. |
|
|
136 |
|
|
137 setup-qmail will download and install qmail if it |
|
|
138 isn't already installed and configure your |
|
|
139 mx domain as a.mx.$nick.ano with the ip of your |
|
|
140 resdb git-daemon ip. |
|
|
141 |
|
|
142 ./contrib/peer2anonet/peer2anonet --setup-qmail |
|
|
143 |
|
884
|
144 <b>COMPLAIN:</b> |
|
804
|
145 |
|
884
|
146 If this README doesn't tell you what you need to know |
|
|
147 you can head over to www.d3v11.ano/peering. If that |
|
|
148 doesn't get you what you want then either complain to |
|
|
149 me or shoot both of us in the face. |
|
804
|
150 |
|
|
151 </pre></font></body></html> |
