I successfully installed VyOS on custom ARM64! | Investor update August 2024.

[@darylfortney8081]

Welcome to embedded development... a deep and dark world of constant unexplained challenges and a community of people who have absolutely no interest in helping you but would rather mock whatever it is you are trying to do. It makes retirement all that much sweeter

[@darylfortney8081]

@MrBigbanan 😂

[@marcogenovesi8570]

@MrBigbanan AI trained on what? embedded stuff is all secrets, NDA and whatever

[@Momi_V]

I am really happy you managed to get this to work. A homebrew rootfs might have been easier in the short term, but this looks a lot more robust and sustainable 5 or 10 years down the line

[@gavinskurrie]

Dude, if I win the lottery, id fund you! this project is awesome! I look forward to each update! Super keen to see how this all turns out! Well done to you and the team! Hello from Aus!

[@tomazzaman]

Thank you! 🙌

[@c0p0n]

Loving the work so far and I hope VyOS works out. It's a really nice router OS, probably the best linux-based solution out there.

[@MelroyvandenBerg]

Good that you listened to the feedback, since I also advised (if you still remember me?) to look into existing solutions rather than trying to create your own software from scratch. I know it won't be easy, but it would have taken much longer if you did all this from scratch. I hope your project will succeed with either VyOS or other Linux or non-Linux routing system!

[@tomazzaman]

Thank you! Regardless if we choose to go with our own solution or a 3rd party, I want to be able to offer plenty of documentation how each and any of those solutions can also be used on our hardware.

[@phillipmcmahon5949]

Super interested, and it's a great video! I run Vyos in my home lab, and the thought of dedicated hardware running this and a UI over the top is exciting. I hope you will support zone-based firewall configuration in your UI if you go that Vyos route. It's such a valuable tool of Vyos and makes complex firewall configuration much more accessible for those who aren't nftables pros.

[@dsincl12]

Super happy to hear that VyOS is on the horizon at least. For me this is a make or break if I will buy this or not.

[@Kitsok]

It seems to me, you've chosen the hard way. You need any working U-boot (which you already have), DTS (yes), and debian for such a board. Then you can install VyOS from packages. Or you boot into live VyOS and patch the install script.

[@tomazzaman]

Honestly, I didn't even think of installing VyOS from packages. Good one, thanks for the suggestion!

[@christopherhenry6562]

Fantastic update! I love the level of detail you include. VyOS is awesome and I'd love it if you're able to get it up and running reliably. Would be a great path forward for this device

[@andibiront2316]

I'm on the video! :) Great to know VyOS runs. AFAIK, Ubiquiti uses VyOS behind all the UI bling, or at least it did back then when I had an Edgerouter. If you wanted to do anything somewhat complicated the GUI didn't support it, but fortunately VyOS CLI is super easy to learn. Most of the packet processing was hardware accelerated in Edgerouter case, but not IPS/IDS. Will this router provide IPS/IDS and what would be the performance target? I guess with those cores, the LAN side is out of the question, but WAN side should be possible.

[@tomazzaman]

I can't answer that yet - I would love it to not only support it but also be relatively performant in it, but haven't gotten around to test any of the IPS (Suricata/Snort) solutions yet. Will do so sometime in the future, of course!

[@gondrom]

Ubiquity EdgeOS was a Fork of Vyatta... en.wikipedia.org/wiki/Vyatta

[@1DwtEaUn]

@@gondrom and an older one than VyOS forked from as well from what I have read 6.3 vs 6.6

[@blunden2]

@@tomazzaman If the hardware accelerated packet processing is implemented as nftables flowtable hardware offloading, it "should just work" in VyOS as long as the drivers support it.

[@not-yourbusiness]

Hoping to see the next video asap. Keep up the great work

[@arthurwiebe5508]

Way to go man, you've just kicked up this project a good several notches

[@youtubeneedsfix]

why was I living in a cave really , eureka moments for me. wow what a project in itself. I wish you all the luck .

[@thiagobmbernabe]

I will be interesting if it could be compatible with this new “mini rack” trend :)

[@tomazzaman]

That's a good point! :)

[@ILike2Tinker]

If you keep going with VyOS, it would be interesting to see a gui front end developed for it. Maybe, further down the road, you build your own fork for your router that adds a gui.

[@nickpetrovsky]

Jool is NAT64 translation mechanism

[@tomazzaman]

Thank you!

[@rfitzgerald2004]

Really glad you gave it a shot, I was one of the people recommending it in your last video (at the time I didn't notice any other comments mention it). I admire your perseverance Tomaž! Hopefully you get it resolved and I look forward to the official VyOS web interface that's in development being a part of this project at some point in the future as well

[@blunden2]

Development of the official VyOS web interface has been stopped a while ago since they didn't see enterprise customers asking for it, which is their target market. Unless Tomaž implements it himself, don't hold your breath for that to ever see the light of day (sadly). To be fair, the CLI is pretty straight forward. It still took me a few days off and on to configure everything for my dual stack home setup. Works great now though. 😀

[@rfitzgerald2004]

@@blunden2 That's a shame to hear, from the previews it looked so polished and well designed, I was looking forward to seeing it some day but I understand the reason. Would be amazing if Tomaž used it for this project and was able to fund completion of the interface, I think Tomaž's target audience being prosumer would benefit from it a lot

[@AhmadSwailem]

Good luck my friend

[@tomazzaman]

Thank you!

[@gcs8]

I told you VyOS gave me PTSD. lol

[@rokr0001]

I will watch your career with great interest.

[@MelroyvandenBerg]

Grub also works with legacy BIOS.

[@efimovv]

Even better - looks like it support uboot! At least fresh one on my system 2.12-r4

[@sethperry6616]

Please make sure that the design can either easily be set in a rack on a 1u shelf, or a 2u shelf. Whatever your enclosure looks like.

[@tomazzaman]

Yup, planned.

[@rooot_]

Couldn't you theoretically build a UI on top of something like VyOS? As in, fork VyOS and add features you want in the router? Sounds like an easier solution than doing a system completely from scratch ^^ Also, loving the progress so far, good luck!!

[@velho6298]

Got recommended this video. Great project idea! Have you thought about configuration without the UI such as from a file or something similiar?

[@tomazzaman]

Some systems already to that (VyOS in particular), and yes, it's definitely a good idea, because it makes backups super easy, just one file!

[@tygi]

What does prototype in october mean for us viewers: we see a case, a pcb, a ui, benchmarks, or what will we see?

[@tomazzaman]

Sorry for the confusion, I meant PCB prototypes, which are primarily for us to develop a "bring-up" - in this process, we will take everything we have been working on so far and adapting it so that we can get the PCB up and working correctly, then proceed to install an operating system. I'm also hoping first iterations of the case design will be ready by then, which means I'll be able to show you an early version of how the final product will look like. But don't hold me to it :)

[@alexthornburg7156]

Love this project

[@4ohm531]

I like your honestly very much

[@tomazzaman]

Thank you!

[@bigpod]

nice it was amaizing to hear that it worked

[@ernstoud]

Merging two different kernel configs, i.e. compiling in a probably large set of modules and functions leads to a monster of a kernel. I guess there is enough memory in this router but it doesn’t sound good.

[@tomazzaman]

Uncompressed kernel is around 40MB. We'll ship with 8GB of RAM. Not a problem :)

[@autohmae]

I think this is mostly, just to get stuff running, I'm certain someone in the future will check it.... hopefully ? right ?

[@ernstoud]

@@tomazzamanKernel in my current AON gateway/router: 1.4 Mb.

[@shapelessed]

To be absolutely honest, if I had to compile a linux carnel over and over again so many times, I would have just given up and spammed Jeff Geerling's DMs...

[@tomazzaman]

Don't want to bother the man, he just got a baby! :)

[@shapelessed]

@@tomazzaman And let the baby take his precious time and erode his passion away! How could I...?

[@DeadlyDragon_]

Are you planning to have separate control and data planes from a hardware standpoint? Since you are going with vyOS which supports BGP will you build this to accommodate a full v4 and v6 routing table? Do you have plans for hardware encryption for IPSec / VPN? Are there going to be any ASICs dedicated to switching and routing? Many many devices will say they can route X gigabit of traffic but the switching or physical interfaces themselves become the bottleneck. Or vice versa happens where the routing portion is vastly underpowered compared to the installed nics/switching plane. Are there going to be dedicated hardware features for layer 4/7 traffic inspection? IPS/IDS induces a hit to throughput due to increased processing requirements.

[@aleksandarvasilevski7410]

It is funny to hear that someone tries brute force to merge different kernel configurations. I am glad that I am not the one responsible for maintaining product with Frankenstein configuration. Wish you best of luck.

[@tomazzaman]

It's not that big of a deal really, for two reasons, this was a just done in a "proof of concept" kind of way, and second, it's very common to reconfigure kernels with fragments, which granted, are normally smaller, but I'd argue nobody really looks at each and every item. Even the "specialized" kernels, like the one from NXP, needlessly include support for chips that aren't even in their portfolios, simply because they'd have to manually go in and remove thousands of options.

[@calvin_thefreak]

12:45 On VyOS, there is I think only /config/ mounted. Rest is generated from config everytime.

[@rjramalho]

I might be late to the party, but have you considered IPFire? Their UI is a bit ugly and their choice of names is... well... wierd to say the least, but its known to be very very secure. Thanks for these in depth videos. I appreciate it. :)

[@tomazzaman]

I have not, no. So far, only OpenWRT and VyOS. Other solutions will unfortunately have to wait for now as I have to put my focus elsewhere.

[@rjramalho]

@@tomazzaman they already have ARM64 kernels, and is tested. It’s just one more option, if VyOS becomes a nuisance.

[@rjramalho]

@@tomazzaman they already have ARM64 kernels, and is tested. It’s just one more option, if VyOS becomes a nuisance.

[@madnessandescapism]

I doubt anyone expect PC-case compatible router board. Better spend this effort to provide good rack-mountable option which won't just waste 1U for 12cm board. Maybe some kind of crazy combination of router and patch-panel or PDU? Or included battery-backup option?

[@matthiasrossini]

Love everything about this project, where can I sign up for the waitlist?

[@tomazzaman]

Many videos have the link in the description and I'll also add one in the upcoming update, so if you're subscribed, you're golden :)

[@AnnatarTheMaia]

Sitnica: "alas" je staroengleski za "nažalost", dakle suprotno od onoga kaj Ste mislili povedati...

[@tomazzaman]

TIL! Thanks!

[@Pea-pod]

Is it too late to ask that the i2c bus be expanded to the front panel of the case so at some point we can add a small display should we want to show stats. Unless it's changed I believe in one of the videos you mentioned the LEDs will be dropped except for a single one to show boot status

[@tomazzaman]

There will be a GPIO expander on the board, I2C bus included :)

[@recursiveg3220]

I wonder if any of these "private" drivers will be open sourced or upstreamed into the mainline kernel? I assume they are for the hardware network accelation functions. Without those, an ARM device can hardly justify itself for me compared to a X86 box, which has more CPU raw power and WAY BETTER OS optionalities. Besides, what about the corresponding userspace programs that're used to control the accelerators, will they be open sourced too?

[@blunden2]

It's fairly common for manufacturers to have out-of-tree drivers in addition to the mainline ones. That doesn't necessarily mean that they are not open source or that patches from them can't be upstreamed. Companies like Mediatek implement hardware offloading for their networking SoCs to be compatible with nftables flowtable offloading (which can use either hardware or software offloading), which is why OpenWrt can support it with their fairly modern kernels. Hopefully NXP did the same. 🙂

[@Alex-cm6uu]

Legend

[@phillipmcmahon5949]

Have you contacted Vyos directly to discuss the project? In particular, they have been threatening a UI for quite some time. Perhaps this is the layer you can provide, and they help ensure Vyos is natively compatible with your hardware platform?

[@tomazzaman]

Not yet, but we did have an internal chat about it the other day. No conclusions yet :)

[@phillipmcmahon5949]

@@tomazzaman genuinely excited by this project. I'll for sure be taking a founders edition model.

[@blunden2]

"Threatening" is probably not the word you meant here. 😉But yes, that sounds like a good idea. They have Figma design drawings for many of the UI screens available already. They might also have some code available from the Web UI implementation project from before they cancelled it.

[@wolfgangpreier9160]

Since i still do not get viable Gigabit VPN-Routers i have to use Linux on Supermicro Boards, Strong Intel or AMD CPUs and 2 HE 19" Enclosures, because the 1HE do not fit the new boards anymore. Still much cheaper than Cisco or e.g. Fortinet. Mikrotiks are nice but slooow.

[@TheMuso28]

If I understood the video correctly, it seems that NXP's own kernel/driver code that is not upstream in the mainline kernel performs better. I am disappointed about this. I would have considered this hardware, even though shipping to where I live would likely not be cheap. However, my first rule for any network boundary hardware is that the hardware must be as performant as it can be with pure upstream code, so that it receives software support longafter the hardware is no longer available. NXP seem to have failed here, which is a shame. I have no problem with the reasons you have for using their hardware, and there are plenty of other solutions I can look into for myself going forward. All the best with the project.

[@wolfgangpreier9160]

I don't care for support anymore. I had the same mindset 20 years ago. I have to replace the firewalls and VPN servers at my customers sites every 5-7 years anyway because Linux does not support the old hardware anymore. Now i have started to use general chinese Intel based small boxes. They have decent performance an seem to work just fine. I do not believe they will last longer than 3-5 years at most. But what is the alternative?

[@csabasipos6525]

​@@wolfgangpreier9160 Linux does not drop support for a very long time. They are just discussing dropping 486 support. Your devices like does not run vanilla linux, but some shite your vendor hacked together, and they stopped supporting their own proprietary crap, never cared upstreaming anything to the actual kernel codebase. Very typical and unfortunate.

[@wolfgangpreier9160]

@@csabasipos6525 I had to switch about 10 times since DLD 1.0 in 1994. Maybe more, it was a long time. Every roughly 5 years i have to get used to a new OS, new tools, new everything. There is no consistency. I can not even upgrade. And, frankly said, besides special services like web or mailservers, mysql, MS SQL, Oracle, acounting and others specific to one OS i do not see any difference between Windows and Linux. Sometimes Windows is easier and more stable - e.g. for virtualization since VMWare has been killed, sometimes Linux is easier for e.g. DNS, Mailservers, Firewalls. And please do not start with KVM or containers and other such complicated nonsense. Sometimes i believe men invent such complicated thingies to impress on their bosses and other men. Useless junk. When i need the processing power and storage, containers do not work and KVM is only good for Linux clients. Or could you tell me how i can provide Office 365 for 100 customers in a container?

[@encryped]

It's a downstream vs upstream thing. The hardware is supported by both kernels Linux upstream and Linux-qoriq, however you can develop more quickly on the linux-qoriq fork because you don't have to send in patches for each change. Typically once things stabilize the downstream changes end up back in upstream. It really depends on development cycles. Also technically you can simply take the linux-qoriq drivers as patches on top off the linux upstream kernel and that should just compile.

[@csabasipos6525]

@@encryped Would be nice, but not in reality. The fact you can boot a vanilla kernel on a SoC does not make all the functions to work. That is the common misconception when you say "the hardware is supported by both kernels", in reality far from all parts of the HW is supported, and in relation to a "high end router" most of the proprietary stuff that makes HW offloading works also breaks the netstack so it will never get merged usptream, and once the proprietary support is over, you are f*cked. This is the sad reality. The second part is also not true: if you look at a relevant example of adding offload support for the IPQ807x platform, it is a heroic struggle for the devs to keep compatibility even between minor versions of kernel, almost every time something breaks, not to mention between major versions, as the glue code is complex and intertwined on so many components of the low level operations of the netstack. Definitely not some easy to apply patches.

[@keylanoslokj1806]

Sir my ISP doesn't allow me to connect another router as extension to their own unsafe one. What should i do?

[@eduardoe2886]

Can you share the result binaries? I have an NXP Eval board and would like to test it... I will try to build It but it can take a while to get a working kernel defconfig...

[@marcogenovesi8570]

Hm, you at least chose a sensible OS, VyOS may not be optimal as it's lacking a web gui, but it's still already built/developed by third parties and based on Debian and designed for firewalls.

[@JustinGreathouse-r4i]

Rosalind Springs

[@AlbertaGiles-p2j]

Weissnat Ridge

[@no0ne.]

How can I get a Prototype Board? 🤤 Would love to tinker with it! Greetings from Austria 🇦🇹

[@tomazzaman]

There will be evaluation boards that we'll sell - but it'll take a bit. :)

[@feo786]

Will the router be "open" in the sense that we'd be able to load something like pfsense or opnsense onto it if we don't like the default OS? The hardware side sounds solid but it's more the software side that might turn people away.

[@xephael3485]

VyOS is "open" as in it's a Linux kernel that is made for routing packets. It's not inherently set up as a firewall

[@tomazzaman]

Yes. We will even prepare tutorials so that you'd be able to do it yourself without much fuss. We'll only ask you test it thoroughly and report back :)

[@mullvaden83]

As I understood it he wont use pfsense or opnsense cause they are FreeBSD based and dont work with ARM. Or work very poorly with his chip or not at all. That is why he is going the Linux route.

[@feo786]

@@tomazzaman ah that's great. So I guess I should hold off on getting a mini PC off AliExpress for my router and buy yours rather, yeah? 😁

[@tomazzaman]

definitely. :D

[@samamvs2698]

Will this introduce a problem later on if we want to upgrade vyos?

[@tomazzaman]

No idea, it shouldn't from what I've seen so far, but I'm no VyOS expert, so can't say definitively yet. Of course, this will be tested in the future.

[@autohmae]

You have to first understand the parts involved then you can learn how to do upgrades

[@mrlazda]

12+ layers board? That is too much for what you are making. Your design needs a maximum of 8 layers, or some went very wrong with PCB design. 12 layers is enough for even high-end FPG design with 100Gb ethernet (just FPG is 20000+€). Smart phones usually are 8-10 layers, same as computer motherboard. With a lot of layers, routing is much easier, but with high speed, you easily get in trouble (vias act as stub, so you need to use blind vias or/and backdrill)

[@RoyvanLierop]

If you could start from scratch with the knowledge you have now, would you go with NXP? I'm contemplating Renesas for my first embedded Linux experience.

[@tomazzaman]

Honestly? Yes, absolutely. Their DPAA architecture is pretty sick. The only alternative I'd personally go with if price wasn't an object, I'd go with one of Marvell's Octeons. Talking in the context of routing.

[@EdwardBean-x5l]

Sauer Haven

Maaan "dude" treba ti jaaka terapija??! & have a good one!! Ne pogrešno shvatiti., ćin-ćin živio!!

[@EffieStilwell-l2y]

Shemar Stravenue

[@SweetAdair-o4p]

Jettie Stravenue

[@melissasmithfe9096]

Joany Isle

[@esra_erimez]

Why not use ipfire?

[@tomazzaman]

I have 0 experience with it.

[@DouglasPeek-g4v]

Everett Street

[@ThomasTurner-o1o]

Stoltenberg Branch

[@HuntingtonCora-c7j]

Gibson Tunnel

[@SavannahHaubrich-y3e]

Cassin Corner

[@nkeor]

Even though I like VyOS, I still wish FreeBSD support can come down the line, I''d be happy to help!

[@blunden2]

Fewer and fewer companies contribute to FreeBSD so it becomes less and less feasible to build products around it. I don't really see that changing unfortunately.

[@virinom]

Do you think at some point a huge networking company(we all can guess who they are) will come to your doorstep and offer you good cash to take down everything? (Or maybe they already did :D)

[@Basn]

DYI, nixos etc? Is this possible? Or is it only i mean with good drivers

[@tomazzaman]

As long as the kernel has drivers for the CPU's data path architecture, then it should work.

[@Basn]

@@tomazzaman its a really fun project to follow 👌

[@BromTeque]

I'm sorry for suggesting VyOS. 🥺

[@tomazzaman]

Don't be. I like a good challenge! :)

[@gamingforlive2150]

gotta ask am i the only one that was a bit confused by vyos when they tried it?

[@WhitAntonia-r4p]

Presley Bridge

[@metropolis10]

I love these videos and your journey, but I do wish you would work on your diction for these videos, it feels like you are shouting the whole time. Even when I turn down the volume. Again love the videos and the journey, just my one small gripe.

[@EllenChaucer-o5g]

Daryl Shoals

[@SadieSimon-j2z]

Lesch Canyon

[@MalthusBarbara-g1z]

Schulist Wall

[@ThomasCostner-c1m]

Koss Inlet

[@tvojejbabkydedko]

Grub requires UEFI?

[@tomazzaman]

Yep, unfortunately.

[@TristanYerkes-y1d]

Berniece Crescent

[@RamonLeysath-s6w]

Marty Brooks

[@MontgomeryBridget-v3u]

Jacques Island

[@SubhadeepSubhadeep1]

maybe it's a bit off-topic, but there is a sweat drop in your forehead XD

[@tomazzaman]

It is. AC is off while recording and it gets insanely hot.

[@user-dy9ux5dc6e]

VyOS would not be my first choice. Nor NXP.. I fear that your learning project may not sell very well. Too many well-supported and mass produced options on the market already. Not much of "niche" here in terms of the hardware. I will buy one as a novelty if it's not too expensive but I don't think it would ever find much of a use. Good video content though!

[@tomazzaman]

Thanks for the feedback - although I disagree with you (and so does more than 5k people on the wait list as of this moment). Some of the Cisco Meraki products for example, use the same CPU.

[@MercedesLott-d2r]

Leland Passage

[@WalkerLucy-v9v]

Bradtke Brook

[@bigpod]

honestly im kinda happy this went ARM route and not X86 route(even tho i think x86 is supiror in desktop space and server space but not in embedded space.) problem with things like PFSense and stuff is they are more of enthusiast tools which means in general enthusiasts will have bunch of x86 harware laying around not so with arm

[@mrlazda]

The only problem is that there are no readly available ARM processors that have speed for 2.5gb routers (they at that speed can just barely do simple routing without any firewall). To be able to do, for example, router and firewall at 5gb speed, you would need i7 12gen (which is 20 times faster than ARM he choose), but probably you could do it with slower ARM/x86 if you pick some high end compiler to compile OS (for example in this for ARM to use IAR, but most linux diatro are made for GCC compatible compilers and IAR is not so you are in trouble there).

[@bigpod]

@@mrlazda thats where off loading comes in there is much more to such hardware then just you know raw compute

[@mrlazda]

​@bigpod offload don't help you. At least offload, you can find off the shelf, they are TCP (or even more specialised for example iSCSI) offload what is for routing useless bacouse routing only use IP and have nothing to do with TCP. You can do offload in some custom FPGA/ASIC, but again, it is not a solution that is readly available. Edit: from pfsense "TCP offloading splits network traffic into MTU size parts. This should only be done from the end-point server. A firewall should not use TCP offloading because the servers behind it are already performing TCP offloading."

[@blunden2]

@@mrlazda You are way off on your performance estimates. Even an Intel Atom C3758R (used in the Netgate 8200 for instance) happily routes 10 Gbps with NAT + firewall (I speak from experience) unless we're talking solely minimum packet sizes (which it can handle too if you use VPP). An Intel N100 can also do 10 Gbps routing as long as you give the NIC the PCI-E lanes it needs. A 12th gen i7 would probably be closer to 15-20 Gbps. Actually, there are several ARM SoCs that have no problem handling 2.5 Gbps routing + firewall. If you also run IDS/IPS on all traffic, that's a different story.

[@blunden2]

@@mrlazda You clearly don't know what kind of offloading people are talking about here. We are talking about network focused ARM SoCs that have hardware packet processing engines. The MediaTek FiLogic 880 is one example, the NXP SoC used here is another. Different SoCs like that have been used in network products for many years at this point, although some of the older ones were MIPS SoCs. TCP offloading is something else and not relevant to this discussion.

[@bdg88]

Just get a CPU that supports all these distros 🙃

[@LeeHearne-w5t]

Dimitri Street

[@ahmetkipkip]

Just develop and contribute to openwrt man........

[@AdahCacibauda-k2z]

Alexie Glens

[@triffid0hunter]

Why grub? Don't need it for a single OS target, just boot the kernel directly…

[@EctalZero]

Because of how VyOS is made, he spoke about it multiple times

[@traced82]

EDIT: since everyone is starting to cry here... not a single unit was too dramatic sorry... What I meant: not many will buy that thing without a gui... ---- You will not sell a single unit if theres not a gui... most of the people are scared to configure a complete device on cli only.

[@alexandrequemy]

I consider myself a power user and I'd not buy a router without a UI. Too useful to not lose time. I also need CLI and/or API for the exact same reason.

[@traced82]

@@alexandrequemy it must have both I think. Easy clickable like pfSense/OpenSense, but also able to change settings via ssh/api, and SNMP for monitoring.

[@tomazzaman]

Well, this whole experiment was done because people literally asked for VyOS, so not true. That being said, I agree with you do a degree, which is why I have also tested OpenWRT and can confirm it's working just fine, regardless if I'm personally not a fan of their UI.

[@kresimirpecar4925]

Did you test it with RouterOS maybe ?

[@ducttapetrousers]

I would certainly buy a router with TUI only, so long as it is a good one (which I believe this will be). Your statement is wrong.

[@ArnoldMiranda-u8g]

Denesik View

[@LamarOderkirk-b1s]

Afton Lane

[@DJDocsVideos]

diff & merge...

[@DavidAguinaldo-d1m]

Kyra Pass

[@xephael3485]

VyOS needs to be forked... They're pulling the same garbage Vayatta did.

[@tomazzaman]

Care to explain?

[@leandrogaleano1771]

​@@tomazzaman TL;DR: VyOS is just a fork of Vyatta, but it still carries too much old baggage from past project; read some controversies for not cutting down on some modules from the past.

[@Fubarist]

@@leandrogaleano1771 quit spreading old outdated useless info.

[@phillipmcmahon5949]

@@leandrogaleano1771 this is being heavily worked on. The team is doing great work to modernise and simplify the Vyos ecosystem.

[@Unicrontesting]

Not true, support costs money, and pre build images need a subscription, but the source is open and you are free to build yourself.

[@MacLimitRange]

But pfSense? Ah no, the system isn't x86. Right. Pff, what a waste using x86 hardware that is readily available everywhere, better going ARM.

[@tomazzaman]

I think there's a company that bet big on ARM when everyone one was screaming x86. Can't remember the name right now, but it's a fruit,... :D

[@chewbaccabg]

Just wondering... why are you bothering with a new router, when Mikrotiks are somewhat cheap and extremely useful already?

[@dezent]

Why are you bothering with a new KZbin comment, when other people already made perfectly good and extremely useful comments?

[@blunden2]

Not everyone likes RouterOS. Also, their options in this performance class are mostly rack mounted with noisy fans last time I checked. The one model that wasn't didn't actually route at full 10 Gbps last time I checked.

[@AntranigVartanian]

I wonder if your board could support FreeBSD. Your life would be much simpler, and you’d have a better network stack anyway.

[@hedikintheoriginal]

i got tought VyOS in school, and had just as many issues

[@xephael3485]

Test

[@tomazzaman]

Test

[@xephael3485]

@@tomazzaman I was trying to reply to you about VyOS in the comments and it didn't seem to be posting

[@ShadowDev6969]

VyOS is soooo bad. I just stick with opnwrt

[@Fubarist]

Wrong.

[@ShadowDev6969]

@@Fubarist im not wrong, this is called an opinion since its all subjective. I have found opnwrt has worked better in my projects. Every time I have used vyos I have had endless issues.

[@sasjadevries]

@@ShadowDev6969 Well, openWRT did pose problems to him, and it's less performant. 🤷‍♂