Packet Pushers

http://packetpushers.net/ - great podcast for network-related industry news & opinion. Nice mix of useful information and personality bombast.

The http://packetpushers.net/ guys are great.

I listed to the Heavy Networking packet pushers episode on this (https://packetpushers.net/podcast/heavy-networking-596-weaponizing-fir… was fascinating! shout out to this podcast, really great quality content!

Along with the other great suggestions: - Daily Tech News Show: http://www.dailytechnewsshow.com/ - Tech's Message (UK focused): http://www.natelanxon.com/podcast/ - PacketPushers Network: http://packetpushers.net/series/weekly-show/ - BBC's Click Podcast: http://www.bbc.co.uk/programmes/p002w6r2/episodes/downloads

Slides from IETF96: https://www.ietf.org/proceedings/96/slides/slides-96-maprg-1.pdf Paper: http://arxiv.org/pdf/1606.00360.pdf Edit: If you have some time and like high quality networking commentary (aka 'rants'), I strongly recommend to listen to this packet pusher episode with Geoff Huston, where he plays devil's advocate for IPv4. http://packetpushers.net/podcast/podcasts/show-275-future-of-networkin…

Exactly. It's information that has to be provided in the IP header. A great description is here: http://packetpushers.net/how-does-qos-work/ If that information isn't there, then the packets are treated as "best effort" (or at least, they should be in a sane world).

http://packetpushers.net/ It's a networking podcast mainly focused on high end datacenter stuff, but also they have a wireless specific podcast periodically. If you're into hardware and systems engineering, it's quite interesting. They also get a lot of vendors on and really grill them.

Warning about old books. (The NoStarch one is from 2005) Given that IPv4 Evolved a lot over the last 20 years to manage the complexity of address assignment and shortages, everyone should be aware that IPV6 has changed too. The chapter on IPv6 just barely hint and the development of IPv6 in real world cases. Don't take an almost 20 year old book for gospel for IPv4 or IPv6. Policy and implementation practice has changed enormously. Look at documentation from the last few years and from good sources. EG Apnic is the Regional Internet Registry for Asia. https://blog.apnic.net/2023/04/04/ipv6-architecture-and-subnetting-gui… Also a good source of info and opinions is the Packet Pusher set of podcasts. https://packetpushers.net/ I find that they tend to have a very real world explanation of topics covered and they avoid the "I've doing networking for 20 years. Don't tell I have to change" attitude.

This is frighteningly complex and I would not recommend this for reliability concerns. Terraform makes it quite difficult to maintain a structure like this, mostly due to the inability to interpolate module versions. I highly recommend anyone using terraform start with a mono repo. Still use modules and then spread out your components but definitely don't try to split them up in separate repos because keeping the version graph together will become a real pain and is easy to mismanage. From there, ensure any logical components have their own separate lock and state file. If you don't do this, it is going to be a game of roulette to know when this resource was last run and what might change if you roll it out. It is easy to build your own directed graph between components using data sources. These allow you to have component B read component A's state file to get the outputs it needs. All in all, I've found most of the documentation and "best practice" in the terraform community promoting dangerous practices. I talk more about these practices in this podcast[0] [0]: https://packetpushers.net/podcast/full-stack-journey-027-understanding…

> See perhaps OPTION_IA_TA (Temporary Address): I was unaware of this, so thanks. Sounds like it addresses (pun intended) my concern. > How does DHCPv6 hold back IPv6-mostly? First, most clients will send out a DHCPv4 request in case IPv4 is the only option, in which case IPv6-mostly can be signalled It's not the signalling that's the problem--it's the configuration of the CLAT which requires SLAAC, afaiu. This is in fact the subject of the latest IPv6 Buzz podcast episode: https://packetpushers.net/podcasts/ipv6-buzz/ipb197-slaac-and-the-end-…

Indeed. IPv6 is something very different from IPv4. And due to the large number of significant changes it's still a work in progress as a standard, with important RFCs coming out "as we speak"[1]. [1]: https://packetpushers.net/podcast/ipv6-buzz-134-revisiting-unique-loca…

The IPv6 Buzz podcast had a recent episode[0] making the claim that IPv6 is happening on your network whether you intentionally enable/control it or not these days and I had a similar reaction to the one in the post. Definitely something to think about though if you’re in a position to worry about such things. 0: https://packetpushers.net/podcast/ipv6-buzz-123-why-you-need-an-ipv6-s…

also, SRv6 in my opinion, is just a mess of security holes [0] and reinventing the same architecture over and over again while it is far more cumbersome to implement in hardware compared to simple MPLS LSP lookups.[1] [0] https://mailarchive.ietf.org/arch/msg/v6ops/GbWiie-bjQ_Bp1JKB1PlDh_fPd… [1] https://packetpushers.net/srx6-snake-oil-or-salvation/

Here's a news article that explains why FRR forked off Quagga: they wanted a more open and receptive development process - https://packetpushers.net/free-range-routing-project-forks-quagga/

ZeroTier is the perfect solution, it's the most genious VPN solution i've seen. http://packetpushers.net/podcast/podcasts/pq-134-meet-zerotier-open-so… <- Here's a Pod with the creator of ZT, once you've listened to it you'll realize how it fits everyone =)

digitalocean charge $5/mo for 1TB. Downloading 200GB will cost you just over 440GB of your 1TB limit Assuming a 10% overhead http://packetpushers.net/ipsec-bandwidth-overhead-using-aes/

Yes, it is based after the musical term! I explained a bit about the naming in the Packet Pushers Podcast[1] (around the 6:40 mark) Disclosure: I'm the creator of Ostinato [1] http://packetpushers.net/podcast/podcasts/pq-show-52-using-ostinato-to…

There are perhaps missing details, but Guifi seems to have "become" a provider by having "enough" customers. They got a peering connection. There's a threshold beyond which peering make more sense than transit... (http://packetpushers.net/transit-vs-peering-makes-sense/).

Networking news https://www.sdxcentral.com http://www.crn.com/news/networking/ http://www.networkcomputing.com/networking.asp http://packetpushers.net http://searchsdn.techtarget.com http://searchnetworking.techtarget.com http://www.theplatform.net/category/connect/ http://www.cbronline.com/enterprise-it/it-network

By no means there's any doubt in MIT admins' competency. Just that by reading the encounter, I feel sorry for the cards they've been dealt with, so to say: 1) a s/w hang for which there was no way to advance in a getting a solid RCA. This alone is a very hard one, and I know the ugly feeling both from the customer's side and from the vendor's side when all you have as an action plan is to try to reduce the potential exposure to what you think the problem is. I've been there myself multiple times, both as a customer, and as a vendor support. 2) Bridge loops. You can fix an active loop by disconnecting links, but root-causing such a problem is not a piece of cake, by far. 3) A buggy client firmware. This particular nastiness has been unfortunately a bane of quite a few networks already - see http://packetpushers.net/good-nics-bad-things-blast-ipv6-multicast-lis… for the details about it, or https://www.mail-archive.com/[email protected]/msg55556.html for the first-hand encounters. 4) TCAM overload (?) due to privacy addresses rotation. "TCAM space dedicated to IPv6 multicast is only 3,000 entries. That would be just barely enough to support all of CSAIL". The network gear frequently allows to re-carve the TCAM space - maybe they might have taken some space from IPv4 which is by default is provisioned much more generously (for various reasons outside the scope for this thread). Besides just brute-forcing, there might be other strategies in…