# routers Published articles for routers. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## RFC 10005: BGP Community for link capacity DevFeed: [RFC 10005: BGP Community for link capacity]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-01T13:31:00Z Content type: article Language: en Sources: [Justin Wilson (j2sw)]() Topics: [BGP](), [standard](), [Load Balancing](), [Network]() Tags: [bgp](), [capacity](), [internet](), [load-balancing](), [network](), [network-operations](), [rfc](), [rfc-10005](), [route](), [routers](), [routing](), [standard](), [traffic]() ### AI overview RFC 10005 defines a BGP extended community for carrying link bandwidth information in routes. When multiple BGP paths are eligible, routers can use the value to weight traffic according to link capacity, while normal best-path policy still determines route eligibility. The RFC is currently a draft. ### Source excerpt RFC 10005 defines a BGP extended community that lets a router attach link bandwidth information to a route. Another router can use that value when it spreads traffic across multiple BGP paths. RFC 10005 matters because links are not always of the same capacity. This RFC provides routers with a standard way to carry bandwidth ... Read more The post RFC 10005: BGP Community for link capacity appeared first on Justin Wilson (j2sw). ## George Washington, the Delaware, and Direct Routes DevFeed: [George Washington, the Delaware, and Direct Routes]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-30T16:15:53Z Content type: opinion Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Network design](), [Networks](), [BGP](), [Network]() Tags: [bgp](), [blog](), [fd-ix](), [internet-architecture](), [ixp](), [network-design](), [network-peering](), [networks](), [peering](), [route](), [routers](), [routing](), [traffic](), [transit]() ### AI overview This commentary compares George Washington's direct route across the Delaware with network peering. It argues that direct connections between networks can reduce transit dependencies, router hops, and latency compared with longer BGP-selected transit paths. ### Source excerpt I originally posted this over on the FD-IX Bloghttps://blog.fd-ix.com/george-washington-the-delaware-and-direct-routes/ When George Washington crossed the Delaware River on Christmas night in 1776, the goal was simple. Reach the objective by the most effective path while avoiding unnecessary delays and giving the opposing force as little warning as possible. The crossing was risky, but it created a ... Read more The post George Washington, the Delaware, and Direct Routes appeared first on Justin Wilson (j2sw). ## Telegram prefixes hijack by Rcom AS18101 DevFeed: [Telegram prefixes hijack by Rcom AS18101]() Original publisher: [Read original article]() Published: 2026-06-16T19:44:03Z Content type: opinion Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [BGP](), [networking](), [Routing (disambiguation)]() Tags: [airtel](), [as15412](), [as18101](), [as4755](), [bgp](), [india](), [outage](), [rcom](), [ripe-ris](), [routers](), [routing](), [rpki](), [telegram](), [traffic]() ### AI overview The article examines Rcom AS18101's apparent BGP hijacking of Telegram prefixes during Telegram's blocking in India. It confirms that Rcom originated at least one Telegram prefix and argues that the incident was more likely an accidental configuration error than intentional sabotage, while noting that the impact varied by upstream connectivity. ### Source excerpt The last few hours were quite noisy with a lot of discussion around Telegram block and Rcom's hijack of Telegram prefixes. For those who may not know, Telegram has been blocked in India till 22 June 2026 (news here). The justification has been to avoid paper leak over the telegram. Anyways, I am not going into whether the block is good or bad as it can be part of an endless discussion depending on how one views it. Maybe some separate time but let's look at the BGP routing side of things. ISPs went for blocking it in all possible ways - from the usual DNS layer to block resolution of Telegram to also blackhole its prefixes. Telegram is a special case as they have their own ASN, IP prefixes etc making it easy to block them at the routing layer directly. I saw this on Airtel, where traffic seems to be dropping at their routers. mtr -wby0 -4 web.telegram.org Start: 2026-06-17T01:20:46+0530 HOST: desktop Loss% Snt Last Avg Best Wrst StDev 1. AS??? _gateway (172.16.0.1) 0.0% 10 0.2 0.2 0.2 0.2 0.0 2. AS??? 10.240.9.204 0.0% 10 4.6 7.4 4.2 25.7 6.5 3. AS??? 172.31.0.154 0.0% 10 8.1 13.5 6.4 26.4 6.2 4. AS9498 169.168.18.125.dhcp.anaronline.net (125.18.168.169) 0.0% 10 5.2 6.8 4.9 13.6 2.6 5. AS??? ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 At 11:58 PM - Telegram CEO Pavel Durov tweeted and accused Reliance (technically Rcom and not Jio) for outage of Telegram outside of India by BGP hijacking. Indian telecom Reliance is sabotaging access to Telegram for millions of users OUTSIDE India (including the UAE) via a rogue method called BGP hijacking. The sabotage seems intentional, as Reliance has ignored multiple reports. This may be part of a competitive war, as... -- Pavel Durov (@durov) June 16, 2026 Technically it's true that Rcom AS18101 has hijacked Telegram's prefixes. Take e.g 91.105.192.0/23 - AS18101 started originating this prefix at 16:14:19 GMT / 21:44:19 IST on 16 June as visible from many RIPE RIS collectors including RIPE RIS RRC01 in London. It's bad and they should not ha ## Who can light fibre in India? DevFeed: [Who can light fibre in India?]() Original publisher: [Read original article]() Published: 2026-02-21T20:49:05Z Content type: article Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [Internet](), [Cloud](), [hosting](), [datacenter]() Tags: [backhaul](), [cloud](), [connectivity](), [datacenter](), [hosting](), [india](), [infrastructure](), [mpls](), [regulatory](), [routers](), [vlan]() ### AI overview The article discusses Indian telecom licensing rules for deploying, lighting, and reselling fibre outside a building. It explains that IP-1 providers may lease passive dark-fibre infrastructure but may not light it, while appropriately licensed ISPs may light fibre for end-user internet access and their own backhaul, not point-to-point connectivity. ### Source excerpt Friend and his two homes... Recently, a friend of mine mentioned his plan to procure dark fibre to connect two of his homes. His idea was straightforward - get LCO to give a dark strand between both homes and run Bidi optics over it. I ended up telling him that while his idea is technically fine, as modern optics can easily cover that sort of distance, it would be illegal as per Indian telecom laws! It wasn't just him, but numerous content players, hosting companies, and Cloud players find it a bit odd when they find this out. In this post, I will document what is allowed and what is not allowed. Advance warning: I am a technical person & do not know much about regulatory. Whatever I am sharing here is what I have learned from my friends who have expertise in the subject. Indian telecom rules are overly complex and can have a different set of interpretations, and often go into the grey area. I welcome readers to share feedback if they are aware of something which isn't correct as per the regulation. With that warning out of the way, I will proceed with the post. Understanding licensing In India, when fibre is going outside of a given building, one needs to have a license to light it. In fact, not just "lighting up a dark fibre" but to deploy and resell dark fibre, one needs a license (IP-1). Infrastructure Provider Category 1 (or IP-1) is considered an easy license which can be used to sell passive assets such as dark fibre, ducts, towers, etc. Active infra i.e lighting up fibre, is not allowed under this license, and it's expected that an IP-1 holder leases their dark fibre only to a license holder who is authorised to light the fibre. Within a building, campus, datacenter, home etc one can deploy a light fibre but as soon as it goes outside of that it becomes a bit of a grey area depending on the use case. An Internet Service Provider (ISP) holding an ISP license or Unified License with ISP authorisation can light fibre but only for two specific purposes: Offering i ## PwnAgent: A One-Click WAN-side RCE in Netgear RAX Routers with CVE-2023-24749 DevFeed: [PwnAgent: A One-Click WAN-side RCE in Netgear RAX Routers with CVE-2023-24749]() Original publisher: [Read original article]() Published: 2023-02-25T00:00:00Z Content type: article Language: en Sources: [mahaloz.re]() Topics: [bug](), [Exploit](), [Hacking](), [nginx](), [Logging]() Tags: [bug-hunting](), [cve](), [exploit](), [firmware](), [hacking](), [nginx](), [pwn2own](), [rce](), [routers]() ### AI overview A technical breakdown of CVE-2023-24749, a remotely accessible command-injection vulnerability in some Netgear RAX routers. The article explains how the bug can enable WAN-side remote code execution, potentially with root access, and discusses its discovery and firmware status. ### Source excerpt A breakdown of a bug SEFCOM T0 and I exploited to achieve a WAN-side RCE in some Netgear RAX routers for pwn2own 2022. The bug is a remotely accessible command injection due to bad packet logging, cataloged as CVE-2023-24749. ## Competing in Pwn2Own 2021 Austin: Icarus at the Zenith DevFeed: [Competing in Pwn2Own 2021 Austin: Icarus at the Zenith]() Original publisher: [Read original article]() Author: Axel "0vercl0k" Souchet Published: 2022-03-26T15:00:00Z Content type: opinion Language: en Sources: [Diary of a reverse-engineer]() Topics: [Security](), [Ghidra](), [Hardware](), [Network](), [Code]() Tags: [archer-c7](), [competition](), [cve-2022-24354](), [exploitation](), [firmware](), [ghidra](), [memory-corruption](), [netusb](), [network](), [pwn2own](), [pwn2own-austin](), [remote-kernel](), [reverse](), [router](), [routers](), [security](), [tp-link](), [tp-link-archer-c7-v5](), [zenith]() ### AI overview A personal account of preparing for and entering the Pwn2Own 2021 Austin competition. The author describes reverse-engineering consumer router firmware, selecting a router target with teammates, and working toward participation in the contest. ### Source excerpt Introduction In 2021, I finally spent some time looking at a consumer router I had been using for years. It started as a weekend project to look at something a bit different from what I was used to. On top of that, it was also a good occasion to play ... ## Comparison of net/http and httprouter DevFeed: [Comparison of net/http and httprouter]() Original publisher: [Read original article]() Published: 2019-05-23T00:00:00Z Content type: comparison Language: en Sources: [Gaurav Sarma's Blog]() Topics: [HTTP](), [Routing (disambiguation)](), [Go Language](), [Framework]() Tags: [comparison](), [go](), [http](), [router](), [routers](), [routing]() ### AI overview This article compares HTTP request routers in Go's standard net/http package and the httprouter package. It explains how net/http maps URI patterns to handlers and how httprouter uses compact prefix trees for routing. ### Source excerpt This post will mainly revolve around the comparison between different implementations of Routers in the HTTP based frameworks. Let's first go over what routers are in the context of a HTTP framework...