JTN Jaringan Tanpa Nama

Jadi langkah selanjutnya adalah jangan install Webmin dulu . Perbaiki repo dulu, lalu cek gnupg , baru lanjut install Webmin. Jalankan ini persis: cat > /etc/apt/sources.list <<'EOF' deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware deb http://deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware EOF apt clean apt update apt install -y wget curl gnupg ca-certificates apt policy gnupg Kalau sudah benar, output apt policy gnupg harus bukan : Candidate: (none) Kalau sudah muncul versi kandidat, lanjut: wget -O /root/webmin-setup-repo.sh https://raw.githubusercontent.com/webmin/webmin/master/webmin-setup-repo.sh sh /root/webmin-setup-repo.sh apt update apt install -y webmin systemctl status webmin ss -lntp | grep...

 Saya sudah cek: di Debian 12 paketnya bukan bird1 , tapi bird versi 1.6.8; paket bird-bgp hanya paket transisi yang menarik ke bird . Jadi untuk BGP di Debian 12, target yang benar adalah bird atau bird-bgp dari repo Bookworm. Thought for 1m 9s Bisa. Di Debian 12, untuk BIRD v1 paket yang dipakai adalah bird versi 1.6.8-2.1 . Paket bird-bgp di Bookworm cuma paket transisi yang mengarah ke bird , dan birdc ikut terpasang dari paket bird . Paket bird mendukung BGP, OSPF, RIP, IPv4, dan IPv6. Install manual dari URL .deb Untuk amd64 : wget https://deb.debian.org/debian/pool/main/b/bird/bird_1.6.8-2.1_amd64.deb sudo apt install ./bird_1.6.8-2.1_amd64.deb Untuk arm64 : wget https://deb.debian.org/debian/pool/main/b/bird/bird_1.6.8-2.1_arm64.deb sudo apt install ./bird_1.6.8-2.1_arm64.deb Nama file .deb untuk amd64 dan arm64 itu memang tersedia di pool Debian mirror. Kalau mau langsung dari URL tanpa simpan nama file: wget -O /tmp/bird.deb https://deb.debian.org/debian...

  How To Enforce Google Safe Search And YouTube Restricted Mode On Your Network Updated: 27 Aug 2025 With the release of  Technitium DNS Server  v5, a new feature called ANAME resource record has been introduced. ANAME resource record implementation is similar to the  IETF draft  with respect to its core functionality that allows adding a CNAME like functionality to the zone root. Essentially, ANAME is similar to CNAME except that the authoritative DNS server resolves the A or AAAA records by itself and returns them. The new release also adds Conditional Forwarder feature that can be combined with the ANAME feature to enforce Google's Safe Search or YouTube's Restricted Mode. To configure Google's Safe Search, you need to add a new "google.com" Conditional Forwarder zone with "Use This DNS Server" option enabled. The "Use This DNS Server" option tells the DNS Server to forward all the queries to itself so that you do not need to configure any o...

  The purpose of this lab is to show how Juniper policy-options can be used to automatically increase AS path length based on community tags attached to routes sent over BGP. BGP AS path length is one option commonly used to determine the best path to a route on the Internet. The AS path length can also be used to influence how traffic is returned when a specific path is required. In the diagram below, we see the network  10.103.0.0/16  is announced to 2 upstream providers. From the  Internet's  perspective there are 2 equal cost return paths. To avoid returning through  LogicalSystem-2 , we can increase the length of the AS path through this hop. BGP will select the route with the shortest hop count, eliminating  LogicalSystem-2  as a viable router. In this lab there are 2 routers  LogicalSystem-1  and  LogicalSystem-2 . There is no  router-3  as seen in the diagram above: Details Juniper Config We are going to configure ...

  Expanding on yesterday’s   BGP Peering   configuration. Today we enable basic BGP prefix filtering. Exchanging routes on the Internet through BGP requires a fair bit of trust in the downstream organization to only send routes they are authoritative for. Without proper filtering, anyone could announce Googles 8.8.8.0/24 route and potentially redirect this critical  DNS traffic back to a rogue location . For a service provider, it is critical to deny all inbound prefixes and only allow those which are properly authorized to do so. Proper  LoAs  and  routing registries  are necessary to validate subnet ownerships. Once ownership is confirmed, proper filtering needs to take place. Below is a basic BGP filter configuration to deny all prefixes and only allow subnets properly authorized by the BGP neighbor. Details Imported routes before BGP prefix filtering: jemurray@juniper-1# run show route receive-protocol bgp 192.168.99.1 logical-system LogicalSy...