/external/autotest/client/tests/ipv6connect/ |
control | 9 to the IPv4, IPv6-mapped-IPv4 and IPv6 loopback address (different code paths).
|
/prebuilts/go/darwin-x86/src/net/ |
ipsock_test.go | 26 {IP: IPv4(127, 0, 0, 1)}, 30 &TCPAddr{IP: IPv4(127, 0, 0, 1), Port: 5682}, 31 addrList{&TCPAddr{IP: IPv4(127, 0, 0, 1), Port: 5682}}, 39 {IP: IPv4(127, 0, 0, 1)}, 42 &TCPAddr{IP: IPv4(127, 0, 0, 1), Port: 5682}, 44 addrList{&TCPAddr{IP: IPv4(127, 0, 0, 1), Port: 5682}}, 50 {IP: IPv4(127, 0, 0, 1)}, 51 {IP: IPv4(192, 168, 0, 1)}, 54 &TCPAddr{IP: IPv4(127, 0, 0, 1), Port: 5682}, 56 &TCPAddr{IP: IPv4(127, 0, 0, 1), Port: 5682} [all...] |
cgo_linux.go | 16 // in the flags (it includes IPv4 results only on IPv4 systems,
|
ipsock_posix.go | 18 // "tcp" and "udp" networks does not listen for both IPv4 and IPv6 19 // connections. This is due to the fact that IPv4 traffic will not be 35 // Should we try to use the IPv4 socket interface if we're 36 // only dealing with IPv4 sockets? As long as the host system 37 // understands IPv6, it's okay to pass IPv4 addresses to the IPv6 42 // probeIPv6Stack probes both basic IPv6 capability and IPv6 IPv4- 47 // boolean value is true, kernel supports IPv6 IPv4-mapping. 55 // IPv6 IPv4-mapped address communication capability 56 {laddr: TCPAddr{IP: IPv4(127, 0, 0, 1)}, value: 0}, 103 // If the platform supports both IPv6 and IPv6 IPv4-mappin [all...] |
/prebuilts/go/linux-x86/src/net/ |
ipsock_test.go | 26 {IP: IPv4(127, 0, 0, 1)}, 30 &TCPAddr{IP: IPv4(127, 0, 0, 1), Port: 5682}, 31 addrList{&TCPAddr{IP: IPv4(127, 0, 0, 1), Port: 5682}}, 39 {IP: IPv4(127, 0, 0, 1)}, 42 &TCPAddr{IP: IPv4(127, 0, 0, 1), Port: 5682}, 44 addrList{&TCPAddr{IP: IPv4(127, 0, 0, 1), Port: 5682}}, 50 {IP: IPv4(127, 0, 0, 1)}, 51 {IP: IPv4(192, 168, 0, 1)}, 54 &TCPAddr{IP: IPv4(127, 0, 0, 1), Port: 5682}, 56 &TCPAddr{IP: IPv4(127, 0, 0, 1), Port: 5682} [all...] |
cgo_linux.go | 16 // in the flags (it includes IPv4 results only on IPv4 systems,
|
ipsock_posix.go | 18 // "tcp" and "udp" networks does not listen for both IPv4 and IPv6 19 // connections. This is due to the fact that IPv4 traffic will not be 35 // Should we try to use the IPv4 socket interface if we're 36 // only dealing with IPv4 sockets? As long as the host system 37 // understands IPv6, it's okay to pass IPv4 addresses to the IPv6 42 // probeIPv6Stack probes both basic IPv6 capability and IPv6 IPv4- 47 // boolean value is true, kernel supports IPv6 IPv4-mapping. 55 // IPv6 IPv4-mapped address communication capability 56 {laddr: TCPAddr{IP: IPv4(127, 0, 0, 1)}, value: 0}, 103 // If the platform supports both IPv6 and IPv6 IPv4-mappin [all...] |
/external/iproute2/ip/ |
routef | 8 echo "This script will flush the IPv4 routing table"
|
/external/tcpdump/tests/ |
nflog-e.out | 1 version 0, resource ID 20, family IPv4 (2), length 180: 74.82.42.42.53 > 10.0.0.20.42585: 17265 1/0/0 A 93.184.216.119 (45) 2 version 0, resource ID 20, family IPv4 (2), length 192: 74.82.42.42.53 > 10.0.0.20.45190: 52954 1/0/0 AAAA 2606:2800:220:6d:26bf:1447:1097:aa7 (57) 3 version 0, resource ID 20, family IPv4 (2), length 184: 74.82.42.42.53 > 10.0.0.20.44031: 8279 1/0/0 A 93.184.216.119 (49) 4 version 0, resource ID 20, family IPv4 (2), length 196: 74.82.42.42.53 > 10.0.0.20.48736: 2122 1/0/0 AAAA 2606:2800:220:6d:26bf:1447:1097:aa7 (61)
|
sflow_multiple_counter_30_pdus-nv.out | 1 IP 15.184.1.76.40948 > 15.184.3.9.6343: sFlowv5, IPv4 agent 15.184.8.4, agent-id 2, length 1288 2 IP 15.184.1.195.4942 > 15.184.3.9.6343: sFlowv5, IPv4 agent 15.184.1.195, agent-id 1, length 1288 3 IP 15.184.1.195.4942 > 15.184.3.9.6343: sFlowv5, IPv4 agent 15.184.1.195, agent-id 1, length 1288 4 IP 15.184.1.195.4942 > 15.184.3.9.6343: sFlowv5, IPv4 agent 15.184.1.195, agent-id 1, length 1288 5 IP 15.184.1.195.4942 > 15.184.3.9.6343: sFlowv5, IPv4 agent 15.184.1.195, agent-id 1, length 1288 6 IP 15.184.1.195.4942 > 15.184.3.9.6343: sFlowv5, IPv4 agent 15.184.1.195, agent-id 1, length 1108 7 IP 15.184.1.76.40948 > 15.184.3.9.6343: sFlowv5, IPv4 agent 15.184.8.4, agent-id 2, length 208 8 IP 15.184.1.194.3099 > 15.184.3.9.6343: sFlowv5, IPv4 agent 15.184.1.194, agent-id 1, length 1288 9 IP 15.184.1.194.3099 > 15.184.3.9.6343: sFlowv5, IPv4 agent 15.184.1.194, agent-id 1, length 1288 10 IP 15.184.1.194.3099 > 15.184.3.9.6343: sFlowv5, IPv4 agent 15.184.1.194, agent-id 1, length 128 [all...] |
isis_1-v.out | 15 NLPID(s): IPv4 (0xcc) 18 IPv4 Interface address(es) TLV #132, length: 4 19 IPv4 interface address: 10.0.10.1 35 NLPID(s): IPv4 (0xcc) 38 IPv4 Interface address(es) TLV #132, length: 4 39 IPv4 interface address: 10.0.10.1 55 NLPID(s): IPv4 (0xcc) 58 IPv4 Interface address(es) TLV #132, length: 4 59 IPv4 interface address: 10.0.10.2 75 NLPID(s): IPv4 (0xcc [all...] |
isis_3-v.out | 6 NLPID(s): IPv4 (0xcc) 9 IPv4 Interface address(es) TLV #132, length: 4 10 IPv4 interface address: 10.0.0.2 24 NLPID(s): IPv4 (0xcc) 27 IPv4 Interface address(es) TLV #132, length: 4 28 IPv4 interface address: 10.0.0.2 42 NLPID(s): IPv4 (0xcc) 45 IPv4 Interface address(es) TLV #132, length: 4 46 IPv4 interface address: 10.0.0.2 60 NLPID(s): IPv4 (0xcc [all...] |
isis_2-v.out | 6 NLPID(s): IPv4 (0xcc) 9 IPv4 Interface address(es) TLV #132, length: 4 10 IPv4 interface address: 10.0.10.2 24 NLPID(s): IPv4 (0xcc) 27 IPv4 Interface address(es) TLV #132, length: 4 28 IPv4 interface address: 10.0.10.2 42 NLPID(s): IPv4 (0xcc) 45 IPv4 Interface address(es) TLV #132, length: 4 46 IPv4 interface address: 10.0.10.2 60 NLPID(s): IPv4 (0xcc [all...] |
isis_4-v.out | 10 NLPID(s): IPv4 (0xcc) 13 IPv4 Interface address(es) TLV #132, length: 4 14 IPv4 interface address: 10.0.0.1 30 NLPID(s): IPv4 (0xcc) 33 IPv4 Interface address(es) TLV #132, length: 4 34 IPv4 interface address: 10.0.0.1 50 NLPID(s): IPv4 (0xcc) 53 IPv4 Interface address(es) TLV #132, length: 4 54 IPv4 interface address: 10.0.0.2 70 NLPID(s): IPv4 (0xcc [all...] |
/prebuilts/go/darwin-x86/src/net/testdata/ |
ipv4-hosts | 3 # The literal IPv4 address parser in the net package is a relaxed 4 # one. It may accept a literal IPv4 address in dotted-decimal notation
|
/prebuilts/go/linux-x86/src/net/testdata/ |
ipv4-hosts | 3 # The literal IPv4 address parser in the net package is a relaxed 4 # one. It may accept a literal IPv4 address in dotted-decimal notation
|
/libcore/harmony-tests/src/test/java/org/apache/harmony/tests/java/net/ |
Inet4AddressTest.java | 92 // There are no link local addresses for IPv4 97 assertTrue("IPv4 address " + addrName 107 // There are no site local addresses for IPv4 112 assertTrue("IPv4 address " + addrName 122 // Create an IPv4 mulitcast address. It should return 123 // false for globabl mutlicast. There are no valid IPv4 129 assertTrue("IPv4 link-local multicast address " + addrName 135 assertTrue("IPv4 link-local multicast address " + addrName 141 assertTrue("IPv4 global multicast address " + addrName 147 assertTrue("IPv4 global multicast address " + addrNam [all...] |
/external/iproute2/testsuite/tests/ip/tunnel/ |
add_tunnel.t | 9 ts_ip "$0" "Add GRE tunnel over IPv4" tunnel add name $TUNNEL_NAME mode gre local 1.1.1.1 remote 2.2.2.2 10 ts_ip "$0" "Del GRE tunnel over IPv4" tunnel del $TUNNEL_NAME
|
/external/iptables/libiptc/ |
libip4tc.pc.in | 7 Description: iptables IPv4 ruleset ADT and kernel interface
|
/external/libnl/include/linux/ |
ip_mp_alg.h | 1 /* ip_mp_alg.h: IPV4 multipath algorithm support, user-visible values.
|
/external/chromium-trace/catapult/telemetry/third_party/webpagereplay/third_party/dns/rdtypes/IN/ |
A.py | 17 import dns.ipv4 24 @ivar address: an IPv4 address 32 junk = dns.ipv4.inet_aton(address) 46 file.write(dns.ipv4.inet_aton(self.address)) 49 address = dns.ipv4.inet_ntoa(wire[current : current + rdlen]) 55 sa = dns.ipv4.inet_aton(self.address) 56 oa = dns.ipv4.inet_aton(other.address)
|
/system/connectivity/shill/doc/ |
ipconfig-api.txt | 42 for IPv4 and any allowed format for IPv6 (as specified 63 "ipv4" (fixed IPv4 network state) 65 "dhcp" (IPv4 state setup using DHCP) 66 "bootp" (IPv4 state setup using BOOTP) 67 "zeroconf" (IPV4 state setup using ZeroConf) 69 "ppp" (IPv4 state setup using PPP) 70 "vpn" (IPv4 state setup using VPN) 90 part of the network address. For IPv4 networks this
|
/external/chromium-libpac/src/ |
net_util.h | 29 // IPv4 addresses will have length 4, whereas IPv6 address will have length 16. 33 // Parses an IP address literal (either IPv4 or IPv6) to its numeric value. 43 // CIDR notation literals can use either IPv4 or IPv6 literals. Some examples: 59 // In cases when an IPv4 address is being compared to an IPv6 address prefix 60 // and vice versa, the IPv4 addresses will be converted to IPv4-mapped
|
/external/avahi/avahi-sharp/en/Avahi/ |
Protocol.xml | 11 <Member MemberName="IPv4"> 12 <MemberSignature Language="C#" Value="IPv4" />
|
/external/chromium-trace/catapult/telemetry/third_party/webpagereplay/third_party/dns/ |
reversename.py | 18 @var ipv4_reverse_domain: The DNS IPv4 reverse-map domain, in-addr.arpa. 26 import dns.ipv4 32 """Convert an IPv4 or IPv6 address in textual form into a Name object whose 34 @param text: an IPv4 or IPv6 address in textual form (e.g. '127.0.0.1', 43 parts = ['%d' % ord(byte) for byte in dns.ipv4.inet_aton(text)] 50 @param name: an IPv4 or IPv6 address in reverse-map form. 60 return dns.ipv4.inet_ntoa(dns.ipv4.inet_aton(text))
|