Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: I built an ISP infrastructure emulator from scratch with a custom vBNG

aether.saphal.me

Post reply on HN
Print view View original

21–24 of 24 posts

Re: Show HN: I built an ISP infrastructure emulator from scratch with a custom vBNG

#21

Post by saphalpdyl »

morphle wrote: post #20

You ask for feedback: I am surprised the author did not mention or uses Software Defined Networking (SDN), Openflow or P4 (programming language for programmable switches) or the mininet simulator. He must have skipped reading the scientific literature even though he is a computer science sophomore? I programmed and build one of the very first ISP hardware and software systems in 1987-1997 when we connected the first…

Thank you for the context. I did start out with mininet, then moved to containernet->containerlab. Mininet could not model subscriber session lifecycle in how I wanted it. P4/Openflow is on the radar, thanks for the pointer.

Re: Show HN: I built an ISP infrastructure emulator from scratch with a custom vBNG

#22

Post by saphalpdyl »

chaz6 wrote: post #12

Thanks for sharing! I am happy to see open-source BNG projects taking off in the last few months. These are a couple of others to look at:- https://github.com/codelaboratoryltd/bng-edge-infra https://github.com/veesix-networks/osvbng

I reached out to the maintainer of osvbng, and he was really receptive about it. I may contribute to the project in a few months.

Meanwhile, I also found another project that works with eBPF-accelerated BNGs for k8s edge deployments. https://github.com/codelaboratoryltd/bng (BUSL-1.1 license though)

Thank you for listing me the projects. Really helped me out!!

Re: Show HN: I built an ISP infrastructure emulator from scratch with a custom vBNG

#23

Post by bewo001 »

morphle wrote: post #20

You ask for feedback: I am surprised the author did not mention or uses Software Defined Networking (SDN), Openflow or P4 (programming language for programmable switches) or the mininet simulator. He must have skipped reading the scientific literature even though he is a computer science sophomore? I programmed and build one of the very first ISP hardware and software systems in 1987-1997 when we connected the first…

well.. openflow is pretty much dead, too inflexible, too slow. The whole control/user plane split is an attempt of the classical router vendors to keep their proprietary boxes. It adds complexity as it requires to synchronize the state of some controller with some data plane box.

P4 was a great idea, but there's not much hardware that supports it.

fd.io / vpp is an impressive stack for software-only routing. Like all SW-only solutions, it suffers from high power consumption and packet rate variability. At today's packet rates, you always have to ask 'how many CPU instructions / cycles are required to perform this or that function per packet'.

Post reply on HN