7 ms·

Unfortunately they went full "Vyatta way" or "RedHat Way" by basically giving rolling release for free only. I remember times when Vyatta went behind paywalls V

by amar0c 3y ago

Unfortunately they went full "Vyatta way" or "RedHat Way" by basically giving rolling release for free only. I remember times when Vyatta went behind paywalls Vyos was completely free. Not sure who would want something rolling on device like router. Nowdays everyone wanting something good and free go OpnSense way.

rnhmjoj 3y ago
The biggest problem I have is that they only support (or at least that's what they release publicly) x86_64. I am forced to use openwrt because the vast majority of consumer low-power hardware is using ARM or exotic architectures. VyOS interface is vastly superior, though.
- sp0ck 3y ago
  VyOS is not targeted for such usage scenarios. It is ISP who are paying for support. I have VyOS systems with BGP, MPLS, PPPoE termination, etc that are pushing gigabits of traffic. This is VyOS usecase. Not 5W router handling home or small office.
  - rnhmjoj 3y ago
    I've used EdgeOS in the past and it's perfect for SOHO routers too, but unfortunately is half full of proprietary extensions and semi-abandoned. I think VyOS could take its place nicely, openwrt feels like a toy compared.
thepill 3y ago
You can build your own LTS image relatively easy and free of charge
- LeBit 3y ago
  The process is not straightforward, especially if you want to customize the image. And I have been unable to build a cloud-init image. But the ISO is buildable from the LTS branch and it works well.
  - solarkraft 3y ago
    It's been a while since I tried it, but I remember this roughly being my experience as well. I'm usually all for up to date software, but on my networking equipment??? I don't really want to beta test that stuff, but that's what they seem to want to make me do.
    - LeBit 3y ago
      It is not really beta software though. If you don't want to go into the trouble of building your own ISO, then, yes, you are a beta tester because the only thing they make available pre-built is the ISO from the 1.4 branch which is in flux. You can build the ISO from the LTS branch though and that branch doesn't move much. Though, I don't know how you can tell which commit was used to release, say v1.3.2. For the moment, I simply build an LTS ISO using the latest commit of the LTS branch. That strategy has been rock solid for years now.

by amar0c 3y ago

rnhmjoj 3y ago

The biggest problem I have is that they only support (or at least that's what they release publicly) x86_64. I am forced to use openwrt because the vast majority of consumer low-power hardware is using ARM or exotic architectures. VyOS interface is vastly superior, though.

sp0ck 3y ago
VyOS is not targeted for such usage scenarios. It is ISP who are paying for support. I have VyOS systems with BGP, MPLS, PPPoE termination, etc that are pushing gigabits of traffic. This is VyOS usecase. Not 5W router handling home or small office.
- rnhmjoj 3y ago
  I've used EdgeOS in the past and it's perfect for SOHO routers too, but unfortunately is half full of proprietary extensions and semi-abandoned. I think VyOS could take its place nicely, openwrt feels like a toy compared.

thepill 3y ago

You can build your own LTS image relatively easy and free of charge

LeBit 3y ago
The process is not straightforward, especially if you want to customize the image. And I have been unable to build a cloud-init image. But the ISO is buildable from the LTS branch and it works well.
- solarkraft 3y ago
  It's been a while since I tried it, but I remember this roughly being my experience as well. I'm usually all for up to date software, but on my networking equipment??? I don't really want to beta test that stuff, but that's what they seem to want to make me do.
  - LeBit 3y ago
    It is not really beta software though. If you don't want to go into the trouble of building your own ISO, then, yes, you are a beta tester because the only thing they make available pre-built is the ISO from the 1.4 branch which is in flux. You can build the ISO from the LTS branch though and that branch doesn't move much. Though, I don't know how you can tell which commit was used to release, say v1.3.2. For the moment, I simply build an LTS ISO using the latest commit of the LTS branch. That strategy has been rock solid for years now.