From 63eef79202f15f6822d2e2fb8dd14bdb8ad63dd5 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Tue, 5 May 2026 11:08:00 +0200 Subject: [PATCH] chore: sync content to repo (#9906) Co-authored-by: nilbuild <4921183+nilbuild@users.noreply.github.com> --- .../access-points--controllers@x1B9MVsG_C-CejgLAeTzA.md | 3 +++ .../content/access-points@XPOTGRx3lpaHHNlzlMTPq.md | 3 +++ .../content/application@IVpbjVpRESZvx8k2Mik5B.md | 3 +++ .../content/application@bnYi5Bwth3f_nOpRDywXc.md | 3 +++ .../network-engineer/content/arp@FuIjDNBlT5SSf9lCG_e3e.md | 3 +++ .../content/bandwidth@dmzQXBY3u5dZ9OtXLSE11.md | 3 +++ .../network-engineer/content/bgp@gCdUfkMlZwamhOpM5aUqr.md | 3 +++ .../content/bluetooth-basics@VdAObqd1uue--xbej2M-f.md | 3 +++ .../network-engineer/content/cidr@y43H6qnMn4qUTjInlGR04.md | 3 +++ .../content/circuit-level-gateway@bolfExgkr0i8jEbw-GF3O.md | 3 +++ .../content/client-server-network@15Q1VPROHgjfaJkTLOfly.md | 3 +++ .../network-engineer/content/client@8QCl0RNdxtpva4AxJUKMT.md | 3 +++ .../network-engineer/content/cloud@GQNvSg3w5UUtpre_9_Pjl.md | 3 +++ .../content/cloudflare@ltBgGfY9KOS87dPUs476I.md | 3 +++ .../content/data-link@wWaxMK7-hGSAZbp7RHrnH.md | 3 +++ .../content/default-gateway@Z9B1TI61zhm7Vp-yur0pD.md | 3 +++ .../network-engineer/content/dhcp@yL4HVbX33i2wAj-k92X48.md | 3 +++ .../network-engineer/content/dns@plhYS2KebLyhuudwhEWHZ.md | 3 +++ .../content/dos--ddos@Absx6bmAk6xq8KDGC5e70.md | 3 +++ .../network-engineer/content/eigrp@tgLkAZB5G4XZj_2QS9mnZ.md | 3 +++ .../content/encryption-basics@oxORoWnDRfGLor3BV76Wo.md | 3 +++ .../network-engineer/content/failover@PcFSE-h39-bLmrVcc1ae7.md | 3 +++ .../content/firewalls@QiTR_A2pALS4UD7cOndjR.md | 3 +++ .../network-engineer/content/frame@JHvS4yZ7z8XyimBXmNG4r.md | 3 +++ .../content/ftp--sftp@yf85bJUO52dfE4G5wjSm9.md | 3 +++ .../network-engineer/content/google@cjUzC-pYTZCSNKeY3fFro.md | 3 +++ .../network-engineer/content/host@klp3FKanVxF2EudcTw4py.md | 3 +++ .../content/hotspot-and-tethering@uEQVBbo3E7eBCyl_XVTuU.md | 3 +++ .../how-does-the-internet-work@k51wR5lAwf7qI-p4jb8ih.md | 3 +++ .../content/http--https@_st-ChGja7h83_MOwtiF2.md | 3 +++ .../network-engineer/content/hub@p9J57XYINH7TYgjw9G-r8.md | 3 +++ .../network-engineer/content/ids--ips@gqRtzgYUs87I7en2MCPSw.md | 3 +++ .../network-engineer/content/internet@TMBH_Y5fPYCIcjhISUojv.md | 3 +++ .../content/introduction@_OZl6uYkb61iQ_Wb0Q70Q.md | 3 +++ .../content/ip-address@FwwaKfxW5j5r4_lN6_G8Z.md | 3 +++ .../content/ip-addressing@2Ajvxz7ErF9tFKi6TuwI_.md | 3 +++ .../content/ip-vs-mac-vs-arp@eXoOjsMKNi90_sRdBc_nY.md | 3 +++ .../content/ipsec-vs-ssl-vpn@LesiUZyQTRgQErALy5W-v.md | 3 +++ .../content/ipv4-vs-ipv6@wzYaf1wtbo2RQ8JSRawFM.md | 3 +++ .../network-engineer/content/lan@6Wfv3THDhldz_9M6Hv1Gr.md | 3 +++ .../network-engineer/content/latency@u1nJXjWZekrzyiDvri6-O.md | 3 +++ .../content/least-connections@1Os97-x1qqdLJyKAjICiV.md | 3 +++ .../content/link-aggregation@h4_EMwTv7j_06MsBhURvg.md | 3 +++ .../content/load-balancer@R5dmATbOlYEFce7rQImiw.md | 3 +++ .../content/mac-address-tables@Yoj06pntnFzv2NDlr6seC.md | 3 +++ .../content/mac-address@6zxS5esVlRNIDrQuZBaHz.md | 3 +++ .../network-engineer/content/man@usgE8mpRUSLMRv7d0kXy3.md | 3 +++ .../content/mobile-networks@nBXPiMyDKkFtD25ReqUEF.md | 3 +++ .../network-engineer/content/modems@5aZe1jNCH2cM-8ZCYeI-e.md | 3 +++ .../network-engineer/content/mpls@uH-ufJAMyoqDlx7RzYsnX.md | 3 +++ .../content/netflow--sflow@sKbTs6q8CBF6_BTDu6xpy.md | 3 +++ .../content/network-access@x6gwBUjdcBwqjrSa_WNkp.md | 3 +++ .../content/network-attacks@iSXa4nyLa6AQDhFRPz87x.md | 3 +++ .../content/network-devices@2b4Bbs-I8k62zOF97Z_uZ.md | 3 +++ .../network-engineer/content/network@20DK-6sEsl8uy6JJoVgE1.md | 3 +++ .../content/next-generation@i7aEMN40vQesQbJENQ6gV.md | 3 +++ .../network-engineer/content/nmap@dwtbPxxNGQtoStpEd_ydY.md | 3 +++ .../network-engineer/content/ntp@b4bKowbNbUcMscWrrT_-k.md | 3 +++ .../content/observability@PHqTXlkAaRPhmRod52aP3.md | 3 +++ .../network-engineer/content/opendns@laCGHS68FdPDeBpC172vo.md | 3 +++ .../content/osi-model@pt6RO3SEStG9TJOWpt_8D.md | 3 +++ .../network-engineer/content/ospf@OZICDRrSq-KJNAGTlmwr7.md | 3 +++ .../network-engineer/content/package@rlUkMwML31YWfLSYLPdaL.md | 3 +++ .../content/packet-filtering@wNwT9OgpslH4YG9BZvQIK.md | 3 +++ .../content/packet-prioritization@IOu0hW9FZsLYe-KIaZZ4s.md | 3 +++ .../network-engineer/content/pan@fLXIQLKecjWUvjIWUaF9r.md | 3 +++ .../content/peer-to-peer-network@DaJDqRCvGNekZ-e6aDVZj.md | 3 +++ .../network-engineer/content/physical@_lqxrKkanbNDimmzcdM1I.md | 3 +++ .../network-engineer/content/port@TJZ9vsSxQlotKCWQ2HHfS.md | 3 +++ .../content/presentation@U3sXE8skdwBwCcYQuKyzk.md | 3 +++ .../network-engineer/content/protocol@9q3EjoReSztEf3wffNDIs.md | 3 +++ .../network-engineer/content/proxy@55_hR5xJzermyLb3lyAvO.md | 3 +++ .../public-vs-private-addresses@DJVkJUV6Sx2Ez6t6yCOm7.md | 3 +++ .../content/qos-quality-of-service@1AWSj4RYLouXC4eJvg2N9.md | 3 +++ .../network-engineer/content/quad9@kSUBDvguhusW8qaCK5bbL.md | 3 +++ .../network-engineer/content/rip@koRzHVPTKTNmTt8dC-h3m.md | 3 +++ .../content/round-robin@uQz1QLVkQtwf8ZeXexEQ1.md | 3 +++ .../network-engineer/content/routers@s_y5I8OZAsmFqj3zier2B.md | 3 +++ .../network-engineer/content/routing@rbm4cELHUgaL_Gl9uuLq1.md | 3 +++ .../network-engineer/content/san@9tkaAhzPhiiGUoL2LqbPb.md | 3 +++ .../network-engineer/content/server@huzbiZu77aeCBVU40C429.md | 3 +++ .../network-engineer/content/session@q6dPa3Nqjw8cmZApzpcZK.md | 3 +++ .../site-to-site-vs-remote-access@e0mUmniS-GT8DccJq95VB.md | 3 +++ .../content/smtp--imap@CxC1hOOue_2aNHs1KdkAV.md | 3 +++ .../network-engineer/content/snmp@KqxGa5MoKuprDLF9OY988.md | 3 +++ .../network-engineer/content/sntp@GhurQiBhFWlYQ7slPP8QU.md | 3 +++ .../network-engineer/content/socket@jvMvCRqstz3Z7cKYv6MZX.md | 3 +++ .../network-engineer/content/ssh@D-4ZVP3RqLuNDzXamRlv3.md | 3 +++ .../network-engineer/content/ssl--tls@ZtMTMBQkOWoM-su3V-T8Z.md | 3 +++ .../content/stateful-inspection@jjdqsmXHNt78cgVDr_gC_.md | 3 +++ .../content/static-vs-dynamic-routing@n3fdYKpMFSkcasrqokPO8.md | 3 +++ .../network-engineer/content/stp@DM50xKwBoRZa0_JdQi07v.md | 3 +++ .../content/subnet-masks@KpifvB6Yn9u32TRBX9hMs.md | 3 +++ .../content/subnetting@d93bl-7gSB8lu43BQlqvY.md | 3 +++ .../content/supernetting@zX1S1ZXm8vTcyXhRvYZGv.md | 3 +++ .../network-engineer/content/switches@4iXennqlVoVVKcV1vCUmP.md | 3 +++ .../content/switching@TLfYI5HUUJBj1MNywlT3Z.md | 3 +++ .../content/tcpip-model@JL4oU_MaY-4QRWKQjMBZb.md | 3 +++ .../content/throughput@BBS99mZfQqfXDEnBlZy1B.md | 3 +++ .../content/traffic-shaping@OoeM99CKlStR1qzyCv1GZ.md | 3 +++ .../content/transmission-media-types@DjlBAH42q4wSa5PUFSbB5.md | 3 +++ .../content/transport@Llr9kp0Oyyj2uZ9qNHCVL.md | 3 +++ .../content/transport@r6i0Wob3RNJrGdEnsZcQ-.md | 3 +++ .../network-engineer/content/vlans@x0bAdjSBNfZ4gm1CwnPBK.md | 3 +++ .../network-engineer/content/vlsm@tXjRU0HJ2d9RWxuOQ79wH.md | 3 +++ .../network-engineer/content/vpn@b2HXcIkkjJB8WhHbrVesk.md | 3 +++ .../network-engineer/content/vpns@WHYQSWWe4mKUl7OC9thyF.md | 3 +++ .../network-engineer/content/wan@1xOaztV7JJaXK9B6Wa4YQ.md | 3 +++ .../content/web-application@xmkSedJJIDwrys8HzDD-j.md | 3 +++ .../content/what-are-networks@0BPBSnyYnEAScnqZ8q5ZX.md | 3 +++ .../content/wifi-standards@Cahf4Y8A0W-EHeeU4dTej.md | 3 +++ .../content/wireless-networking@RCUgWXsit4Jcma9UNBd2c.md | 3 +++ .../content/wireless-security@MThbykuwPtbDeskypaD7I.md | 3 +++ .../content/wireshark@Ly43qxaO0RsKSy-_VuIBx.md | 3 +++ .../network-engineer/content/wlan@D_zZAYVkxB_SLTCuhqkZY.md | 3 +++ .../content/wpa-vs-wps@_J0L4Ir0pxXPVeW7x68dv.md | 3 +++ .../content/zero-trust-architecture@qW27P1HWMCtVkLgVHmU7z.md | 3 +++ 117 files changed, 351 insertions(+) create mode 100644 src/data/roadmaps/network-engineer/content/access-points--controllers@x1B9MVsG_C-CejgLAeTzA.md create mode 100644 src/data/roadmaps/network-engineer/content/access-points@XPOTGRx3lpaHHNlzlMTPq.md create mode 100644 src/data/roadmaps/network-engineer/content/application@IVpbjVpRESZvx8k2Mik5B.md create mode 100644 src/data/roadmaps/network-engineer/content/application@bnYi5Bwth3f_nOpRDywXc.md create mode 100644 src/data/roadmaps/network-engineer/content/arp@FuIjDNBlT5SSf9lCG_e3e.md create mode 100644 src/data/roadmaps/network-engineer/content/bandwidth@dmzQXBY3u5dZ9OtXLSE11.md create mode 100644 src/data/roadmaps/network-engineer/content/bgp@gCdUfkMlZwamhOpM5aUqr.md create mode 100644 src/data/roadmaps/network-engineer/content/bluetooth-basics@VdAObqd1uue--xbej2M-f.md create mode 100644 src/data/roadmaps/network-engineer/content/cidr@y43H6qnMn4qUTjInlGR04.md create mode 100644 src/data/roadmaps/network-engineer/content/circuit-level-gateway@bolfExgkr0i8jEbw-GF3O.md create mode 100644 src/data/roadmaps/network-engineer/content/client-server-network@15Q1VPROHgjfaJkTLOfly.md create mode 100644 src/data/roadmaps/network-engineer/content/client@8QCl0RNdxtpva4AxJUKMT.md create mode 100644 src/data/roadmaps/network-engineer/content/cloud@GQNvSg3w5UUtpre_9_Pjl.md create mode 100644 src/data/roadmaps/network-engineer/content/cloudflare@ltBgGfY9KOS87dPUs476I.md create mode 100644 src/data/roadmaps/network-engineer/content/data-link@wWaxMK7-hGSAZbp7RHrnH.md create mode 100644 src/data/roadmaps/network-engineer/content/default-gateway@Z9B1TI61zhm7Vp-yur0pD.md create mode 100644 src/data/roadmaps/network-engineer/content/dhcp@yL4HVbX33i2wAj-k92X48.md create mode 100644 src/data/roadmaps/network-engineer/content/dns@plhYS2KebLyhuudwhEWHZ.md create mode 100644 src/data/roadmaps/network-engineer/content/dos--ddos@Absx6bmAk6xq8KDGC5e70.md create mode 100644 src/data/roadmaps/network-engineer/content/eigrp@tgLkAZB5G4XZj_2QS9mnZ.md create mode 100644 src/data/roadmaps/network-engineer/content/encryption-basics@oxORoWnDRfGLor3BV76Wo.md create mode 100644 src/data/roadmaps/network-engineer/content/failover@PcFSE-h39-bLmrVcc1ae7.md create mode 100644 src/data/roadmaps/network-engineer/content/firewalls@QiTR_A2pALS4UD7cOndjR.md create mode 100644 src/data/roadmaps/network-engineer/content/frame@JHvS4yZ7z8XyimBXmNG4r.md create mode 100644 src/data/roadmaps/network-engineer/content/ftp--sftp@yf85bJUO52dfE4G5wjSm9.md create mode 100644 src/data/roadmaps/network-engineer/content/google@cjUzC-pYTZCSNKeY3fFro.md create mode 100644 src/data/roadmaps/network-engineer/content/host@klp3FKanVxF2EudcTw4py.md create mode 100644 src/data/roadmaps/network-engineer/content/hotspot-and-tethering@uEQVBbo3E7eBCyl_XVTuU.md create mode 100644 src/data/roadmaps/network-engineer/content/how-does-the-internet-work@k51wR5lAwf7qI-p4jb8ih.md create mode 100644 src/data/roadmaps/network-engineer/content/http--https@_st-ChGja7h83_MOwtiF2.md create mode 100644 src/data/roadmaps/network-engineer/content/hub@p9J57XYINH7TYgjw9G-r8.md create mode 100644 src/data/roadmaps/network-engineer/content/ids--ips@gqRtzgYUs87I7en2MCPSw.md create mode 100644 src/data/roadmaps/network-engineer/content/internet@TMBH_Y5fPYCIcjhISUojv.md create mode 100644 src/data/roadmaps/network-engineer/content/introduction@_OZl6uYkb61iQ_Wb0Q70Q.md create mode 100644 src/data/roadmaps/network-engineer/content/ip-address@FwwaKfxW5j5r4_lN6_G8Z.md create mode 100644 src/data/roadmaps/network-engineer/content/ip-addressing@2Ajvxz7ErF9tFKi6TuwI_.md create mode 100644 src/data/roadmaps/network-engineer/content/ip-vs-mac-vs-arp@eXoOjsMKNi90_sRdBc_nY.md create mode 100644 src/data/roadmaps/network-engineer/content/ipsec-vs-ssl-vpn@LesiUZyQTRgQErALy5W-v.md create mode 100644 src/data/roadmaps/network-engineer/content/ipv4-vs-ipv6@wzYaf1wtbo2RQ8JSRawFM.md create mode 100644 src/data/roadmaps/network-engineer/content/lan@6Wfv3THDhldz_9M6Hv1Gr.md create mode 100644 src/data/roadmaps/network-engineer/content/latency@u1nJXjWZekrzyiDvri6-O.md create mode 100644 src/data/roadmaps/network-engineer/content/least-connections@1Os97-x1qqdLJyKAjICiV.md create mode 100644 src/data/roadmaps/network-engineer/content/link-aggregation@h4_EMwTv7j_06MsBhURvg.md create mode 100644 src/data/roadmaps/network-engineer/content/load-balancer@R5dmATbOlYEFce7rQImiw.md create mode 100644 src/data/roadmaps/network-engineer/content/mac-address-tables@Yoj06pntnFzv2NDlr6seC.md create mode 100644 src/data/roadmaps/network-engineer/content/mac-address@6zxS5esVlRNIDrQuZBaHz.md create mode 100644 src/data/roadmaps/network-engineer/content/man@usgE8mpRUSLMRv7d0kXy3.md create mode 100644 src/data/roadmaps/network-engineer/content/mobile-networks@nBXPiMyDKkFtD25ReqUEF.md create mode 100644 src/data/roadmaps/network-engineer/content/modems@5aZe1jNCH2cM-8ZCYeI-e.md create mode 100644 src/data/roadmaps/network-engineer/content/mpls@uH-ufJAMyoqDlx7RzYsnX.md create mode 100644 src/data/roadmaps/network-engineer/content/netflow--sflow@sKbTs6q8CBF6_BTDu6xpy.md create mode 100644 src/data/roadmaps/network-engineer/content/network-access@x6gwBUjdcBwqjrSa_WNkp.md create mode 100644 src/data/roadmaps/network-engineer/content/network-attacks@iSXa4nyLa6AQDhFRPz87x.md create mode 100644 src/data/roadmaps/network-engineer/content/network-devices@2b4Bbs-I8k62zOF97Z_uZ.md create mode 100644 src/data/roadmaps/network-engineer/content/network@20DK-6sEsl8uy6JJoVgE1.md create mode 100644 src/data/roadmaps/network-engineer/content/next-generation@i7aEMN40vQesQbJENQ6gV.md create mode 100644 src/data/roadmaps/network-engineer/content/nmap@dwtbPxxNGQtoStpEd_ydY.md create mode 100644 src/data/roadmaps/network-engineer/content/ntp@b4bKowbNbUcMscWrrT_-k.md create mode 100644 src/data/roadmaps/network-engineer/content/observability@PHqTXlkAaRPhmRod52aP3.md create mode 100644 src/data/roadmaps/network-engineer/content/opendns@laCGHS68FdPDeBpC172vo.md create mode 100644 src/data/roadmaps/network-engineer/content/osi-model@pt6RO3SEStG9TJOWpt_8D.md create mode 100644 src/data/roadmaps/network-engineer/content/ospf@OZICDRrSq-KJNAGTlmwr7.md create mode 100644 src/data/roadmaps/network-engineer/content/package@rlUkMwML31YWfLSYLPdaL.md create mode 100644 src/data/roadmaps/network-engineer/content/packet-filtering@wNwT9OgpslH4YG9BZvQIK.md create mode 100644 src/data/roadmaps/network-engineer/content/packet-prioritization@IOu0hW9FZsLYe-KIaZZ4s.md create mode 100644 src/data/roadmaps/network-engineer/content/pan@fLXIQLKecjWUvjIWUaF9r.md create mode 100644 src/data/roadmaps/network-engineer/content/peer-to-peer-network@DaJDqRCvGNekZ-e6aDVZj.md create mode 100644 src/data/roadmaps/network-engineer/content/physical@_lqxrKkanbNDimmzcdM1I.md create mode 100644 src/data/roadmaps/network-engineer/content/port@TJZ9vsSxQlotKCWQ2HHfS.md create mode 100644 src/data/roadmaps/network-engineer/content/presentation@U3sXE8skdwBwCcYQuKyzk.md create mode 100644 src/data/roadmaps/network-engineer/content/protocol@9q3EjoReSztEf3wffNDIs.md create mode 100644 src/data/roadmaps/network-engineer/content/proxy@55_hR5xJzermyLb3lyAvO.md create mode 100644 src/data/roadmaps/network-engineer/content/public-vs-private-addresses@DJVkJUV6Sx2Ez6t6yCOm7.md create mode 100644 src/data/roadmaps/network-engineer/content/qos-quality-of-service@1AWSj4RYLouXC4eJvg2N9.md create mode 100644 src/data/roadmaps/network-engineer/content/quad9@kSUBDvguhusW8qaCK5bbL.md create mode 100644 src/data/roadmaps/network-engineer/content/rip@koRzHVPTKTNmTt8dC-h3m.md create mode 100644 src/data/roadmaps/network-engineer/content/round-robin@uQz1QLVkQtwf8ZeXexEQ1.md create mode 100644 src/data/roadmaps/network-engineer/content/routers@s_y5I8OZAsmFqj3zier2B.md create mode 100644 src/data/roadmaps/network-engineer/content/routing@rbm4cELHUgaL_Gl9uuLq1.md create mode 100644 src/data/roadmaps/network-engineer/content/san@9tkaAhzPhiiGUoL2LqbPb.md create mode 100644 src/data/roadmaps/network-engineer/content/server@huzbiZu77aeCBVU40C429.md create mode 100644 src/data/roadmaps/network-engineer/content/session@q6dPa3Nqjw8cmZApzpcZK.md create mode 100644 src/data/roadmaps/network-engineer/content/site-to-site-vs-remote-access@e0mUmniS-GT8DccJq95VB.md create mode 100644 src/data/roadmaps/network-engineer/content/smtp--imap@CxC1hOOue_2aNHs1KdkAV.md create mode 100644 src/data/roadmaps/network-engineer/content/snmp@KqxGa5MoKuprDLF9OY988.md create mode 100644 src/data/roadmaps/network-engineer/content/sntp@GhurQiBhFWlYQ7slPP8QU.md create mode 100644 src/data/roadmaps/network-engineer/content/socket@jvMvCRqstz3Z7cKYv6MZX.md create mode 100644 src/data/roadmaps/network-engineer/content/ssh@D-4ZVP3RqLuNDzXamRlv3.md create mode 100644 src/data/roadmaps/network-engineer/content/ssl--tls@ZtMTMBQkOWoM-su3V-T8Z.md create mode 100644 src/data/roadmaps/network-engineer/content/stateful-inspection@jjdqsmXHNt78cgVDr_gC_.md create mode 100644 src/data/roadmaps/network-engineer/content/static-vs-dynamic-routing@n3fdYKpMFSkcasrqokPO8.md create mode 100644 src/data/roadmaps/network-engineer/content/stp@DM50xKwBoRZa0_JdQi07v.md create mode 100644 src/data/roadmaps/network-engineer/content/subnet-masks@KpifvB6Yn9u32TRBX9hMs.md create mode 100644 src/data/roadmaps/network-engineer/content/subnetting@d93bl-7gSB8lu43BQlqvY.md create mode 100644 src/data/roadmaps/network-engineer/content/supernetting@zX1S1ZXm8vTcyXhRvYZGv.md create mode 100644 src/data/roadmaps/network-engineer/content/switches@4iXennqlVoVVKcV1vCUmP.md create mode 100644 src/data/roadmaps/network-engineer/content/switching@TLfYI5HUUJBj1MNywlT3Z.md create mode 100644 src/data/roadmaps/network-engineer/content/tcpip-model@JL4oU_MaY-4QRWKQjMBZb.md create mode 100644 src/data/roadmaps/network-engineer/content/throughput@BBS99mZfQqfXDEnBlZy1B.md create mode 100644 src/data/roadmaps/network-engineer/content/traffic-shaping@OoeM99CKlStR1qzyCv1GZ.md create mode 100644 src/data/roadmaps/network-engineer/content/transmission-media-types@DjlBAH42q4wSa5PUFSbB5.md create mode 100644 src/data/roadmaps/network-engineer/content/transport@Llr9kp0Oyyj2uZ9qNHCVL.md create mode 100644 src/data/roadmaps/network-engineer/content/transport@r6i0Wob3RNJrGdEnsZcQ-.md create mode 100644 src/data/roadmaps/network-engineer/content/vlans@x0bAdjSBNfZ4gm1CwnPBK.md create mode 100644 src/data/roadmaps/network-engineer/content/vlsm@tXjRU0HJ2d9RWxuOQ79wH.md create mode 100644 src/data/roadmaps/network-engineer/content/vpn@b2HXcIkkjJB8WhHbrVesk.md create mode 100644 src/data/roadmaps/network-engineer/content/vpns@WHYQSWWe4mKUl7OC9thyF.md create mode 100644 src/data/roadmaps/network-engineer/content/wan@1xOaztV7JJaXK9B6Wa4YQ.md create mode 100644 src/data/roadmaps/network-engineer/content/web-application@xmkSedJJIDwrys8HzDD-j.md create mode 100644 src/data/roadmaps/network-engineer/content/what-are-networks@0BPBSnyYnEAScnqZ8q5ZX.md create mode 100644 src/data/roadmaps/network-engineer/content/wifi-standards@Cahf4Y8A0W-EHeeU4dTej.md create mode 100644 src/data/roadmaps/network-engineer/content/wireless-networking@RCUgWXsit4Jcma9UNBd2c.md create mode 100644 src/data/roadmaps/network-engineer/content/wireless-security@MThbykuwPtbDeskypaD7I.md create mode 100644 src/data/roadmaps/network-engineer/content/wireshark@Ly43qxaO0RsKSy-_VuIBx.md create mode 100644 src/data/roadmaps/network-engineer/content/wlan@D_zZAYVkxB_SLTCuhqkZY.md create mode 100644 src/data/roadmaps/network-engineer/content/wpa-vs-wps@_J0L4Ir0pxXPVeW7x68dv.md create mode 100644 src/data/roadmaps/network-engineer/content/zero-trust-architecture@qW27P1HWMCtVkLgVHmU7z.md diff --git a/src/data/roadmaps/network-engineer/content/access-points--controllers@x1B9MVsG_C-CejgLAeTzA.md b/src/data/roadmaps/network-engineer/content/access-points--controllers@x1B9MVsG_C-CejgLAeTzA.md new file mode 100644 index 000000000..89a9fe3aa --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/access-points--controllers@x1B9MVsG_C-CejgLAeTzA.md @@ -0,0 +1,3 @@ +# Access Points & Controllers + +Wireless access points (APs) are devices that broadcast Wi-Fi signals and connect wireless clients to a wired network. In larger deployments, multiple access points are managed by a wireless controller, which centralizes configuration, monitoring, and roaming policies across all APs. This controller-based architecture simplifies management and ensures consistent performance and security across the entire wireless network. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/access-points@XPOTGRx3lpaHHNlzlMTPq.md b/src/data/roadmaps/network-engineer/content/access-points@XPOTGRx3lpaHHNlzlMTPq.md new file mode 100644 index 000000000..3c6d53a68 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/access-points@XPOTGRx3lpaHHNlzlMTPq.md @@ -0,0 +1,3 @@ +# Access Points + +A wireless access point (AP) is a device that creates a wireless local area network, typically in an office or large building, by connecting to a wired router or switch and broadcasting a Wi-Fi signal. Multiple access points can be deployed across a large area to extend wireless coverage and allow devices to roam seamlessly. Access points are distinct from routers —they extend the network wirelessly but do not typically perform routing functions on their own. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/application@IVpbjVpRESZvx8k2Mik5B.md b/src/data/roadmaps/network-engineer/content/application@IVpbjVpRESZvx8k2Mik5B.md new file mode 100644 index 000000000..6392438dd --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/application@IVpbjVpRESZvx8k2Mik5B.md @@ -0,0 +1,3 @@ +# Application + +The Application layer is the seventh and topmost layer of the OSI model, where end-user software interacts with the network. It provides network services directly to applications, enabling functions like web browsing, email, file transfer, and domain name resolution. Protocols such as HTTP, FTP, SMTP, and DNS all operate at this layer. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/application@bnYi5Bwth3f_nOpRDywXc.md b/src/data/roadmaps/network-engineer/content/application@bnYi5Bwth3f_nOpRDywXc.md new file mode 100644 index 000000000..779416e28 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/application@bnYi5Bwth3f_nOpRDywXc.md @@ -0,0 +1,3 @@ +# Application + +The Application layer of the TCP/IP model is the topmost layer and encompasses all the protocols that applications use to communicate over the network. It combines the functions of the OSI Session, Presentation, and Application layers into one. Protocols like HTTP, DNS, SMTP, FTP, and SSH all operate here, directly serving user-facing applications. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/arp@FuIjDNBlT5SSf9lCG_e3e.md b/src/data/roadmaps/network-engineer/content/arp@FuIjDNBlT5SSf9lCG_e3e.md new file mode 100644 index 000000000..b5ee6bcab --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/arp@FuIjDNBlT5SSf9lCG_e3e.md @@ -0,0 +1,3 @@ +# ARP + +ARP, or Address Resolution Protocol, is used to map an IP address to a physical MAC address on a local network. When a device wants to communicate with another device on the same network, it uses ARP to discover which MAC address corresponds to a known IP address. The result is stored temporarily in an ARP cache to speed up future lookups. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/bandwidth@dmzQXBY3u5dZ9OtXLSE11.md b/src/data/roadmaps/network-engineer/content/bandwidth@dmzQXBY3u5dZ9OtXLSE11.md new file mode 100644 index 000000000..c7092a91d --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/bandwidth@dmzQXBY3u5dZ9OtXLSE11.md @@ -0,0 +1,3 @@ +# Bandwidth + +Bandwidth refers to the maximum amount of data that can be transmitted over a network connection in a given amount of time, typically measured in bits per second (bps). Higher bandwidth means more data can flow simultaneously, which generally results in faster network performance. It is often compared to the width of a pipe: the wider the pipe, the more water (data) can flow through it at once. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/bgp@gCdUfkMlZwamhOpM5aUqr.md b/src/data/roadmaps/network-engineer/content/bgp@gCdUfkMlZwamhOpM5aUqr.md new file mode 100644 index 000000000..7206e39ff --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/bgp@gCdUfkMlZwamhOpM5aUqr.md @@ -0,0 +1,3 @@ +# BGP + +BGP, or Border Gateway Protocol, is the routing protocol that powers the Internet by exchanging routing information between autonomous systems, i.e., the large networks operated by ISPs, corporations, and other organizations. It is a path-vector protocol that makes routing decisions based on network policies, path attributes, and rules rather than simply the shortest path. BGP is responsible for ensuring that traffic can reach any two points on the global Internet. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/bluetooth-basics@VdAObqd1uue--xbej2M-f.md b/src/data/roadmaps/network-engineer/content/bluetooth-basics@VdAObqd1uue--xbej2M-f.md new file mode 100644 index 000000000..7da38eb97 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/bluetooth-basics@VdAObqd1uue--xbej2M-f.md @@ -0,0 +1,3 @@ +# Bluetooth Basics + +Bluetooth is a short-range wireless communication standard used to connect devices over distances typically up to 10 meters. It operates in the 2.4 GHz frequency band and is designed for low-power, point-to-point or small-group connections between devices like phones, headsets, keyboards, and IoT sensors. Bluetooth is not a replacement for Wi-Fi, but complements it for personal area networking and device pairing scenarios. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/cidr@y43H6qnMn4qUTjInlGR04.md b/src/data/roadmaps/network-engineer/content/cidr@y43H6qnMn4qUTjInlGR04.md new file mode 100644 index 000000000..1d641cac5 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/cidr@y43H6qnMn4qUTjInlGR04.md @@ -0,0 +1,3 @@ +# CIDR + +CIDR, or Classless Inter-Domain Routing, is a method of allocating IP addresses and routing that replaced the older class-based system. Instead of fixed classes (A, B, C), CIDR uses a slash notation (e.g., 192.168.1.0/24) to indicate how many bits are used for the network portion of the address. This allows for more flexible and efficient use of IP address space and is the standard method used in modern networking. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/circuit-level-gateway@bolfExgkr0i8jEbw-GF3O.md b/src/data/roadmaps/network-engineer/content/circuit-level-gateway@bolfExgkr0i8jEbw-GF3O.md new file mode 100644 index 000000000..27190f69f --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/circuit-level-gateway@bolfExgkr0i8jEbw-GF3O.md @@ -0,0 +1,3 @@ +# Circuit Level Gateway + +A circuit-level gateway is a type of firewall that operates at the session layer and monitors TCP handshakes to verify that a connection is legitimate before allowing data to flow. Unlike application-layer proxies, it does not inspect the content of the data itself — only the connection establishment. Once a session is deemed valid, traffic passes through without further inspection, making it faster but less thorough than application-layer firewalls. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/client-server-network@15Q1VPROHgjfaJkTLOfly.md b/src/data/roadmaps/network-engineer/content/client-server-network@15Q1VPROHgjfaJkTLOfly.md new file mode 100644 index 000000000..510f066aa --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/client-server-network@15Q1VPROHgjfaJkTLOfly.md @@ -0,0 +1,3 @@ +# Client-Server Network + +A client-server network is a model where one or more central servers provide resources or services, and multiple client devices request and consume those resources. The server manages shared resources such as files, databases, or applications, while clients interact with them through the network. This model is widely used in enterprise environments because it centralizes management, improves security, and makes it easier to scale. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/client@8QCl0RNdxtpva4AxJUKMT.md b/src/data/roadmaps/network-engineer/content/client@8QCl0RNdxtpva4AxJUKMT.md new file mode 100644 index 000000000..0fc29490a --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/client@8QCl0RNdxtpva4AxJUKMT.md @@ -0,0 +1,3 @@ +# Client + +A client is any device or software application that sends requests to a server to access resources or services. In everyday terms, your web browser acts as a client when it asks a web server to load a page. Clients initiate communication in the client-server model and rely on servers to respond with the requested data or functionality. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/cloud@GQNvSg3w5UUtpre_9_Pjl.md b/src/data/roadmaps/network-engineer/content/cloud@GQNvSg3w5UUtpre_9_Pjl.md new file mode 100644 index 000000000..dbdfffda1 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/cloud@GQNvSg3w5UUtpre_9_Pjl.md @@ -0,0 +1,3 @@ +# Cloud + +In networking, the cloud refers to a model of delivering computing resources, such as servers, storage, databases, and networking, over the Internet on a pay-as-you-go basis. Rather than owning and maintaining physical infrastructure, organizations can provision and scale resources through cloud providers like AWS, Azure, or Google Cloud. This shifts network design considerations to include connectivity to cloud environments, hybrid architectures, and cloud-native security. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/cloudflare@ltBgGfY9KOS87dPUs476I.md b/src/data/roadmaps/network-engineer/content/cloudflare@ltBgGfY9KOS87dPUs476I.md new file mode 100644 index 000000000..c183a4f3d --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/cloudflare@ltBgGfY9KOS87dPUs476I.md @@ -0,0 +1,3 @@ +# Cloudflare + +Cloudflare's DNS resolver, known by its address 1.1.1.1, is a public DNS service focused on speed and privacy. It is consistently ranked among the fastest DNS resolvers in the world and does not log user queries for advertising purposes. Cloudflare also supports DNS over HTTPS (DoH) and DNS over TLS (DoT) to encrypt DNS queries and prevent snooping. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/data-link@wWaxMK7-hGSAZbp7RHrnH.md b/src/data/roadmaps/network-engineer/content/data-link@wWaxMK7-hGSAZbp7RHrnH.md new file mode 100644 index 000000000..d2f82fb85 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/data-link@wWaxMK7-hGSAZbp7RHrnH.md @@ -0,0 +1,3 @@ +# Data Link + +The Data Link layer is the second layer of the OSI model, responsible for node-to-node data transfer and error detection within a single network segment. It organizes raw bits from the Physical layer into frames and uses MAC addresses to identify devices on the local network. This layer is divided into two sublayers: the Logical Link Control (LLC) and the Media Access Control (MAC). \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/default-gateway@Z9B1TI61zhm7Vp-yur0pD.md b/src/data/roadmaps/network-engineer/content/default-gateway@Z9B1TI61zhm7Vp-yur0pD.md new file mode 100644 index 000000000..f32702386 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/default-gateway@Z9B1TI61zhm7Vp-yur0pD.md @@ -0,0 +1,3 @@ +# Default Gateway + +A default gateway is the IP address of the router that a device uses to send traffic destined for networks outside its own local subnet. When a device does not have a specific route for a destination, it forwards the packet to the default gateway, which then handles the routing decision. In most home and office networks, the default gateway is the IP address of the local router. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/dhcp@yL4HVbX33i2wAj-k92X48.md b/src/data/roadmaps/network-engineer/content/dhcp@yL4HVbX33i2wAj-k92X48.md new file mode 100644 index 000000000..6bbba6e02 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/dhcp@yL4HVbX33i2wAj-k92X48.md @@ -0,0 +1,3 @@ +# DHCP + +DHCP, or Dynamic Host Configuration Protocol, is a network management protocol that automatically assigns IP addresses and other network configuration parameters to devices when they join a network. Without DHCP, administrators would need to manually configure the IP address, subnet mask, gateway, and DNS settings on every device. DHCP simplifies network management by handling these assignments dynamically from a central server or router. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/dns@plhYS2KebLyhuudwhEWHZ.md b/src/data/roadmaps/network-engineer/content/dns@plhYS2KebLyhuudwhEWHZ.md new file mode 100644 index 000000000..6c1105b96 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/dns@plhYS2KebLyhuudwhEWHZ.md @@ -0,0 +1,3 @@ +# DNS + +DNS, or Domain Name System, is the system that translates human-readable domain names like www.example.com into IP addresses that computers use to identify each other on the network. Without DNS, users would need to memorize IP addresses to visit websites or access online services. DNS operates as a distributed, hierarchical database spread across many servers around the world. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/dos--ddos@Absx6bmAk6xq8KDGC5e70.md b/src/data/roadmaps/network-engineer/content/dos--ddos@Absx6bmAk6xq8KDGC5e70.md new file mode 100644 index 000000000..b501c906a --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/dos--ddos@Absx6bmAk6xq8KDGC5e70.md @@ -0,0 +1,3 @@ +# DoS & DDoS + +A DoS (Denial of Service) attack is an attempt to make a network resource or service unavailable by overwhelming it with a flood of illegitimate traffic or requests. A DDoS (Distributed Denial of Service) attack is the same concept but launched from many different sources simultaneously — often thousands of compromised machines in a botnet — making it much harder to block. These attacks do not typically steal data but can cause significant downtime and financial damage to the targeted organization. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/eigrp@tgLkAZB5G4XZj_2QS9mnZ.md b/src/data/roadmaps/network-engineer/content/eigrp@tgLkAZB5G4XZj_2QS9mnZ.md new file mode 100644 index 000000000..ea4f2830d --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/eigrp@tgLkAZB5G4XZj_2QS9mnZ.md @@ -0,0 +1,3 @@ +# EIGRP + +EIGRP, or Enhanced Interior Gateway Routing Protocol, is an advanced distance-vector routing protocol developed by Cisco that combines features of both distance-vector and link-state protocols. It uses a composite metric based on bandwidth, delay, load, and reliability to calculate the best route and converges faster than traditional distance-vector protocols. EIGRP is efficient in terms of bandwidth usage and CPU load, making it popular in Cisco-based enterprise networks. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/encryption-basics@oxORoWnDRfGLor3BV76Wo.md b/src/data/roadmaps/network-engineer/content/encryption-basics@oxORoWnDRfGLor3BV76Wo.md new file mode 100644 index 000000000..7e3aa9149 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/encryption-basics@oxORoWnDRfGLor3BV76Wo.md @@ -0,0 +1,3 @@ +# Encryption Basics + +Encryption is the process of converting readable data (plaintext) into an unreadable format (ciphertext) using an algorithm and a key, so that only authorized parties with the correct key can decrypt and read it. It is the foundation of data security in networking, protecting information in transit and at rest from unauthorized access. The two main types are symmetric encryption, where the same key is used to encrypt and decrypt, and asymmetric encryption, which uses a pair of public and private keys. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/failover@PcFSE-h39-bLmrVcc1ae7.md b/src/data/roadmaps/network-engineer/content/failover@PcFSE-h39-bLmrVcc1ae7.md new file mode 100644 index 000000000..dcc894783 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/failover@PcFSE-h39-bLmrVcc1ae7.md @@ -0,0 +1,3 @@ +# Failover + +Failover is the process by which a system automatically switches to a backup server, network path, or resource when the primary one becomes unavailable due to failure or maintenance. The goal is to minimize downtime and ensure continuity of service without requiring manual intervention. Failover configurations can be active-passive, where the backup sits idle until needed, or active-active, where multiple systems share the load and take over seamlessly if one fails. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/firewalls@QiTR_A2pALS4UD7cOndjR.md b/src/data/roadmaps/network-engineer/content/firewalls@QiTR_A2pALS4UD7cOndjR.md new file mode 100644 index 000000000..7bb747990 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/firewalls@QiTR_A2pALS4UD7cOndjR.md @@ -0,0 +1,3 @@ +# Firewalls + +A firewall is a network security device or software that monitors and controls incoming and outgoing network traffic based on predefined security rules. It acts as a barrier between a trusted internal network and untrusted external networks, blocking traffic that does not meet the specified criteria. Firewalls are a foundational component of network security and can be implemented in hardware, software, or as a cloud-based service. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/frame@JHvS4yZ7z8XyimBXmNG4r.md b/src/data/roadmaps/network-engineer/content/frame@JHvS4yZ7z8XyimBXmNG4r.md new file mode 100644 index 000000000..c4fad973b --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/frame@JHvS4yZ7z8XyimBXmNG4r.md @@ -0,0 +1,3 @@ +# Frame + +A frame is a unit of data transmission at the Data Link layer of the OSI model. It wraps raw bits into a structured format that includes source and destination MAC addresses, the data payload, and error-checking information. Frames are used to move data between devices on the same local network segment. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/ftp--sftp@yf85bJUO52dfE4G5wjSm9.md b/src/data/roadmaps/network-engineer/content/ftp--sftp@yf85bJUO52dfE4G5wjSm9.md new file mode 100644 index 000000000..a7410d1f0 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/ftp--sftp@yf85bJUO52dfE4G5wjSm9.md @@ -0,0 +1,3 @@ +# FTP / SFTP + +FTP (File Transfer Protocol) is a standard protocol used to transfer files between a client and a server over a network. It operates over two channels (one for commands and one for data), but transmits information in plain text, making it insecure. SFTP (SSH File Transfer Protocol) is a secure alternative that encrypts both commands and data using SSH, making it the preferred choice for transferring sensitive files. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/google@cjUzC-pYTZCSNKeY3fFro.md b/src/data/roadmaps/network-engineer/content/google@cjUzC-pYTZCSNKeY3fFro.md new file mode 100644 index 000000000..691e8f2b7 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/google@cjUzC-pYTZCSNKeY3fFro.md @@ -0,0 +1,3 @@ +# Google + +Google's public DNS service, accessible at 8.8.8.8 and 8.8.4.4, is one of the most widely used DNS resolvers in the world. It provides fast and reliable DNS resolution and supports modern security extensions like DNSSEC to protect against DNS spoofing. Google Public DNS is free to use and is often chosen as an alternative to ISP-provided DNS for its speed and reliability. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/host@klp3FKanVxF2EudcTw4py.md b/src/data/roadmaps/network-engineer/content/host@klp3FKanVxF2EudcTw4py.md new file mode 100644 index 000000000..2cddce376 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/host@klp3FKanVxF2EudcTw4py.md @@ -0,0 +1,3 @@ +# Host + +A host is any device connected to a network that has an IP address and can send or receive data. This includes computers, servers, printers, smartphones, and any other networked device. The term is used broadly to refer to any endpoint that participates in network communication. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/hotspot-and-tethering@uEQVBbo3E7eBCyl_XVTuU.md b/src/data/roadmaps/network-engineer/content/hotspot-and-tethering@uEQVBbo3E7eBCyl_XVTuU.md new file mode 100644 index 000000000..69f937edc --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/hotspot-and-tethering@uEQVBbo3E7eBCyl_XVTuU.md @@ -0,0 +1,3 @@ +# Hotspot and Tethering + +A hotspot is a physical location or device that provides wireless Internet access to other devices, typically by sharing a cellular data connection. Tethering is the act of connecting a device, such as a laptop, to a smartphone's mobile data connection via Wi-Fi, USB, or Bluetooth to access the Internet. Both concepts are relevant for network engineers when designing mobile connectivity solutions or troubleshooting remote access scenarios. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/how-does-the-internet-work@k51wR5lAwf7qI-p4jb8ih.md b/src/data/roadmaps/network-engineer/content/how-does-the-internet-work@k51wR5lAwf7qI-p4jb8ih.md new file mode 100644 index 000000000..30c4ee91f --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/how-does-the-internet-work@k51wR5lAwf7qI-p4jb8ih.md @@ -0,0 +1,3 @@ +# How does the Internet Work? + +The Internet is a massive global network of interconnected computers and devices that communicate by sending data to each other using a shared set of rules. When you visit a website, your device sends a request that travels through multiple routers and networks until it reaches the server hosting that site, which then sends the data back to your screen. This exchange happens through a system of protocols —most notably TCP/IP— that break data into small packets, route them across the network, and reassemble them at the destination. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/http--https@_st-ChGja7h83_MOwtiF2.md b/src/data/roadmaps/network-engineer/content/http--https@_st-ChGja7h83_MOwtiF2.md new file mode 100644 index 000000000..cc2cb479d --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/http--https@_st-ChGja7h83_MOwtiF2.md @@ -0,0 +1,3 @@ +# HTTP / HTTPS + +HTTP (HyperText Transfer Protocol) is the foundation of data communication on the web, defining how messages are formatted and transmitted between browsers and servers. HTTPS is the secure version of HTTP, adding an SSL/TLS encryption layer to protect data from being intercepted during transmission. Most modern websites use HTTPS to ensure privacy and data integrity for their users. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/hub@p9J57XYINH7TYgjw9G-r8.md b/src/data/roadmaps/network-engineer/content/hub@p9J57XYINH7TYgjw9G-r8.md new file mode 100644 index 000000000..f54ac549e --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/hub@p9J57XYINH7TYgjw9G-r8.md @@ -0,0 +1,3 @@ +# Hub + +A hub is a basic network device that connects multiple devices in a LAN and broadcasts incoming data to all connected ports, regardless of the intended recipient. This makes hubs simple but inefficient, as all devices receive all traffic, even if it is not meant for them. Hubs have largely been replaced by switches, which are smarter and handle traffic more efficiently. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/ids--ips@gqRtzgYUs87I7en2MCPSw.md b/src/data/roadmaps/network-engineer/content/ids--ips@gqRtzgYUs87I7en2MCPSw.md new file mode 100644 index 000000000..8094e2703 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/ids--ips@gqRtzgYUs87I7en2MCPSw.md @@ -0,0 +1,3 @@ +# IDS / IPS + +An IDS (Intrusion Detection System) monitors network traffic for suspicious patterns and known attack signatures, alerting administrators when potential threats are detected without taking direct action. An IPS (Intrusion Prevention System) goes a step further by automatically blocking or dropping malicious traffic in real time based on the same detection mechanisms. Together, they provide visibility into network threats and an active layer of defense against intrusions. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/internet@TMBH_Y5fPYCIcjhISUojv.md b/src/data/roadmaps/network-engineer/content/internet@TMBH_Y5fPYCIcjhISUojv.md new file mode 100644 index 000000000..759d39101 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/internet@TMBH_Y5fPYCIcjhISUojv.md @@ -0,0 +1,3 @@ +# Internet + +The Internet layer of the TCP/IP model corresponds to the Network layer of the OSI model and is responsible for logical addressing and routing packets across networks. The primary protocol at this layer is IP (Internet Protocol), which assigns addresses to packets and determines how they are routed toward their destination. ICMP and ARP also operate at this layer. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/introduction@_OZl6uYkb61iQ_Wb0Q70Q.md b/src/data/roadmaps/network-engineer/content/introduction@_OZl6uYkb61iQ_Wb0Q70Q.md new file mode 100644 index 000000000..0d9020366 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/introduction@_OZl6uYkb61iQ_Wb0Q70Q.md @@ -0,0 +1,3 @@ +# Introduction + +A network engineer is a technology professional responsible for designing, building, and maintaining the communication infrastructure that allows computers and devices to exchange data. This includes planning how networks are structured, selecting and configuring hardware like routers and switches, troubleshooting connectivity issues, and ensuring the network remains secure and reliable. Network engineers work across a wide range of environments and must understand both the theoretical principles behind how data travels and the practical skills needed to implement and manage real-world systems. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/ip-address@FwwaKfxW5j5r4_lN6_G8Z.md b/src/data/roadmaps/network-engineer/content/ip-address@FwwaKfxW5j5r4_lN6_G8Z.md new file mode 100644 index 000000000..58fb7e626 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/ip-address@FwwaKfxW5j5r4_lN6_G8Z.md @@ -0,0 +1,3 @@ +# IP Address + +An IP address is a numerical label assigned to each device on a network that uses the Internet Protocol for communication. It serves two main purposes: identifying the host and providing its location in the network for routing purposes. IP addresses come in two versions: IPv4, which uses a 32-bit format, and IPv6, which uses a 128-bit format to accommodate a much larger number of devices. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/ip-addressing@2Ajvxz7ErF9tFKi6TuwI_.md b/src/data/roadmaps/network-engineer/content/ip-addressing@2Ajvxz7ErF9tFKi6TuwI_.md new file mode 100644 index 000000000..e88b443d0 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/ip-addressing@2Ajvxz7ErF9tFKi6TuwI_.md @@ -0,0 +1,3 @@ +# IP Addressing + +IP addressing is the system used to assign unique numerical identifiers to devices on a network so they can communicate with each other. Every device connected to a network needs an IP address, which tells other devices where to send data. IP addresses come in two versions — IPv4 and IPv6 — and can be assigned statically by an administrator or dynamically by a DHCP server. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/ip-vs-mac-vs-arp@eXoOjsMKNi90_sRdBc_nY.md b/src/data/roadmaps/network-engineer/content/ip-vs-mac-vs-arp@eXoOjsMKNi90_sRdBc_nY.md new file mode 100644 index 000000000..84ed28f28 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/ip-vs-mac-vs-arp@eXoOjsMKNi90_sRdBc_nY.md @@ -0,0 +1,3 @@ +# IP vs MAC vs ARP + +An IP address is a logical address used to identify a device across networks and is assigned by software, while a MAC address is a physical address burned into the network interface hardware, used for communication within a local network segment. ARP (Address Resolution Protocol) bridges the two by resolving a known IP address to its corresponding MAC address so that data can be delivered on the local network. Together, these three concepts work in layers: IP handles routing across networks, MAC handles delivery within a network, and ARP connects them. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/ipsec-vs-ssl-vpn@LesiUZyQTRgQErALy5W-v.md b/src/data/roadmaps/network-engineer/content/ipsec-vs-ssl-vpn@LesiUZyQTRgQErALy5W-v.md new file mode 100644 index 000000000..d3ec55b94 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/ipsec-vs-ssl-vpn@LesiUZyQTRgQErALy5W-v.md @@ -0,0 +1,3 @@ +# IPSec vs SSL VPN + +IPSec (Internet Protocol Security) VPNs operate at the network layer, encrypting all IP traffic between two endpoints and are commonly used for site-to-site connections between networks. SSL/TLS VPNs operate at the application layer, typically accessible through a web browser or lightweight client, and are better suited for remote individual user access. The choice between the two depends on the use case: IPSec is generally preferred for permanent network-to-network tunnels, while SSL VPNs offer more flexibility for end-user remote access. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/ipv4-vs-ipv6@wzYaf1wtbo2RQ8JSRawFM.md b/src/data/roadmaps/network-engineer/content/ipv4-vs-ipv6@wzYaf1wtbo2RQ8JSRawFM.md new file mode 100644 index 000000000..9b6052121 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/ipv4-vs-ipv6@wzYaf1wtbo2RQ8JSRawFM.md @@ -0,0 +1,3 @@ +# IPv4 vs IPv6 + +IPv4 is the original version of the Internet Protocol, using 32-bit addresses written in dotted decimal notation (e.g., 192.168.1.1), allowing for about 4.3 billion unique addresses. IPv6 was introduced to solve the problem of IPv4 address exhaustion, using 128-bit addresses written in hexadecimal (e.g., 2001:0db8::1), providing an astronomically larger address space. Beyond address size, IPv6 also introduces improvements in routing efficiency, auto-configuration, and built-in security features. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/lan@6Wfv3THDhldz_9M6Hv1Gr.md b/src/data/roadmaps/network-engineer/content/lan@6Wfv3THDhldz_9M6Hv1Gr.md new file mode 100644 index 000000000..538b8f957 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/lan@6Wfv3THDhldz_9M6Hv1Gr.md @@ -0,0 +1,3 @@ +# LAN + +A LAN, or Local Area Network, is a network that connects devices within a limited geographic area, such as a home, office, or building. LANs typically use Ethernet cables or Wi-Fi to link computers, printers, and other devices, allowing them to share files and resources at high speeds. Because all devices are physically close, LANs offer low latency and high bandwidth compared to larger network types. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/latency@u1nJXjWZekrzyiDvri6-O.md b/src/data/roadmaps/network-engineer/content/latency@u1nJXjWZekrzyiDvri6-O.md new file mode 100644 index 000000000..648d9c2c1 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/latency@u1nJXjWZekrzyiDvri6-O.md @@ -0,0 +1,3 @@ +# Latency + +Latency is the time it takes for a data packet to travel from its source to its destination, usually measured in milliseconds. Low latency means data arrives quickly, which is critical for real-time applications like video calls and online gaming. Latency is influenced by factors such as physical distance, network congestion, and the number of hops between devices. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/least-connections@1Os97-x1qqdLJyKAjICiV.md b/src/data/roadmaps/network-engineer/content/least-connections@1Os97-x1qqdLJyKAjICiV.md new file mode 100644 index 000000000..fb97fe69e --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/least-connections@1Os97-x1qqdLJyKAjICiV.md @@ -0,0 +1,3 @@ +# Least Connections + +The Least Connections algorithm is a load-balancing method that routes each new request to the server with the fewest active connections at that moment. This approach is more adaptive than Round Robin because it accounts for varying request durations and server load. It is particularly useful when requests have significantly different processing times, ensuring that no single server gets backed up while others are idle. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/link-aggregation@h4_EMwTv7j_06MsBhURvg.md b/src/data/roadmaps/network-engineer/content/link-aggregation@h4_EMwTv7j_06MsBhURvg.md new file mode 100644 index 000000000..6e7d939d6 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/link-aggregation@h4_EMwTv7j_06MsBhURvg.md @@ -0,0 +1,3 @@ +# Link Aggregation + +Link aggregation is a technique that combines multiple physical network connections between two devices into a single logical link, increasing bandwidth and providing redundancy. If one physical link fails, the others continue to carry traffic without interruption. It is standardized under IEEE 802.3ad (LACP) and is commonly used between switches, servers, and storage devices to improve both performance and reliability. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/load-balancer@R5dmATbOlYEFce7rQImiw.md b/src/data/roadmaps/network-engineer/content/load-balancer@R5dmATbOlYEFce7rQImiw.md new file mode 100644 index 000000000..d89ce8b63 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/load-balancer@R5dmATbOlYEFce7rQImiw.md @@ -0,0 +1,3 @@ +# Load Balancer + +A load balancer is a device or software that distributes incoming network traffic across multiple servers to prevent any single server from becoming overwhelmed. By spreading the workload, load balancers improve application availability, responsiveness, and fault tolerance. They can operate at Layer 4 (based on IP and TCP/UDP) or Layer 7 (based on application-level data like HTTP headers and URLs). \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/mac-address-tables@Yoj06pntnFzv2NDlr6seC.md b/src/data/roadmaps/network-engineer/content/mac-address-tables@Yoj06pntnFzv2NDlr6seC.md new file mode 100644 index 000000000..8f5fdef52 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/mac-address-tables@Yoj06pntnFzv2NDlr6seC.md @@ -0,0 +1,3 @@ +# MAC Address Tables + +A MAC address table, also called a CAM (Content Addressable Memory) table, is a database maintained by a network switch that maps MAC addresses to the specific ports those devices are connected to. When a frame arrives, the switch looks up the destination MAC address in this table to determine which port to forward the frame to. If the address is not found, the switch floods the frame to all ports until it learns the correct mapping. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/mac-address@6zxS5esVlRNIDrQuZBaHz.md b/src/data/roadmaps/network-engineer/content/mac-address@6zxS5esVlRNIDrQuZBaHz.md new file mode 100644 index 000000000..9490efda9 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/mac-address@6zxS5esVlRNIDrQuZBaHz.md @@ -0,0 +1,3 @@ +# Mac Address + +A MAC address, or Media Access Control address, is a unique hardware identifier assigned to a network interface card (NIC) by its manufacturer. It operates at the Data Link layer and is used to identify devices within the same local network segment. Unlike IP addresses, MAC addresses are typically fixed and do not change as a device moves between networks. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/man@usgE8mpRUSLMRv7d0kXy3.md b/src/data/roadmaps/network-engineer/content/man@usgE8mpRUSLMRv7d0kXy3.md new file mode 100644 index 000000000..2bf548b81 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/man@usgE8mpRUSLMRv7d0kXy3.md @@ -0,0 +1,3 @@ +# MAN + +A MAN, or Metropolitan Area Network, is a network that covers a geographic area roughly the size of a city or a large campus. It is larger than a LAN but smaller than a WAN, often used by organizations or service providers to connect multiple buildings or locations within the same metropolitan region. MANs typically use fiber optic cables or wireless links to achieve high-speed connectivity across the area. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/mobile-networks@nBXPiMyDKkFtD25ReqUEF.md b/src/data/roadmaps/network-engineer/content/mobile-networks@nBXPiMyDKkFtD25ReqUEF.md new file mode 100644 index 000000000..12e626b96 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/mobile-networks@nBXPiMyDKkFtD25ReqUEF.md @@ -0,0 +1,3 @@ +# Mobile Networks + +Mobile networks are wireless communication systems that provide connectivity to devices over large geographic areas through a network of cell towers and base stations. They have evolved through generations, from 2G and 3G through 4G to 5G, each offering faster speeds, lower latency, and greater capacity. Understanding mobile network architecture is increasingly important as more devices rely on cellular connectivity and as 5G enables new enterprise and IoT use cases. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/modems@5aZe1jNCH2cM-8ZCYeI-e.md b/src/data/roadmaps/network-engineer/content/modems@5aZe1jNCH2cM-8ZCYeI-e.md new file mode 100644 index 000000000..2f8a1f5b3 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/modems@5aZe1jNCH2cM-8ZCYeI-e.md @@ -0,0 +1,3 @@ +# Modems + +A modem (modulator-demodulator) is a device that converts digital data from a computer into a format suitable for transmission over a communication medium such as telephone lines or cable, and vice versa. It serves as the bridge between your local network and your Internet Service Provider's infrastructure. Modern modems often include router functionality built in, combining both devices into a single unit. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/mpls@uH-ufJAMyoqDlx7RzYsnX.md b/src/data/roadmaps/network-engineer/content/mpls@uH-ufJAMyoqDlx7RzYsnX.md new file mode 100644 index 000000000..10285c9cb --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/mpls@uH-ufJAMyoqDlx7RzYsnX.md @@ -0,0 +1,3 @@ +# MPLS + +MPLS, or Multiprotocol Label Switching, is a technique for speeding up network traffic by using short labels to direct packets along predetermined paths rather than making complex routing decisions at each hop. When a packet enters an MPLS network, it is assigned a label, and subsequent routers forward it based on that label without needing to inspect the IP header. MPLS is widely used by service providers to manage traffic efficiently and deliver services like VPNs and quality of service guarantees. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/netflow--sflow@sKbTs6q8CBF6_BTDu6xpy.md b/src/data/roadmaps/network-engineer/content/netflow--sflow@sKbTs6q8CBF6_BTDu6xpy.md new file mode 100644 index 000000000..95a8ca904 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/netflow--sflow@sKbTs6q8CBF6_BTDu6xpy.md @@ -0,0 +1,3 @@ +# NetFlow / sFlow + +NetFlow is a Cisco-developed protocol that collects and exports metadata about IP traffic flows passing through a network device, providing visibility into who is communicating with whom, how much data is being exchanged, and what protocols are in use. sFlow is a similar, vendor-neutral sampling-based protocol that works across a broader range of hardware. Both are used for traffic analysis, capacity planning, anomaly detection, and security monitoring without requiring full packet capture. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/network-access@x6gwBUjdcBwqjrSa_WNkp.md b/src/data/roadmaps/network-engineer/content/network-access@x6gwBUjdcBwqjrSa_WNkp.md new file mode 100644 index 000000000..dda44d535 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/network-access@x6gwBUjdcBwqjrSa_WNkp.md @@ -0,0 +1,3 @@ +# Network Access + +The Network Access layer is the lowest layer of the TCP/IP model, combining the functions of the OSI Physical and Data Link layers. It handles how data is physically transmitted over the network medium, including framing, MAC addressing, and hardware-level error detection. Ethernet and Wi-Fi protocols operate at this layer. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/network-attacks@iSXa4nyLa6AQDhFRPz87x.md b/src/data/roadmaps/network-engineer/content/network-attacks@iSXa4nyLa6AQDhFRPz87x.md new file mode 100644 index 000000000..29a4d051e --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/network-attacks@iSXa4nyLa6AQDhFRPz87x.md @@ -0,0 +1,3 @@ +# Network Attacks + +Network attacks are deliberate actions taken by malicious actors to disrupt, intercept, or gain unauthorized access to network resources and data. They can target vulnerabilities in protocols, devices, software, or human behavior to compromise the confidentiality, integrity, or availability of a network. Understanding the types of attacks that exist is the first step in designing defenses and responding effectively when incidents occur. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/network-devices@2b4Bbs-I8k62zOF97Z_uZ.md b/src/data/roadmaps/network-engineer/content/network-devices@2b4Bbs-I8k62zOF97Z_uZ.md new file mode 100644 index 000000000..d350777c3 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/network-devices@2b4Bbs-I8k62zOF97Z_uZ.md @@ -0,0 +1,3 @@ +# Network Devices + +Network devices are the physical hardware components that make up a network and enable communication between connected devices. Each type of device serves a specific function, such as directing traffic, amplifying signals, or connecting different network segments. Understanding what each device does and how they interact is fundamental to designing and troubleshooting any network. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/network@20DK-6sEsl8uy6JJoVgE1.md b/src/data/roadmaps/network-engineer/content/network@20DK-6sEsl8uy6JJoVgE1.md new file mode 100644 index 000000000..c28b1a78c --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/network@20DK-6sEsl8uy6JJoVgE1.md @@ -0,0 +1,3 @@ +# Network + +The Network layer is the third layer of the OSI model, responsible for logical addressing and routing data packets between devices across different networks. It uses IP addresses to determine the best path for data to travel from source to destination. Routers operate at this layer, making forwarding decisions based on routing tables and protocols. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/next-generation@i7aEMN40vQesQbJENQ6gV.md b/src/data/roadmaps/network-engineer/content/next-generation@i7aEMN40vQesQbJENQ6gV.md new file mode 100644 index 000000000..eb3c41c66 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/next-generation@i7aEMN40vQesQbJENQ6gV.md @@ -0,0 +1,3 @@ +# Next-Generation + +A Next-Generation Firewall (NGFW) is an advanced firewall that goes beyond traditional packet filtering and stateful inspection to include deep packet inspection, application awareness, intrusion prevention, and user identity tracking. NGFWs can identify and control traffic based on the specific application being used, regardless of port or protocol, and can detect and block sophisticated threats in real time. They represent the current standard for enterprise perimeter security. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/nmap@dwtbPxxNGQtoStpEd_ydY.md b/src/data/roadmaps/network-engineer/content/nmap@dwtbPxxNGQtoStpEd_ydY.md new file mode 100644 index 000000000..1c7bcb5ca --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/nmap@dwtbPxxNGQtoStpEd_ydY.md @@ -0,0 +1,3 @@ +# Nmap + +Nmap (Network Mapper) is a free, open-source tool used to discover hosts and services on a network by sending packets and analyzing the responses. It can identify active devices, open ports, running services, operating systems, and potential vulnerabilities across a network. Nmap is widely used by network engineers and security professionals for network inventory, auditing, and reconnaissance. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/ntp@b4bKowbNbUcMscWrrT_-k.md b/src/data/roadmaps/network-engineer/content/ntp@b4bKowbNbUcMscWrrT_-k.md new file mode 100644 index 000000000..10ae0d667 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/ntp@b4bKowbNbUcMscWrrT_-k.md @@ -0,0 +1,3 @@ +# NTP + +NTP, or Network Time Protocol, is used to synchronize the clocks of computers and network devices over a network. Accurate timekeeping is essential for logging events, coordinating distributed systems, and ensuring security certificates work correctly. NTP works by having devices query time servers and adjust their local clocks to match, accounting for network delay in the process. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/observability@PHqTXlkAaRPhmRod52aP3.md b/src/data/roadmaps/network-engineer/content/observability@PHqTXlkAaRPhmRod52aP3.md new file mode 100644 index 000000000..13638d1fd --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/observability@PHqTXlkAaRPhmRod52aP3.md @@ -0,0 +1,3 @@ +# Observability + +Network observability refers to the ability to understand the internal state and behavior of a network by collecting and analyzing data from its components, including logs, metrics, traces, and flow records. It goes beyond basic monitoring by providing deep insight into why things are happening, not just what is happening. Good observability enables network engineers to detect issues early, troubleshoot faster, and optimize performance across complex, distributed environments. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/opendns@laCGHS68FdPDeBpC172vo.md b/src/data/roadmaps/network-engineer/content/opendns@laCGHS68FdPDeBpC172vo.md new file mode 100644 index 000000000..eb7ecbf50 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/opendns@laCGHS68FdPDeBpC172vo.md @@ -0,0 +1,3 @@ +# OpenDNS + +OpenDNS is a cloud-based DNS service operated by Cisco that provides fast DNS resolution along with additional security and filtering features. It can block access to malicious websites, phishing domains, and unwanted content categories before a connection is ever established. OpenDNS is commonly used by organizations and families to add a layer of protection at the DNS level without requiring software on individual devices. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/osi-model@pt6RO3SEStG9TJOWpt_8D.md b/src/data/roadmaps/network-engineer/content/osi-model@pt6RO3SEStG9TJOWpt_8D.md new file mode 100644 index 000000000..fe0f8de53 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/osi-model@pt6RO3SEStG9TJOWpt_8D.md @@ -0,0 +1,3 @@ +# OSI Model + +The OSI (Open Systems Interconnection) model is a conceptual framework that standardizes the functions of a network into seven distinct layers, from physical transmission up to application-level communication. It was developed to help different systems and vendors communicate using common standards, making troubleshooting and network design more systematic. Each layer has a specific role and interacts only with the layers directly above and below it. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/ospf@OZICDRrSq-KJNAGTlmwr7.md b/src/data/roadmaps/network-engineer/content/ospf@OZICDRrSq-KJNAGTlmwr7.md new file mode 100644 index 000000000..65d17d798 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/ospf@OZICDRrSq-KJNAGTlmwr7.md @@ -0,0 +1,3 @@ +# OSPF + +OSPF, or Open Shortest Path First, is a link-state interior gateway routing protocol used within a single autonomous system or organization. It works by having each router build a complete map of the network topology and then calculate the shortest path to every destination using Dijkstra's algorithm. OSPF converges quickly after network changes and is widely used in medium to large enterprise networks. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/package@rlUkMwML31YWfLSYLPdaL.md b/src/data/roadmaps/network-engineer/content/package@rlUkMwML31YWfLSYLPdaL.md new file mode 100644 index 000000000..6ab16f405 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/package@rlUkMwML31YWfLSYLPdaL.md @@ -0,0 +1,3 @@ +# Package + +In networking, a package (or packet) is a small chunk of data broken off from a larger message for transmission across a network. Each packet travels independently through the network and is reassembled at the destination. Packets contain both the payload data and header information, such as source and destination addresses, needed to route them correctly. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/packet-filtering@wNwT9OgpslH4YG9BZvQIK.md b/src/data/roadmaps/network-engineer/content/packet-filtering@wNwT9OgpslH4YG9BZvQIK.md new file mode 100644 index 000000000..fc01f3a10 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/packet-filtering@wNwT9OgpslH4YG9BZvQIK.md @@ -0,0 +1,3 @@ +# Packet Filtering + +Packet filtering is the most basic type of firewall technique, where each packet is inspected individually against a set of rules based on attributes like source IP, destination IP, port numbers, and protocol. If a packet matches an allow rule, it passes through; if it matches a deny rule or no rule at all, it is dropped. Packet filtering is fast and lightweight, but provides limited protection since it does not consider the state of the connection or the content of the data. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/packet-prioritization@IOu0hW9FZsLYe-KIaZZ4s.md b/src/data/roadmaps/network-engineer/content/packet-prioritization@IOu0hW9FZsLYe-KIaZZ4s.md new file mode 100644 index 000000000..6d57568f4 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/packet-prioritization@IOu0hW9FZsLYe-KIaZZ4s.md @@ -0,0 +1,3 @@ +# Packet prioritization + +Packet prioritization is the process of classifying network traffic and assigning different levels of importance to different types of packets so that critical traffic is processed and delivered first. Real-time traffic, like VoIP and video conferencing, is given higher priority than background activities like file downloads or software updates. This ensures that time-sensitive applications remain functional even when the network is under heavy load. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/pan@fLXIQLKecjWUvjIWUaF9r.md b/src/data/roadmaps/network-engineer/content/pan@fLXIQLKecjWUvjIWUaF9r.md new file mode 100644 index 000000000..d32581d8b --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/pan@fLXIQLKecjWUvjIWUaF9r.md @@ -0,0 +1,3 @@ +# PAN + +A PAN, or Personal Area Network, is a small network designed for communication between devices in proximity to a single person, typically within a range of a few meters. Examples include connecting a smartphone to wireless earbuds via Bluetooth or linking a laptop to a smartwatch. PANs can be wired (such as USB) or wireless (such as Bluetooth or infrared). \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/peer-to-peer-network@DaJDqRCvGNekZ-e6aDVZj.md b/src/data/roadmaps/network-engineer/content/peer-to-peer-network@DaJDqRCvGNekZ-e6aDVZj.md new file mode 100644 index 000000000..f6a151648 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/peer-to-peer-network@DaJDqRCvGNekZ-e6aDVZj.md @@ -0,0 +1,3 @@ +# Peer-to-Peer Network + +A peer-to-peer (P2P) network is one where each device, or peer, can act as both a client and a server, sharing resources directly with other devices without a central server. This model is simpler and cheaper to set up than a client-server network, making it common in small home networks or applications like file sharing. However, P2P networks can be harder to manage and secure as they grow in size. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/physical@_lqxrKkanbNDimmzcdM1I.md b/src/data/roadmaps/network-engineer/content/physical@_lqxrKkanbNDimmzcdM1I.md new file mode 100644 index 000000000..669bff49f --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/physical@_lqxrKkanbNDimmzcdM1I.md @@ -0,0 +1,3 @@ +# Physical + +The Physical layer is the first and lowest layer of the OSI model, responsible for the actual transmission of raw bits over a physical medium such as copper cables, fiber optics, or radio waves. It defines the electrical, mechanical, and timing specifications for hardware components like network cables, connectors, and network interface cards. Everything at this layer deals with the physical delivery of signals, not their meaning. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/port@TJZ9vsSxQlotKCWQ2HHfS.md b/src/data/roadmaps/network-engineer/content/port@TJZ9vsSxQlotKCWQ2HHfS.md new file mode 100644 index 000000000..10c31c8b2 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/port@TJZ9vsSxQlotKCWQ2HHfS.md @@ -0,0 +1,3 @@ +# Port + +A port is a numerical identifier used to direct network traffic to a specific application or service running on a device. While an IP address identifies the device, the port number identifies which program on that device should handle the incoming data. For example, web traffic typically uses port 80 for HTTP and port 443 for HTTPS. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/presentation@U3sXE8skdwBwCcYQuKyzk.md b/src/data/roadmaps/network-engineer/content/presentation@U3sXE8skdwBwCcYQuKyzk.md new file mode 100644 index 000000000..c4c751e2a --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/presentation@U3sXE8skdwBwCcYQuKyzk.md @@ -0,0 +1,3 @@ +# Presentation + +The Presentation layer is the sixth layer of the OSI model, responsible for translating data between the format used by the application and the format used for network transmission. It handles tasks such as data encryption and decryption, compression, and character encoding. This layer ensures that data sent from one system can be read by another, regardless of differences in internal data representation. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/protocol@9q3EjoReSztEf3wffNDIs.md b/src/data/roadmaps/network-engineer/content/protocol@9q3EjoReSztEf3wffNDIs.md new file mode 100644 index 000000000..59f75394e --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/protocol@9q3EjoReSztEf3wffNDIs.md @@ -0,0 +1,3 @@ +# Protocol + +A protocol is a set of rules that defines how data is formatted, transmitted, and received between devices on a network. Protocols ensure that different systems, regardless of manufacturer or operating system, can predictably communicate with each other. Examples include TCP, IP, HTTP, and DNS, each governing a specific aspect of how network communication works. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/proxy@55_hR5xJzermyLb3lyAvO.md b/src/data/roadmaps/network-engineer/content/proxy@55_hR5xJzermyLb3lyAvO.md new file mode 100644 index 000000000..d6a72009f --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/proxy@55_hR5xJzermyLb3lyAvO.md @@ -0,0 +1,3 @@ +# Proxy + +A proxy firewall operates at the application layer and acts as an intermediary between internal clients and external servers, inspecting the full content of network requests and responses. Instead of allowing direct connections, all traffic is routed through the proxy, which can apply content filtering, authentication, and logging. Because it terminates and re-establishes each connection, a proxy firewall provides deep inspection but can introduce latency. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/public-vs-private-addresses@DJVkJUV6Sx2Ez6t6yCOm7.md b/src/data/roadmaps/network-engineer/content/public-vs-private-addresses@DJVkJUV6Sx2Ez6t6yCOm7.md new file mode 100644 index 000000000..cc718e587 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/public-vs-private-addresses@DJVkJUV6Sx2Ez6t6yCOm7.md @@ -0,0 +1,3 @@ +# Public vs Private Addresses + +Public IP addresses are globally unique addresses assigned by Internet Service Providers and are reachable over the Internet. Private IP addresses are reserved for use within local networks and are not routable on the public Internet (ranges like 192.168.x.x, 10.x.x.x, and 172.16.x.x are commonly used internally). Devices with private addresses access the Internet through a process called NAT (Network Address Translation), which maps multiple private addresses to a single public one. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/qos-quality-of-service@1AWSj4RYLouXC4eJvg2N9.md b/src/data/roadmaps/network-engineer/content/qos-quality-of-service@1AWSj4RYLouXC4eJvg2N9.md new file mode 100644 index 000000000..41a0af1a7 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/qos-quality-of-service@1AWSj4RYLouXC4eJvg2N9.md @@ -0,0 +1,3 @@ +# QoS (Quality of Service) + +QoS, or Quality of Service, refers to a set of techniques used to manage network traffic and ensure that critical applications receive the bandwidth, low latency, and reliability they need. Without QoS, all traffic is treated equally, which can cause voice calls to break up or video to buffer when the network is congested. QoS works by classifying, prioritizing, and managing packets so that high-priority traffic is delivered first. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/quad9@kSUBDvguhusW8qaCK5bbL.md b/src/data/roadmaps/network-engineer/content/quad9@kSUBDvguhusW8qaCK5bbL.md new file mode 100644 index 000000000..1c5f86e11 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/quad9@kSUBDvguhusW8qaCK5bbL.md @@ -0,0 +1,3 @@ +# Quad9 + +Quad9 is a free, public DNS resolver that focuses on security by blocking access to known malicious domains at the DNS level. It uses threat intelligence from multiple cybersecurity partners to identify and block harmful websites before a connection is made, without logging personally identifiable information. Quad9 is operated by a non-profit organization and is accessible at the address 9.9.9.9. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/rip@koRzHVPTKTNmTt8dC-h3m.md b/src/data/roadmaps/network-engineer/content/rip@koRzHVPTKTNmTt8dC-h3m.md new file mode 100644 index 000000000..c1f42534e --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/rip@koRzHVPTKTNmTt8dC-h3m.md @@ -0,0 +1,3 @@ +# RIP + +RIP, or Routing Information Protocol, is one of the oldest dynamic routing protocols, using a distance-vector algorithm to determine the best path based on hop count —the number of routers a packet must pass through to reach its destination. It has a maximum hop count of 15, making it unsuitable for large networks. RIP is simple to configure but has largely been replaced by more efficient protocols like OSPF and EIGRP in modern networks. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/round-robin@uQz1QLVkQtwf8ZeXexEQ1.md b/src/data/roadmaps/network-engineer/content/round-robin@uQz1QLVkQtwf8ZeXexEQ1.md new file mode 100644 index 000000000..6489ac56c --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/round-robin@uQz1QLVkQtwf8ZeXexEQ1.md @@ -0,0 +1,3 @@ +# Round Robin + +Round Robin is one of the simplest load balancing algorithms, where incoming requests are distributed sequentially to each server in the pool, one after another, cycling back to the first when the end is reached. It assumes all servers have roughly equal capacity and is easy to implement. Round Robin works well when the servers are similar in performance and the requests are similar in complexity. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/routers@s_y5I8OZAsmFqj3zier2B.md b/src/data/roadmaps/network-engineer/content/routers@s_y5I8OZAsmFqj3zier2B.md new file mode 100644 index 000000000..d6ed1d81c --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/routers@s_y5I8OZAsmFqj3zier2B.md @@ -0,0 +1,3 @@ +# Routers + +A router is a network device that forwards data packets between different networks, directing traffic based on IP addresses. It determines the best path for data to travel from source to destination, making routing decisions using routing tables and protocols. Routers are what connect your home or office network to the Internet and are essential for communication between separate networks. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/routing@rbm4cELHUgaL_Gl9uuLq1.md b/src/data/roadmaps/network-engineer/content/routing@rbm4cELHUgaL_Gl9uuLq1.md new file mode 100644 index 000000000..53989af22 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/routing@rbm4cELHUgaL_Gl9uuLq1.md @@ -0,0 +1,3 @@ +# Routing + +Routing is the process of selecting a path for traffic to travel across one or more networks from source to destination. Routers perform this function by examining the destination IP address of each packet and consulting a routing table to determine where to forward it next. Routing can be done statically, where paths are manually configured, or dynamically, where routers automatically discover and update paths using routing protocols. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/san@9tkaAhzPhiiGUoL2LqbPb.md b/src/data/roadmaps/network-engineer/content/san@9tkaAhzPhiiGUoL2LqbPb.md new file mode 100644 index 000000000..8e95f99d0 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/san@9tkaAhzPhiiGUoL2LqbPb.md @@ -0,0 +1,3 @@ +# SAN + +A SAN, or Storage Area Network, is a specialized high-speed network that provides block-level access to shared storage devices such as disk arrays and tape libraries. Unlike a regular network where files are shared, a SAN makes storage appear as locally attached to the servers that use it, enabling fast and reliable data access. SANs are commonly used in enterprise environments to support databases, virtualization, and backup systems. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/server@huzbiZu77aeCBVU40C429.md b/src/data/roadmaps/network-engineer/content/server@huzbiZu77aeCBVU40C429.md new file mode 100644 index 000000000..82304fabe --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/server@huzbiZu77aeCBVU40C429.md @@ -0,0 +1,3 @@ +# Server + +A server is a computer or software system that listens for requests from clients and responds by providing resources, data, or services. Servers can host websites, store files, manage emails, or run applications that many users access simultaneously. They are typically designed to be always available, handling multiple client connections at the same time. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/session@q6dPa3Nqjw8cmZApzpcZK.md b/src/data/roadmaps/network-engineer/content/session@q6dPa3Nqjw8cmZApzpcZK.md new file mode 100644 index 000000000..ee1ea93d3 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/session@q6dPa3Nqjw8cmZApzpcZK.md @@ -0,0 +1,3 @@ +# Session + +The Session layer is the fifth layer of the OSI model, responsible for establishing, managing, and terminating communication sessions between applications. It handles synchronization and dialog control, ensuring that data exchanges are organized and that sessions can be paused and resumed if needed. Examples of protocols operating at this layer include NetBIOS and RPC. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/site-to-site-vs-remote-access@e0mUmniS-GT8DccJq95VB.md b/src/data/roadmaps/network-engineer/content/site-to-site-vs-remote-access@e0mUmniS-GT8DccJq95VB.md new file mode 100644 index 000000000..b2f583da2 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/site-to-site-vs-remote-access@e0mUmniS-GT8DccJq95VB.md @@ -0,0 +1,3 @@ +# Site-to-Site vs Remote Access + +Site-to-site VPNs connect two entire networks together — such as a branch office to a headquarters — over an encrypted tunnel, allowing devices on both networks to communicate as if they were on the same LAN. Remote access VPNs allow individual users to securely connect to a corporate network from any location, typically using a VPN client on their device. Both serve different purposes and are often deployed together in enterprise environments to address different connectivity needs. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/smtp--imap@CxC1hOOue_2aNHs1KdkAV.md b/src/data/roadmaps/network-engineer/content/smtp--imap@CxC1hOOue_2aNHs1KdkAV.md new file mode 100644 index 000000000..dacf30bfe --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/smtp--imap@CxC1hOOue_2aNHs1KdkAV.md @@ -0,0 +1,3 @@ +# SMTP / IMAP + +SMTP (Simple Mail Transfer Protocol) is the protocol used to send emails from a client to a server or between mail servers. IMAP (Internet Message Access Protocol) is used by email clients to retrieve and manage messages stored on a mail server, allowing access from multiple devices while keeping messages synchronized. Together, these protocols handle the sending and receiving sides of email communication. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/snmp@KqxGa5MoKuprDLF9OY988.md b/src/data/roadmaps/network-engineer/content/snmp@KqxGa5MoKuprDLF9OY988.md new file mode 100644 index 000000000..9456b9a2e --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/snmp@KqxGa5MoKuprDLF9OY988.md @@ -0,0 +1,3 @@ +# SNMP + +SNMP, or Simple Network Management Protocol, is a widely used protocol for monitoring and managing network devices such as routers, switches, servers, and printers. It allows a central management system to query devices for performance data — like CPU usage, interface statistics, and error counts — and can also receive unsolicited alerts called traps when certain conditions occur. SNMP is a foundational tool in network operations centers (NOCs) for maintaining visibility across large infrastructure. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/sntp@GhurQiBhFWlYQ7slPP8QU.md b/src/data/roadmaps/network-engineer/content/sntp@GhurQiBhFWlYQ7slPP8QU.md new file mode 100644 index 000000000..0afe92395 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/sntp@GhurQiBhFWlYQ7slPP8QU.md @@ -0,0 +1,3 @@ +# SNTP + +SNTP, or Simple Network Time Protocol, is a simplified version of NTP used to synchronize device clocks over a network. It is less precise than full NTP but requires fewer resources, making it suitable for devices that do not need highly accurate timekeeping. SNTP is commonly used in embedded systems, IoT devices, and environments where simplicity is prioritized over precision. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/socket@jvMvCRqstz3Z7cKYv6MZX.md b/src/data/roadmaps/network-engineer/content/socket@jvMvCRqstz3Z7cKYv6MZX.md new file mode 100644 index 000000000..30ddd3f58 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/socket@jvMvCRqstz3Z7cKYv6MZX.md @@ -0,0 +1,3 @@ +# Socket + +A socket is the combination of an IP address and a port number, forming a unique endpoint for network communication. When two devices establish a connection, each end uses a socket to send and receive data, creating a two-way communication channel. Sockets are the fundamental abstraction used by applications to interact with the network. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/ssh@D-4ZVP3RqLuNDzXamRlv3.md b/src/data/roadmaps/network-engineer/content/ssh@D-4ZVP3RqLuNDzXamRlv3.md new file mode 100644 index 000000000..db01f6e55 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/ssh@D-4ZVP3RqLuNDzXamRlv3.md @@ -0,0 +1,3 @@ +# SSH + +SSH, or Secure Shell, is a network protocol that provides a secure, encrypted channel for remotely accessing and managing devices over an unsecured network. It replaces older, insecure protocols like Telnet by encrypting all communication between the client and the server. Network engineers use SSH extensively to configure routers, switches, and servers from a remote location. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/ssl--tls@ZtMTMBQkOWoM-su3V-T8Z.md b/src/data/roadmaps/network-engineer/content/ssl--tls@ZtMTMBQkOWoM-su3V-T8Z.md new file mode 100644 index 000000000..a11f735ab --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/ssl--tls@ZtMTMBQkOWoM-su3V-T8Z.md @@ -0,0 +1,3 @@ +# SSL / TLS + +SSL (Secure Sockets Layer) and its successor TLS (Transport Layer Security) are cryptographic protocols designed to provide secure communication over a network. They work by encrypting the data exchanged between a client and a server, verifying the identity of the parties involved through digital certificates. TLS is the modern standard and is used to secure HTTPS connections, email, and many other internet services. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/stateful-inspection@jjdqsmXHNt78cgVDr_gC_.md b/src/data/roadmaps/network-engineer/content/stateful-inspection@jjdqsmXHNt78cgVDr_gC_.md new file mode 100644 index 000000000..9edaf6304 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/stateful-inspection@jjdqsmXHNt78cgVDr_gC_.md @@ -0,0 +1,3 @@ +# Stateful Inspection + +Stateful inspection, also known as dynamic packet filtering, is a firewall technique that tracks the state of active network connections and makes filtering decisions based on context, not just individual packets. By maintaining a state table of established connections, a stateful firewall can allow response packets that belong to a legitimate session while blocking unsolicited incoming traffic. This provides significantly better security than simple packet filtering without sacrificing too much performance. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/static-vs-dynamic-routing@n3fdYKpMFSkcasrqokPO8.md b/src/data/roadmaps/network-engineer/content/static-vs-dynamic-routing@n3fdYKpMFSkcasrqokPO8.md new file mode 100644 index 000000000..4229fcb57 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/static-vs-dynamic-routing@n3fdYKpMFSkcasrqokPO8.md @@ -0,0 +1,3 @@ +# Static vs Dynamic Routing + +Static routing involves manually configuring fixed routes in a router's routing table, which do not change unless an administrator updates them. It is simple and predictable, but does not adapt automatically to network changes or failures. Dynamic routing uses routing protocols that allow routers to automatically discover routes, share information with neighboring routers, and adapt to topology changes in real time. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/stp@DM50xKwBoRZa0_JdQi07v.md b/src/data/roadmaps/network-engineer/content/stp@DM50xKwBoRZa0_JdQi07v.md new file mode 100644 index 000000000..8e997f586 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/stp@DM50xKwBoRZa0_JdQi07v.md @@ -0,0 +1,3 @@ +# STP + +STP, or Spanning Tree Protocol, is a network protocol that prevents loops in Ethernet networks by creating a logical tree topology from a physically redundant network. Without STP, multiple paths between switches could cause broadcast storms that would bring a network down. STP works by electing a root bridge and blocking redundant paths, re-enabling them only if the primary path fails. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/subnet-masks@KpifvB6Yn9u32TRBX9hMs.md b/src/data/roadmaps/network-engineer/content/subnet-masks@KpifvB6Yn9u32TRBX9hMs.md new file mode 100644 index 000000000..7822738c6 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/subnet-masks@KpifvB6Yn9u32TRBX9hMs.md @@ -0,0 +1,3 @@ +# Subnet Masks + +A subnet mask is a 32-bit number used alongside an IP address to determine which portion of the address identifies the network and which portion identifies the individual host. It works by applying a bitwise AND operation with the IP address to extract the network address. For example, a subnet mask of 255.255.255.0 means the first three octets represent the network and the last octet identifies hosts within that network. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/subnetting@d93bl-7gSB8lu43BQlqvY.md b/src/data/roadmaps/network-engineer/content/subnetting@d93bl-7gSB8lu43BQlqvY.md new file mode 100644 index 000000000..cb479b545 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/subnetting@d93bl-7gSB8lu43BQlqvY.md @@ -0,0 +1,3 @@ +# Subnetting + +Subnetting is the process of dividing a large network into smaller, more manageable sub-networks called subnets. It helps improve network performance by reducing broadcast traffic and allows organizations to organize their network logically, such as separating departments or locations. Subnetting works by borrowing bits from the host portion of an IP address to create a subnet identifier, controlled by the subnet mask. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/supernetting@zX1S1ZXm8vTcyXhRvYZGv.md b/src/data/roadmaps/network-engineer/content/supernetting@zX1S1ZXm8vTcyXhRvYZGv.md new file mode 100644 index 000000000..cf0f2ff4b --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/supernetting@zX1S1ZXm8vTcyXhRvYZGv.md @@ -0,0 +1,3 @@ +# Supernetting + +Supernetting, also known as route aggregation or summarization, is the process of combining multiple smaller network routes into a single, larger route advertisement. This reduces the size of routing tables and simplifies routing by representing several contiguous subnets as one summary route. It is commonly used in large-scale networks and by ISPs to keep routing tables manageable. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/switches@4iXennqlVoVVKcV1vCUmP.md b/src/data/roadmaps/network-engineer/content/switches@4iXennqlVoVVKcV1vCUmP.md new file mode 100644 index 000000000..75e0cf5f3 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/switches@4iXennqlVoVVKcV1vCUmP.md @@ -0,0 +1,3 @@ +# Switches + +A switch is a network device that connects multiple devices within the same local network and forwards data based on MAC addresses. Unlike a hub, a switch sends data only to the specific device it is intended for, making communication more efficient and reducing unnecessary network traffic. Managed switches offer additional features like VLANs, port security, and traffic monitoring. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/switching@TLfYI5HUUJBj1MNywlT3Z.md b/src/data/roadmaps/network-engineer/content/switching@TLfYI5HUUJBj1MNywlT3Z.md new file mode 100644 index 000000000..d283e2abf --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/switching@TLfYI5HUUJBj1MNywlT3Z.md @@ -0,0 +1,3 @@ +# Switching + +Switching is the process of forwarding data frames within a local network based on MAC addresses. A network switch receives incoming frames and sends them only to the port connected to the intended destination device, unlike a hub which broadcasts to all ports. Switching forms the foundation of modern LAN design and can be enhanced with features like VLANs, STP, and link aggregation. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/tcpip-model@JL4oU_MaY-4QRWKQjMBZb.md b/src/data/roadmaps/network-engineer/content/tcpip-model@JL4oU_MaY-4QRWKQjMBZb.md new file mode 100644 index 000000000..64ea03992 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/tcpip-model@JL4oU_MaY-4QRWKQjMBZb.md @@ -0,0 +1,3 @@ +# TCP/IP Model + +The TCP/IP model is a practical, four-layer framework that describes how data is transmitted over the Internet and most modern networks. It was developed by the U.S. Department of Defense and serves as the foundation for Internet communication. Unlike the OSI model's seven layers, the TCP/IP model consolidates functions into four layers: Network Access, Internet, Transport, and Application. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/throughput@BBS99mZfQqfXDEnBlZy1B.md b/src/data/roadmaps/network-engineer/content/throughput@BBS99mZfQqfXDEnBlZy1B.md new file mode 100644 index 000000000..cabaf2a4b --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/throughput@BBS99mZfQqfXDEnBlZy1B.md @@ -0,0 +1,3 @@ +# Throughput + +Throughput is the actual amount of data successfully transferred over a network in a given period of time, as opposed to the theoretical maximum that bandwidth represents. While bandwidth is the capacity of a network link, throughput reflects real-world performance after accounting for packet loss, latency, and protocol overhead. It is also measured in bits per second. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/traffic-shaping@OoeM99CKlStR1qzyCv1GZ.md b/src/data/roadmaps/network-engineer/content/traffic-shaping@OoeM99CKlStR1qzyCv1GZ.md new file mode 100644 index 000000000..6f1e62f23 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/traffic-shaping@OoeM99CKlStR1qzyCv1GZ.md @@ -0,0 +1,3 @@ +# Traffic shaping + +Traffic shaping is a QoS technique used to control the rate at which data is transmitted on a network, smoothing out bursts and enforcing bandwidth limits for specific types of traffic. By delaying or queuing packets that exceed a defined rate, traffic shaping ensures that no single application or user monopolizes network resources. It is commonly used by ISPs and enterprises to manage congestion and maintain consistent performance across the network. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/transmission-media-types@DjlBAH42q4wSa5PUFSbB5.md b/src/data/roadmaps/network-engineer/content/transmission-media-types@DjlBAH42q4wSa5PUFSbB5.md new file mode 100644 index 000000000..dfcd816eb --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/transmission-media-types@DjlBAH42q4wSa5PUFSbB5.md @@ -0,0 +1,3 @@ +# Transmission Media Types + +Transmission media refers to the physical or wireless channels through which data travels between devices. Wired media includes twisted pair cables (like Ethernet), coaxial cables, and fiber optic cables, each with different speeds, ranges, and interference characteristics. Wireless media uses radio waves, microwaves, or infrared signals to transmit data without physical connections. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/transport@Llr9kp0Oyyj2uZ9qNHCVL.md b/src/data/roadmaps/network-engineer/content/transport@Llr9kp0Oyyj2uZ9qNHCVL.md new file mode 100644 index 000000000..b0b13e859 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/transport@Llr9kp0Oyyj2uZ9qNHCVL.md @@ -0,0 +1,3 @@ +# Transport + +The Transport layer is the fourth layer of the OSI model, responsible for end-to-end communication, data flow control, and error recovery between applications on different hosts. It breaks data into segments, ensures they are delivered reliably and in order, and manages retransmission if packets are lost. The two main protocols at this layer are TCP, which provides reliable delivery, and UDP, which prioritizes speed over reliability. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/transport@r6i0Wob3RNJrGdEnsZcQ-.md b/src/data/roadmaps/network-engineer/content/transport@r6i0Wob3RNJrGdEnsZcQ-.md new file mode 100644 index 000000000..f2f0ed50c --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/transport@r6i0Wob3RNJrGdEnsZcQ-.md @@ -0,0 +1,3 @@ +# Transport + +The Transport layer of the TCP/IP model is responsible for end-to-end communication between applications on different hosts. It uses TCP for reliable, ordered delivery and UDP for faster, connectionless communication where some data loss is acceptable. This layer manages segmentation, flow control, and error handling to ensure data reaches the correct application. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/vlans@x0bAdjSBNfZ4gm1CwnPBK.md b/src/data/roadmaps/network-engineer/content/vlans@x0bAdjSBNfZ4gm1CwnPBK.md new file mode 100644 index 000000000..d93aa730a --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/vlans@x0bAdjSBNfZ4gm1CwnPBK.md @@ -0,0 +1,3 @@ +# VLANs + +A VLAN, or Virtual Local Area Network, is a logical subdivision of a physical network that groups devices together regardless of their physical location. VLANs allow network administrators to segment traffic, improve security, and reduce broadcast domains without needing separate physical switches. Devices in different VLANs cannot communicate directly without going through a router or a Layer 3 switch. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/vlsm@tXjRU0HJ2d9RWxuOQ79wH.md b/src/data/roadmaps/network-engineer/content/vlsm@tXjRU0HJ2d9RWxuOQ79wH.md new file mode 100644 index 000000000..fd010b392 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/vlsm@tXjRU0HJ2d9RWxuOQ79wH.md @@ -0,0 +1,3 @@ +# VLSM + +VLSM, or Variable Length Subnet Masking, is a technique that allows a network to be divided into subnets of different sizes by using different subnet masks within the same network. Unlike fixed-length subnetting, where all subnets are the same size, VLSM lets you allocate address space more efficiently based on the actual needs of each subnet. This is especially useful for conserving IP addresses in complex network designs with varying host requirements. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/vpn@b2HXcIkkjJB8WhHbrVesk.md b/src/data/roadmaps/network-engineer/content/vpn@b2HXcIkkjJB8WhHbrVesk.md new file mode 100644 index 000000000..6649de0da --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/vpn@b2HXcIkkjJB8WhHbrVesk.md @@ -0,0 +1,3 @@ +# VPN + +A VPN, or Virtual Private Network, creates an encrypted tunnel between a device and a remote network over the public Internet, allowing secure communication as if the device were directly connected to that network. Organizations use VPNs to let remote employees securely access internal resources, while individuals use them for privacy and to bypass geographic content restrictions. VPNs mask the user's IP address and encrypt all traffic passing through the tunnel. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/vpns@WHYQSWWe4mKUl7OC9thyF.md b/src/data/roadmaps/network-engineer/content/vpns@WHYQSWWe4mKUl7OC9thyF.md new file mode 100644 index 000000000..9eb611798 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/vpns@WHYQSWWe4mKUl7OC9thyF.md @@ -0,0 +1,3 @@ +# VPNs + +A VPN, or Virtual Private Network, is a technology that creates an encrypted, secure tunnel between a device and a remote network or server over the public Internet. It allows users to access private network resources securely from remote locations and hides their traffic from potential eavesdroppers. VPNs are used by organizations for secure remote access and site-to-site connectivity, as well as by individuals for privacy and anonymity online. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/wan@1xOaztV7JJaXK9B6Wa4YQ.md b/src/data/roadmaps/network-engineer/content/wan@1xOaztV7JJaXK9B6Wa4YQ.md new file mode 100644 index 000000000..6523a830a --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/wan@1xOaztV7JJaXK9B6Wa4YQ.md @@ -0,0 +1,3 @@ +# WAN + +A WAN, or Wide Area Network, is a network that spans a large geographic area, often connecting multiple LANs across cities, countries, or continents. The Internet itself is the largest example of a WAN. Organizations use WANs to link their branch offices and data centers together, often leasing connections from telecommunications providers to do so. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/web-application@xmkSedJJIDwrys8HzDD-j.md b/src/data/roadmaps/network-engineer/content/web-application@xmkSedJJIDwrys8HzDD-j.md new file mode 100644 index 000000000..ae23f4c4e --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/web-application@xmkSedJJIDwrys8HzDD-j.md @@ -0,0 +1,3 @@ +# Web Application + +A Web Application Firewall (WAF) is a specialized security tool designed to filter, monitor, and block HTTP/HTTPS traffic to and from web applications. It protects against common web-based attacks such as SQL injection, cross-site scripting (XSS), and cross-site request forgery (CSRF) by inspecting application-layer traffic against a set of rules or policies. WAFs can be deployed as hardware, software, or cloud services and are an essential layer of defense for any publicly accessible web application. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/what-are-networks@0BPBSnyYnEAScnqZ8q5ZX.md b/src/data/roadmaps/network-engineer/content/what-are-networks@0BPBSnyYnEAScnqZ8q5ZX.md new file mode 100644 index 000000000..5ee116af9 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/what-are-networks@0BPBSnyYnEAScnqZ8q5ZX.md @@ -0,0 +1,3 @@ +# What are Networks? + +A network is a collection of two or more devices connected to share resources and communicate. Networks can be as small as two computers linked in a home office or as large as the global infrastructure of the Internet. They form the backbone of modern digital communication, enabling everything from file sharing and printing to video streaming and cloud computing. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/wifi-standards@Cahf4Y8A0W-EHeeU4dTej.md b/src/data/roadmaps/network-engineer/content/wifi-standards@Cahf4Y8A0W-EHeeU4dTej.md new file mode 100644 index 000000000..2f6d11f4b --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/wifi-standards@Cahf4Y8A0W-EHeeU4dTej.md @@ -0,0 +1,3 @@ +# WiFi Standards + +Wi-Fi standards are a series of specifications developed by the IEEE under the 802.11 family that define how wireless networks operate. Each generation, from 802.11b and 802.11g through to 802.11ac (Wi-Fi 5) and 802.11ax (Wi-Fi 6), brings improvements in speed, range, efficiency, and the ability to handle more simultaneous connections. Understanding the differences between standards helps in selecting the right hardware for a given environment. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/wireless-networking@RCUgWXsit4Jcma9UNBd2c.md b/src/data/roadmaps/network-engineer/content/wireless-networking@RCUgWXsit4Jcma9UNBd2c.md new file mode 100644 index 000000000..a001341d4 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/wireless-networking@RCUgWXsit4Jcma9UNBd2c.md @@ -0,0 +1,3 @@ +# Wireless Networking + +Wireless networking refers to the technology that allows devices to connect to a network and communicate without physical cables, using radio frequency signals instead. It encompasses standards like Wi-Fi, Bluetooth, and cellular networks, each suited to different ranges and use cases. Wireless networks introduce unique considerations around signal strength, interference, frequency bands, and security that wired networks do not face. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/wireless-security@MThbykuwPtbDeskypaD7I.md b/src/data/roadmaps/network-engineer/content/wireless-security@MThbykuwPtbDeskypaD7I.md new file mode 100644 index 000000000..0f24d269f --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/wireless-security@MThbykuwPtbDeskypaD7I.md @@ -0,0 +1,3 @@ +# Wireless Security + +Wireless security refers to the measures taken to protect wireless networks from unauthorized access, eavesdropping, and attacks. Because wireless signals travel through the air and can be intercepted by anyone within range, securing Wi-Fi networks requires encryption, strong authentication, and proper configuration. Key considerations include choosing strong encryption protocols, using strong passwords, and monitoring for rogue access points. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/wireshark@Ly43qxaO0RsKSy-_VuIBx.md b/src/data/roadmaps/network-engineer/content/wireshark@Ly43qxaO0RsKSy-_VuIBx.md new file mode 100644 index 000000000..e454bdd24 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/wireshark@Ly43qxaO0RsKSy-_VuIBx.md @@ -0,0 +1,3 @@ +# Wireshark + +Wireshark is an open-source network protocol analyzer that captures and displays the data traveling across a network in real time. Engineers use it to inspect individual packets, decode protocols, diagnose connectivity problems, and investigate security incidents at a granular level. It supports hundreds of protocols and is one of the most widely used tools for deep network troubleshooting and analysis. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/wlan@D_zZAYVkxB_SLTCuhqkZY.md b/src/data/roadmaps/network-engineer/content/wlan@D_zZAYVkxB_SLTCuhqkZY.md new file mode 100644 index 000000000..2ec7c534b --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/wlan@D_zZAYVkxB_SLTCuhqkZY.md @@ -0,0 +1,3 @@ +# WLAN + +A WLAN, or Wireless Local Area Network, is a type of LAN that uses wireless radio signals instead of cables to connect devices. It is the technology behind Wi-Fi networks found in homes, offices, and public spaces. WLANs offer the convenience of mobility within the coverage area, though they can be more susceptible to interference and security risks than wired networks. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/wpa-vs-wps@_J0L4Ir0pxXPVeW7x68dv.md b/src/data/roadmaps/network-engineer/content/wpa-vs-wps@_J0L4Ir0pxXPVeW7x68dv.md new file mode 100644 index 000000000..422e1481f --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/wpa-vs-wps@_J0L4Ir0pxXPVeW7x68dv.md @@ -0,0 +1,3 @@ +# WPA vs WPS + +WPA (Wi-Fi Protected Access) is a security protocol designed to protect wireless networks through encryption and authentication, with WPA2 and WPA3 being the current standards offering strong AES-based encryption. WPS (Wi-Fi Protected Setup) is a feature designed to simplify the process of connecting devices to a Wi-Fi network, typically using a PIN or button press. However, WPS has well-known security vulnerabilities (particularly the PIN method) and is generally recommended to be disabled on network equipment. \ No newline at end of file diff --git a/src/data/roadmaps/network-engineer/content/zero-trust-architecture@qW27P1HWMCtVkLgVHmU7z.md b/src/data/roadmaps/network-engineer/content/zero-trust-architecture@qW27P1HWMCtVkLgVHmU7z.md new file mode 100644 index 000000000..b12cb2bb5 --- /dev/null +++ b/src/data/roadmaps/network-engineer/content/zero-trust-architecture@qW27P1HWMCtVkLgVHmU7z.md @@ -0,0 +1,3 @@ +# Zero Trust Architecture + +Zero Trust is a security model based on the principle of "never trust, always verify" — meaning no user, device, or network segment is trusted by default, even if they are inside the corporate network. Every access request must be authenticated, authorized, and continuously validated regardless of where it originates. Zero Trust architecture replaces the traditional perimeter-based security model and is increasingly adopted as networks become more distributed and cloud-based. \ No newline at end of file