About 31 results found. (Query 0.03100 seconds)
No information is available for this page.
No information is available for this page.
We don't conduct statistics on your messages, we don't demand personal information on you Our server is changed by TTL values (Time To Live). TTL - lifetime of an information block. Usually each router through which there passed the packet reduces TTL by unit.
Example output of ping tool to magma.lavafeld.org : PING magma.lavafeld.org (37.218.242.177) 56(84) bytes of data. 64 bytes from 37.218.242.177: icmp_seq=1 ttl=54 time=22.7 ms 64 bytes from 37.218.242.177: icmp_seq=2 ttl=54 time=23.5 ms 64 bytes from 37.218.242.177: icmp_seq=3 ttl=54 time=22.9 ms --- magma.lavafeld.org ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 22.798/23.085/23.548/0.330 ms #...
It then repeats the exercise with TTL set to 2, which will fail after two hops. traceroute increases the TTL to three and tries again. This process repeats until the destination is reached or the maximum number of hops (30, by default) is tested.
D'abord, l' espace de noms urn:ietf:params:xml:ns:epp:ttl-1.0 (enregistré à l'IANA ), qui identifie cette extension (le RFC utilise l'alias ttl mais rappelez-vous qu'en XML , c'est l'espace de noms qui compte, l'alias est choisi par l'auteur du document XML). Ensuite, l'élément <ttl:ttl> (donc, en complet, {urn:ietf:params:xml:ns:epp:ttl-1.0}ttl ), qui peut être ajouté aux demandes EPP ou aux réponses.
Adding a windows host: root@Monitoring:~# ping 10.0.0.203 PING 10.0.0.203 (10.0.0.203) 56(84) bytes of data. 64 bytes from 10.0.0.203: icmp_seq=1 ttl=128 time=8.28 ms 64 bytes from 10.0.0.203: icmp_seq=2 ttl=128 time=0.718 ms 64 bytes from 10.0.0.203: icmp_seq=3 ttl=128 time=0.878 ms 64 bytes from 10.0.0.203: icmp_seq=4 ttl=128 time=11.3 ms 64 bytes from 10.0.0.203: icmp_seq=5 ttl=128 time=0.953 ms 64 bytes from...
The interval value specifies the minimum time between checks. If the A record has a TTL greater than this value, then service discovery honors said TTL. For example, if the TTL of the A record is 90 seconds, then service discovery waits at least 90 seconds before checking the A record again.
А выданный в логе пингуется, но толку то. 2025-07-10T14:41:20.581928Z INFO mycelium::router: Acquired route subnet=56e:5c68:436b:d2a9::/64 peer="QUIC -> 142.93.217.194:9651" # ping6 56e:5c68:436b:d2a9::1 PING 56e:5c68:436b:d2a9::1 (56e:5c68:436b:d2a9::1) 56 data bytes 64 bytes from 56e:5c68:436b:d2a9::1: icmp_seq=1 ttl=60 time=428 ms 64 bytes from 56e:5c68:436b:d2a9::1: icmp_seq=2 ttl=60 time=326...
. / Due to the TLL gates fall, you can get some troubles when calling via routes tll1-st / tll2-st /tll1-ua / tll1-kz Это сообщение исчезнет, как только шлюзы TTL возобновят работу. / This message will be annihilated when the TLL gates will became works. Спасибо, что Вы с нами, %username%. Sincerelly yours, hana, Narayana Team. by hana, 2018-12-27 06:36:03.612536
これは出口ノードからの攻撃を防ぐのと同時に、curlなど意図的にonionドメインを拒否する一部のアプリケーション以外からもonionドメインへのアクセスを可能にします。 またキャッシュ機能とTTLを調整する機能を備えておりサーバー側の設定に依存しないTTLで正引きする事が可能です。 多くのTor透過プロキシが存在しますが、このような仕組みはIROHA以外に存在しないと思われます。 アプリケーション毎の経路切り替え IROHAはアプリケーション毎にTorを使うかVPNだけを使うか生IPで接続するかを選択できます。
The SOA record looks like this: ;; ANSWER SECTION: google.com. 86400 IN SOA ns1.google.com. dns-admin.google.com. 1399740 7200 1800 1209600 300 You have the domain name, TTL, protocol, record type. Then “mname” which should be the name of the PRIMARY domain name server, followed by “rname” which is the zone admin email (using a . instead of an @) and then serial #, refresh, retry, expire, and a default Time-To-Live for records.
Once the NS dns record propagated, your domain should resolve anywhere in the world: [ mainpc ] [ /dev/pts/10 ] [~/Nextcloud/blog-contributions] → ping ns1.nihilism.network PING ns1.nihilism.network (23.137.250.140) 56(84) bytes of data. 64 bytes from mail.nihilism.network (23.137.250.140): icmp_seq=1 ttl=56 time=58.9 ms 64 bytes from mail.nihilism.network (23.137.250.140): icmp_seq=2 ttl=56 time=55.8 ms 64 bytes from mail.nihilism.network (23.137.250.140): icmp_seq=3...
Compliance Holo supports the following Internet Standards: BFD RFC 5880 - Bidirectional Forwarding Detection (BFD) RFC 5881 - Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop) RFC 5882 - Generic Application of Bidirectional Forwarding Detection (BFD) RFC 5883 - Bidirectional Forwarding Detection (BFD) for Multihop Paths BGP RFC 1997 - BGP Communities Attribute RFC 2385 - Protection of BGP Sessions via the TCP MD5 Signature Option RFC 2545 - Use of BGP-4 Multiprotocol Extensions for...
Here's a packet capture I did from pfSense while running the TCP test, I set it level of detail to "Full": 20:00:06.108044 AF IPv4 (2), length 80: (tos 0x0, ttl 54, id 10076, offset 0, flags [DF], proto UDP (17), length 76) 188.166.175.60.59010 > XX.XX.XXX.XX.40756: [udp sum ok] UDP, length 48 20:00:11.284073 AF IPv4 (2), length 64: (tos 0x0, ttl 54, id 5974, offset 0, flags [DF], proto TCP (6), length 60) 188.166.175.60.53688 > XX.XX.XXX.XX.40756:...
Now if there are other websites that didn't get blocked by mullvad, you can mention them from the hosts file in your computer: [ mainpc ] [ /dev/pts/3 ] [blog/productivity/mentalopti] → sudo vim /etc/hosts [ mainpc ] [ /dev/pts/3 ] [blog/productivity/mentalopti] → cat /etc/hosts | grep youtube 0.0.0.0 youtube.com www.youtube.com [ mainpc ] [ /dev/pts/3 ] [blog/productivity/mentalopti] → ping www.youtube.com PING youtube.com (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1...
На практике, конечно, никто не делает бесконечные сети, поскольку тут также, как и в коммутаторах, может возникнуть зацикливание, когда ввиду определенной настройки маршрутов пакет будет бесконечно перемещаться между маршрутизаторами. Для защиты от этого придуман механизм TTL (Time to live - время жизни): при отправке в заголовок третьего уровня добавляется счетчик времени жизни пакета (как правило, 255).