circuit_st.h 6.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172
  1. /* Copyright (c) 2001 Matej Pfajfar.
  2. * Copyright (c) 2001-2004, Roger Dingledine.
  3. * Copyright (c) 2004-2006, Roger Dingledine, Nick Mathewson.
  4. * Copyright (c) 2007-2018, The Tor Project, Inc. */
  5. /* See LICENSE for licensing information */
  6. #ifndef CIRCUIT_ST_H
  7. #define CIRCUIT_ST_H
  8. #include "or/or.h"
  9. #include "or/cell_queue_st.h"
  10. /**
  11. * A circuit is a path over the onion routing
  12. * network. Applications can connect to one end of the circuit, and can
  13. * create exit connections at the other end of the circuit. AP and exit
  14. * connections have only one circuit associated with them (and thus these
  15. * connection types are closed when the circuit is closed), whereas
  16. * OR connections multiplex many circuits at once, and stay standing even
  17. * when there are no circuits running over them.
  18. *
  19. * A circuit_t structure can fill one of two roles. First, a or_circuit_t
  20. * links two connections together: either an edge connection and an OR
  21. * connection, or two OR connections. (When joined to an OR connection, a
  22. * circuit_t affects only cells sent to a particular circID on that
  23. * connection. When joined to an edge connection, a circuit_t affects all
  24. * data.)
  25. * Second, an origin_circuit_t holds the cipher keys and state for sending data
  26. * along a given circuit. At the OP, it has a sequence of ciphers, each
  27. * of which is shared with a single OR along the circuit. Separate
  28. * ciphers are used for data going "forward" (away from the OP) and
  29. * "backward" (towards the OP). At the OR, a circuit has only two stream
  30. * ciphers: one for data going forward, and one for data going backward.
  31. */
  32. struct circuit_t {
  33. uint32_t magic; /**< For memory and type debugging: must equal
  34. * ORIGIN_CIRCUIT_MAGIC or OR_CIRCUIT_MAGIC. */
  35. /** The channel that is next in this circuit. */
  36. channel_t *n_chan;
  37. /**
  38. * The circuit_id used in the next (forward) hop of this circuit;
  39. * this is unique to n_chan, but this ordered pair is globally
  40. * unique:
  41. *
  42. * (n_chan->global_identifier, n_circ_id)
  43. */
  44. circid_t n_circ_id;
  45. /**
  46. * Circuit mux associated with n_chan to which this circuit is attached;
  47. * NULL if we have no n_chan.
  48. */
  49. circuitmux_t *n_mux;
  50. /** Queue of cells waiting to be transmitted on n_chan */
  51. cell_queue_t n_chan_cells;
  52. /**
  53. * The hop to which we want to extend this circuit. Should be NULL if
  54. * the circuit has attached to a channel.
  55. */
  56. extend_info_t *n_hop;
  57. /** True iff we are waiting for n_chan_cells to become less full before
  58. * allowing p_streams to add any more cells. (Origin circuit only.) */
  59. unsigned int streams_blocked_on_n_chan : 1;
  60. /** True iff we are waiting for p_chan_cells to become less full before
  61. * allowing n_streams to add any more cells. (OR circuit only.) */
  62. unsigned int streams_blocked_on_p_chan : 1;
  63. /** True iff we have queued a delete backwards on this circuit, but not put
  64. * it on the output buffer. */
  65. unsigned int p_delete_pending : 1;
  66. /** True iff we have queued a delete forwards on this circuit, but not put
  67. * it on the output buffer. */
  68. unsigned int n_delete_pending : 1;
  69. /** True iff this circuit has received a DESTROY cell in either direction */
  70. unsigned int received_destroy : 1;
  71. uint8_t state; /**< Current status of this circuit. */
  72. uint8_t purpose; /**< Why are we creating this circuit? */
  73. /** How many relay data cells can we package (read from edge streams)
  74. * on this circuit before we receive a circuit-level sendme cell asking
  75. * for more? */
  76. int package_window;
  77. /** How many relay data cells will we deliver (write to edge streams)
  78. * on this circuit? When deliver_window gets low, we send some
  79. * circuit-level sendme cells to indicate that we're willing to accept
  80. * more. */
  81. int deliver_window;
  82. /** Temporary field used during circuits_handle_oom. */
  83. uint32_t age_tmp;
  84. /** For storage while n_chan is pending (state CIRCUIT_STATE_CHAN_WAIT). */
  85. struct create_cell_t *n_chan_create_cell;
  86. /** When did circuit construction actually begin (ie send the
  87. * CREATE cell or begin cannibalization).
  88. *
  89. * Note: This timer will get reset if we decide to cannibalize
  90. * a circuit. It may also get reset during certain phases of hidden
  91. * service circuit use.
  92. *
  93. * We keep this timestamp with a higher resolution than most so that the
  94. * circuit-build-time tracking code can get millisecond resolution.
  95. */
  96. struct timeval timestamp_began;
  97. /** This timestamp marks when the init_circuit_base constructor ran. */
  98. struct timeval timestamp_created;
  99. /** When the circuit was first used, or 0 if the circuit is clean.
  100. *
  101. * XXXX Note that some code will artificially adjust this value backward
  102. * in time in order to indicate that a circuit shouldn't be used for new
  103. * streams, but that it can stay alive as long as it has streams on it.
  104. * That's a kludge we should fix.
  105. *
  106. * XXX The CBT code uses this field to record when HS-related
  107. * circuits entered certain states. This usage probably won't
  108. * interfere with this field's primary purpose, but we should
  109. * document it more thoroughly to make sure of that.
  110. *
  111. * XXX The SocksPort option KeepaliveIsolateSOCKSAuth will artificially
  112. * adjust this value forward each time a suitable stream is attached to an
  113. * already constructed circuit, potentially keeping the circuit alive
  114. * indefinitely.
  115. */
  116. time_t timestamp_dirty;
  117. uint16_t marked_for_close; /**< Should we close this circuit at the end of
  118. * the main loop? (If true, holds the line number
  119. * where this circuit was marked.) */
  120. const char *marked_for_close_file; /**< For debugging: in which file was this
  121. * circuit marked for close? */
  122. /** For what reason (See END_CIRC_REASON...) is this circuit being closed?
  123. * This field is set in circuit_mark_for_close and used later in
  124. * circuit_about_to_free. */
  125. int marked_for_close_reason;
  126. /** As marked_for_close_reason, but reflects the underlying reason for
  127. * closing this circuit.
  128. */
  129. int marked_for_close_orig_reason;
  130. /** Unique ID for measuring tunneled network status requests. */
  131. uint64_t dirreq_id;
  132. /** Index in smartlist of all circuits (global_circuitlist). */
  133. int global_circuitlist_idx;
  134. /** Various statistics about cells being added to or removed from this
  135. * circuit's queues; used only if CELL_STATS events are enabled and
  136. * cleared after being sent to control port. */
  137. smartlist_t *testing_cell_stats;
  138. /** If set, points to an HS token that this circuit might be carrying.
  139. * Used by the HS circuitmap. */
  140. hs_token_t *hs_token;
  141. /** Hashtable node: used to look up the circuit by its HS token using the HS
  142. circuitmap. */
  143. HT_ENTRY(circuit_t) hs_circuitmap_node;
  144. };
  145. #endif