![]() ![]() enter yournetwork into /usr/local/etc/tinc/nets.boot to let this network be started on bootĢ.copy the /usr/local/etc/tinc/example folder to /usr/local/etc/tinc/yournetwork.Remember to still set up your tinc-up script. ![]() This node will then automatically generate configuration, private/public keys and will exchange this key with the other node on connection. On the other node you can join by using: $ tinc join nIRp5pJCnfnhuV13JUomscGs1q5HqEbz3AydZer7wRaMcpUB Tinc will print the invitaion which you need to copy to your peering partner. # tinc -n dn42_yourpeer init dn42_yourself Debian: follow these instructions to get a package.It also introduces the tinc binary in addition to tincd, which allows tinc to be configured via an readline interface. To keep backwards compatibility with the tinc 1.0 release you need rsa keys, if you don't need that only generate ed25519 keys. Instead of rsa keys it uses ed25519 keys. The current development version (which is pretty stable by the way), allow to bootstrap networks using invitation urls. MIIBCgKCAQEAoGeD5b1HKW2UAFpIPayxsOOYx5qC0oHrJnvcPH33jnDBGiOYJ9ma QZErWdF0Qsnqh/ wJE6i569fzKWOUdLHrN5dVzD/ Q5zjMOwJf3rmcerS0oAFTxKDj pkw2kKcLA/ lSNMIN// W66mM258BLo1XgEraUx5RcJ4hTxawhNTn0NTJVCbfUX6e5 tcJpbgbYRzBTUPdS元OB8k0qlmFI2ZYTnCzOSpgxRQARIB1ecoqOYVxQISK2pzxi MHQQlVbquwldaKiVoj7tD7PFW4oQxpiMHZnHIA6dnZCsT3ktTOzCjhf2XMi8o8u5 P9C5dYrmVWrVAWQznlbuq/ w1z+ PrTYquoQIDAQAB Import for each other party the key like this /etc/tinc/dn42_yourpeer/hosts/: # address/port are optional, in case they're missing you only expect connections from that host To generate a public/private key pair use: $ tincd -K Ip route add 172.16.0.1/30 dev $INTERFACE table peersįor authentication tinc uses public key authentication instead of certificates or pre-shared keys.įor each key tinc should connect to or allow to connect, a file with the name of the peer in tincd -n twwh -K Ip addr add fe80::1/64 dev $INTERFACE # add routes Ip addr add 172.16.0.1/30 dev $INTERFACE scope link Linux/iproute2 #!/bin/sh # set the interface up On startup it will execute /etc/tinc/dn42_yourpeer/tinc-up if it exists and is executable: Tinc requires to add manually ip addresses and routes to the tap/tun interfaces. ConnectTo can be specified multiple times.ĬonnectTo = remote_host # In newer versions (>= 1.1) you can use AutoConnect instead Mode = switch # To discover other hosts, it is required to initially specify a number of hosts to connect to. ConfigurationĮxample /etc/tinc/dn42_yourpeer/nf: Interface = dn42_yourpeer Name = your_host # Only switch mode is feasible for dn42 peerings, since in router mode tinc takes care of routing decisions on its own One advantage of tinc is that you can have multiple peering over the same VPN configuration by opening multiple connections. In Switch mode tinc will act like a L2 network, in which the routing table reflects the peers mac addresses. This is the default mode, but it is unsuitable for dn42, because you cannot influence how tinc will route to a certain network. Tinc will spawn an interface on which it will act as a 元 network, routing according to announcements. In Router mode each peer announces the addresses/subnets it serves. A third mode, the hub mode, exists, but it's just a dumb router mode that keeps no routing table and broadcasts everything - don't use it. Tinc primarily operates in two modes: router and switch. Tinc is most notably powering the Freifunk communitys ICVPN (in L2/Switch-Mode) and ChaosVPN (in 元/Router-Mode). If that is not possible traffic may be routed via a shared neighbor. If nodes want to reach each other, they establish a direct connection. Tinc will use a bunch of nodes to build the network graph, which in return all nodes use to learn addresses from each other. It allows multiple parties to connect and discover each other independently, while minimizing points of failure. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |