Home
last modified time | relevance | path

Searched refs:TTL (Results 1 – 25 of 30) sorted by relevance

12

/NextBSD/contrib/netbsd-tests/ipf/input/
HDf132 # 1.1.1.1,1025 -> 2.1.1.1,25 TTL=63 TCP DF,FO=0 SYN
7 # 1.1.1.1,1025 -> 2.1.1.1,25 TTL=63 TCP MF ACK
12 # 1.1.1.1,1025 -> 2.1.1.1,25 TTL=63 TCP FO=2 ACK
17 # 1.1.1.1,1024 -> 2.1.1.1,25 TTL=63 TCP DF MF FO=0 SYN
22 # 1.1.1.1,1025 -> 2.1.1.1,25 TTL=63 TCP DF FO=0
27 # 1.1.1.1 -> 2.1.1.1 TTL=63 TCP DF FO=1 SYN
32 # 1.1.1.1 -> 2.1.1.1 TTL=63 UDP DF MF FO=0
36 # 1.1.1.1,53 -> 2.1.1.1,53 TTL=63 UDP MF FO=0
41 # 1.1.1.1,53 -> 2.1.1.1,53 TTL=63 UDP MF FO=0
46 # 1.1.1.1,53 -> 2.1.1.1,54 TTL=63 UDP MF FO=0 (short)
[all …]
HDf121 # 1.1.1.1,1025 -> 2.1.1.1,25 TTL=63 TCP DF SYN
6 # 1.1.1.1,1025 -> 2.1.1.1,25 TTL=63 TCP DF ACK
11 # 1.1.1.1,1025 -> 2.1.1.1,25 TTL=63 TCP DF MF FO=0 ACK
16 # 1.1.1.1,1025 -> 2.1.1.1,25 TTL=63 TCP DF FO=0
21 # 1.1.1.1 -> 2.1.1.1 TTL=63 TCP DF FO=1 ACK
26 # 1.1.1.1 -> 2.1.1.1 TTL=63 UDP DF MF FO=0
30 # 1.1.1.1,53 -> 2.1.1.1,53 TTL=63 UDP MF FO=0
35 # 1.1.1.1,1 -> 2.1.1.1,1 TTL=63 UDP MF FO=0
40 # 1.1.1.1,53 -> 2.1.1.1,53 TTL=63 UDP MF FO=0
HDl11 # 1.1.1.1,1025 -> 2.2.2.2,25 TTL=63 TCP DF SYN
/NextBSD/tools/tools/tinybsd/conf/wireless/etc/
HDpf.os56 # - Initial TTL - We check the actual TTL of a received packet. It can't
57 # be higher than the initial TTL, and also shouldn't be dramatically
60 # NEW SIGNATURE: *Never* copy TTL from a p0f-reported signature literally.
61 # You need to determine the initial TTL. The best way to do it is to
63 # A fairly good method is to simply round the observed TTL up to
66 # "original" initial TTL settings). If not sure, you can see how many
105 # To wildcard any value (except for initial TTL or TCP options), replace
116 # ttt - initial TTL
338 8192:32:1:44:M*: Windows:95::Windows 95 (low TTL)
341 S44:32:1:48:M*,N,N,S: Windows:98::Windows 98 (low TTL)
[all …]
/NextBSD/tools/tools/tinybsd/conf/firewall/etc/
HDpf.os56 # - Initial TTL - We check the actual TTL of a received packet. It can't
57 # be higher than the initial TTL, and also shouldn't be dramatically
60 # NEW SIGNATURE: *Never* copy TTL from a p0f-reported signature literally.
61 # You need to determine the initial TTL. The best way to do it is to
63 # A fairly good method is to simply round the observed TTL up to
66 # "original" initial TTL settings). If not sure, you can see how many
105 # To wildcard any value (except for initial TTL or TCP options), replace
116 # ttt - initial TTL
338 8192:32:1:44:M*: Windows:95::Windows 95 (low TTL)
341 S44:32:1:48:M*,N,N,S: Windows:98::Windows 98 (low TTL)
[all …]
/NextBSD/contrib/unbound/doc/
HDTODO2 o understand synthesized DNAMEs, so those TTL=0 packets are cached properly.
8 o (option) private TTL feature (always report TTL x in answers).
HDrequirements.txt20 time to live (TTL). During this time the data can be cached. It is
108 The message has a TTL smaller or equal to the TTL of the answer RR.
110 RR may be inserted, within the message TTL time, and thus return the
251 Unbound keeps TTL values for message formats, and thus rcodes, such
253 So it will faithfully negative cache for the exact TTL as originally
258 These situations become consistent once the original TTL expires.
HDFEATURES34 RFC 2308: TTL directive, and the rest of the RFC too.
HDexample.conf.in134 # the time to live (TTL) value lower bound, in seconds. Default 0.
138 # the time to live (TTL) value cap for RRsets and messages in the
142 # the time to live (TTL) value cap for negative responses in the cache
145 # the time to live (TTL) value for cached roundtrip times, lameness and
384 # single line, surrounded by "". TTL is ignored. class is IN default.
HDChangelog229 - SOA negative TTL is capped at minimumttl in its rdata section.
572 - $TTL's value starts at position 5 (ldns).
1500 parent again. If child NS has longer TTL, that TTL does not get
1547 because of a bug in the TTL-fix in 1.4.15, it picked the wrong rdata
1548 for an NSEC3. Now it does not change rdata, and fixes TTL.
1584 - Fix bug #425: unbound reports wrong TTL in reply, it reports a TTL
1585 that would be permissible by the RFCs but it is not the TTL in the
1883 - Fix TTL of SOA so negative TTL is separately cached from normal TTL.
1895 and curb the TTL if it is bad, thus protecting the cache for use by
1945 cache effects with different TTL for glue and DNSKEY.
[all …]
/NextBSD/etc/
HDpf.os58 # - Initial TTL - We check the actual TTL of a received packet. It can't
59 # be higher than the initial TTL, and also shouldn't be dramatically
62 # NEW SIGNATURE: *Never* copy TTL from a p0f-reported signature literally.
63 # You need to determine the initial TTL. The best way to do it is to
65 # A fairly good method is to simply round the observed TTL up to
68 # "original" initial TTL settings). If not sure, you can see how many
107 # To wildcard any value (except for initial TTL or TCP options), replace
118 # ttt - initial TTL
397 S44:32:1:48:M*,N,N,S: Windows:98:lowTTL:Windows 98 (low TTL)
398 8192:32:1:48:M*,N,N,S: Windows:98:lowTTL:Windows 98 (low TTL)
/NextBSD/sys/gnu/dts/arm/
HDkirkwood-b3.dts110 /* Internal on test pins, 3.3v TTL
/NextBSD/sys/sparc64/conf/
HDNOTES79 # Sun type 4/5/6 RS-232@TTL keyboard
/NextBSD/contrib/amd/
HDtasks47 - detecting down'ed hosts faster: use default portmap TTL variables?
/NextBSD/sys/boot/efi/include/
HDefipxebc.h249 UINT8 TTL; member
/NextBSD/contrib/ntp/ntpd/
HDntp.conf.def1694 and minimum feasible time-to-live (TTL) hops, depending
1708 in scope of the current TTL and is itself synchronized
1754 Initially, the TTL is
1756 At each retransmission the TTL is increased until reaching
1759 Further retransmissions use the same TTL.
1795 servers are found when the TTL has reached the maximum hops,
1802 TTL values.
1810 By default, the increment for TTL hops is 32 starting
1821 in TTL range, which is probably the most common objective.
1823 in TTL range will eventually find all primary servers
[all …]
HDinvoke-ntp.conf.texi1626 and minimum feasible time-to-live (TTL) hops, depending
1640 in scope of the current TTL and is itself synchronized
1686 Initially, the TTL is
1688 At each retransmission the TTL is increased until reaching
1691 Further retransmissions use the same TTL.
1727 servers are found when the TTL has reached the maximum hops,
1734 TTL values.
1742 By default, the increment for TTL hops is 32 starting
1753 in TTL range, which is probably the most common objective.
1755 in TTL range will eventually find all primary servers
[all …]
/NextBSD/contrib/ldns/
HDChangelog242 * Fix ldns zone, so that $TTL definition match RFC 2308.
435 * ldns-signzone now equalizes the TTL of the DNSKEY RRset (to
436 the first non-default DNSKEY TTL value it sees)
/NextBSD/share/examples/ipfilter/
HDexamples.txt458 by not causing any decrement in the TTL to occur as it passes through the
HDipf-howto.txt1574 router should by decrementing the TTL on the packet and
1578 various TTL values to map the hops between two sites. If we
1599 which results in a TTL decrement. The packet will be placed
2072 TCP connection. This TTL counter is decremented every sec-
2075 idle. The TTL is also reset to 864000 whenever the state
/NextBSD/sbin/pfctl/
HDparse.y448 %token NOROUTE URPFFAILED FRAGMENT USER GROUP MAXMSS MAXIMUM TTL TOS DROP TABLE
2569 | RETURNRST '(' TTL NUMBER ')' {
5466 { "ttl", TTL}, in lookup()
/NextBSD/tools/tools/sysdoc/
HDtunables.mdoc1341 The TTL (time-to-live) to use for outgoing packets.
/NextBSD/contrib/llvm/tools/clang/lib/Sema/
HDTreeTransform.h3244 TypedefTypeLoc TTL = TL.getAs<TypedefTypeLoc>(); in TransformNestedNameSpecifierLoc() local
3245 if (!TTL || !TTL.getTypedefNameDecl()->isInvalidDecl()) { in TransformNestedNameSpecifierLoc()
HDSemaChecking.cpp8308 if (TypedefTypeLoc TTL = TL.getAs<TypedefTypeLoc>()) { in IsTailPaddedMemberArray() local
8309 const TypedefNameDecl *TDL = TTL.getTypedefNameDecl(); in IsTailPaddedMemberArray()
/NextBSD/usr.sbin/bsnmpd/modules/snmp_wlan/
HDBEGEMOT-WIRELESS-MIB.txt3620 because of a zero TTL."

12