From 3db38c992ac51ff7d9a5764fe4e8aa202212c019 Mon Sep 17 00:00:00 2001 From: Brian May Date: Tue, 15 Dec 2015 14:23:19 +1100 Subject: Replace numbered points with dot points. --- README.rst | 48 ++++++++++++++++++++++++------------------------ 1 file changed, 24 insertions(+), 24 deletions(-) (limited to 'README.rst') diff --git a/README.rst b/README.rst index bd64a10..5deb8ec 100644 --- a/README.rst +++ b/README.rst @@ -72,39 +72,39 @@ later. There are some things you need to consider for TPROXY to work: -1. The following commands need to be run first as root. This only needs to be - done once after booting up:: +- The following commands need to be run first as root. This only needs to be + done once after booting up:: - ip route add local default dev lo table 100 - ip rule add fwmark 1 lookup 100 - ip -6 route add local default dev lo table 100 - ip -6 rule add fwmark 1 lookup 100 + ip route add local default dev lo table 100 + ip rule add fwmark 1 lookup 100 + ip -6 route add local default dev lo table 100 + ip -6 rule add fwmark 1 lookup 100 -2. The client needs to be run as root. e.g.:: +- The client needs to be run as root. e.g.:: - sudo SSH_AUTH_SOCK="$SSH_AUTH_SOCK" $HOME/tree/sshuttle.tproxy/sshuttle --method=tproxy ... + sudo SSH_AUTH_SOCK="$SSH_AUTH_SOCK" $HOME/tree/sshuttle.tproxy/sshuttle --method=tproxy ... -3. You may need to exclude the IP address of the server you are connecting to. - Otherwise sshuttle may attempt to intercept the ssh packets, which will not - work. Use the `--exclude` parameter for this. +- You may need to exclude the IP address of the server you are connecting to. + Otherwise sshuttle may attempt to intercept the ssh packets, which will not + work. Use the `--exclude` parameter for this. -4. Similarly, UDP return packets (including DNS) could get intercepted and - bounced back. This is the case if you have a broad subnet such as - ``0.0.0.0/0`` that includes the IP address of the client. Use the - `--exclude` parameter for this. +- Similarly, UDP return packets (including DNS) could get intercepted and + bounced back. This is the case if you have a broad subnet such as + ``0.0.0.0/0`` that includes the IP address of the client. Use the + `--exclude` parameter for this. -5. You do need the `--method=tproxy` parameter, as above. +- You do need the `--method=tproxy` parameter, as above. -6. The routes for the outgoing packets must already exist. For example, if your - connection does not have IPv6 support, no IPv6 routes will exist, IPv6 - packets will not be generated and sshuttle cannot intercept them:: +- The routes for the outgoing packets must already exist. For example, if your + connection does not have IPv6 support, no IPv6 routes will exist, IPv6 + packets will not be generated and sshuttle cannot intercept them:: - telnet -6 www.google.com 80 - Trying 2404:6800:4001:805::1010... - telnet: Unable to connect to remote host: Network is unreachable + telnet -6 www.google.com 80 + Trying 2404:6800:4001:805::1010... + telnet: Unable to connect to remote host: Network is unreachable - Add some dummy routes to external interfaces. Make sure they get removed - however after sshuttle exits. + Add some dummy routes to external interfaces. Make sure they get removed + however after sshuttle exits. Obtaining sshuttle -- cgit v1.2.3 1.38 Mirror of https://github.com/netdata/netdatamatthias
summaryrefslogtreecommitdiffstats
path: root/backends/json/json.c
blob: 0c7cc738f8c6a7237c611a09cf26a26dee61c21a (plain) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152