mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,4 Tsd.
aktive Profile

#vyos

0 Beiträge0 Beteiligte0 Beiträge heute
Scott Laird<p>Yow! I've been running <a href="https://hachyderm.io/tags/Minisforum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Minisforum</span></a> MS-A2 <a href="https://hachyderm.io/tags/VyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VyOS</span></a> router performance benchmarks in the background for most of the weekend. I'll make a relatively small config, reboot, re-run the multi-hour NDR sweep with trex, lather, rinse, repeat.</p><p>When I set the BIOS to "performance" power mode instead of "balanced" (the default), I notice that it spikes to drawing 185W from the wall and runs like a bat out of hell for 6 seconds before throttling itself back down to 155W.</p><p>That's a spicy little mini PC -- I don't know how it expects to cool 185W. I mean, obviously it isn't, but it seems like a weirdly aggressive thing to even attempt.</p><p>This is *obviously* optimized for gaming/desktop uses, where a 6s spike in performance followed by slowing back down is a good thing. It benchmarks fairly poorly this way, though. Dropping back to "balanced" seems to give much better numbers overall.</p><p>I tried turning on AMD PBO, which will boost clock speeds even more when thermals permit it. </p><p>Thermals didn't permit it. </p><p>I'm running each test 3x, and with PBO I was seeing giant differences from run to run. Like 5.84/14.83/5.85 Mpps across 3 runs. In "balanced" mode without PBO it consistently got &gt;15 Mpps, so enabling PBO isn't even slightly helpful.</p><p>This box feels like it should be faster than it is on routing; it's clearly faster than my previously-measured numbers on this thing's Intel twin, but throughput doesn't seem to be linear with CPU load. At 80% of peak load, it's using something like 50% of its CPU, but increasing past that rapidly swamps the CPU.</p><p>I saw similar with the Intel system, but I blamed it on Alder Lake's mix of P and E cores. The AMD model has 16 equal cores, so *that*'s not the problem.</p><p>I'm not sure if I'm hitting kernel-tunable issues (I've found at least one so far), hardware-tunable issues (Mellanox *loves* knobs), cache-size issues, or memory-bandwidth issues.</p><p>I probably have the tools to figure it out, though, so I'll leave tests running in the background for a day or two and keep making little tweaks to see what helps.</p>
Salearlyman<p>Hey fellow sysadmin cosplay nerds, does anyone here use VyOS? I use VyOS as the main router for my home network and I just found out that a job for uploading backups to an off-site location is strangling my upstream bandwidth.</p><p>I want to create a QOS / traffic shaping policy to treat this as bulk traffic - take up as much bandwidth as available but give priority to all other traffic.</p><p>Is there a simple way to do this? I don't want to allocate a fixed bandwidth for it.</p><p><a href="https://cloudisland.nz/tags/HomeLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HomeLab</span></a> <a href="https://cloudisland.nz/tags/vyos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vyos</span></a> <a href="https://cloudisland.nz/tags/sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sysadmin</span></a></p>
Junicast<p>After a couple of years of abstence I have to try <a href="https://chaos.social/tags/vyos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vyos</span></a> once again. I have been also trying to go back to <a href="https://chaos.social/tags/opnsense" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opnsense</span></a> lately but it seems I like <a href="https://chaos.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> based firewalls better, even though somehow <a href="https://chaos.social/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BSD</span></a>'s <a href="https://chaos.social/tags/pf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pf</span></a> is really good.</p>
Scott Laird<p>Feeling okay about progress on my <a href="https://hachyderm.io/tags/golang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>golang</span></a> <a href="https://hachyderm.io/tags/VyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VyOS</span></a> config handling code. It can read and write all 3 forms of config (`show`, `set`, and the on-disk boot format), and I have a demo WASM app with a text area that I can paste `show` configs into and get them auto-converted to `set` configs.</p><p>The next step is to bundle up a couple sample configs and add a template interface where you can specify which interfaces have LAN, WAN, etc, and what your IP address ranges look like. Then it'll auto-create a config for you.</p><p>Yeah, this is doable without a full parser or WASM, but it's not a bad exercise. Plus this is inherently flexible in ways that strict text templating systems aren't.</p>
Scott Laird<p>Today's "fun" side project: working on a <a href="https://hachyderm.io/tags/golang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>golang</span></a> library for parsing <a href="https://hachyderm.io/tags/VyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VyOS</span></a> router configs. </p><p>VyOS"s config is Juniper-like, rather than IOS-like, which I like. However, like Junos, that means that it has (at least) 2 different formats: the block-structured `show configuration` output and the `set` format (`show | display set` in Junos, `show | commands` in VyOS) that can actually be pasted into a device.</p><p>Right now, I can parse VyOS's block-structured configs into an AST and then dump the AST as `set` commands. The goal is to be able to parse and write all 3 of VyOS's config formats (its boot config format is *just* different enough to need its own code), to allow conversion between formats. The end goal is to be able to throw together a web app generating templatized starter configs that can convert between formats trivially.</p><p>The other goal is to get some practice with Go generics and probably WASM.</p>
Scott Laird<p>You know, <a href="https://hachyderm.io/tags/VyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VyOS</span></a> really doesn't seem happy when you try to add 65,536 static routes to its config. Sorta slow.</p>
Marek<p>VyOS is unfortunately becoming more and more isolated. They now even have an EULA - doesn't that contradict the GNU GPL?<br>I can understand the commercial interests behind it, but I think it's a shame.</p><p><a href="https://forum.vyos.io/t/doesnt-the-eula-contradict-the-gnu-gpl-is-vyos-stream-publicly-available/15756" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">forum.vyos.io/t/doesnt-the-eul</span><span class="invisible">a-contradict-the-gnu-gpl-is-vyos-stream-publicly-available/15756</span></a></p><p><a href="https://blog.vyos.io/vyos-1.4.1-release" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.vyos.io/vyos-1.4.1-releas</span><span class="invisible">e</span></a></p><p><a href="https://layer8.space/tags/VyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VyOS</span></a> <a href="https://layer8.space/tags/BGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BGP</span></a> <a href="https://layer8.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a> <a href="https://layer8.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> <a href="https://layer8.space/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeSoftware</span></a></p>
AliveDevil<p><a href="https://tauri.earth/tags/VyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VyOS</span></a> PSA: If you have Accept_ANY rules in Zone-based firewall, don't</p><p># set firewall global-options state-policy invalid action drop</p><p>This will just shortcut drop all new packets, sometimes.</p><p><a href="https://tauri.earth/tags/Router" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Router</span></a> <a href="https://tauri.earth/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a></p>
AliveDevil<p>So … <a href="https://tauri.earth/tags/VyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VyOS</span></a> people. What's your solution for monitoring link stability?<br>E.g. latency, ICMP drops, etc.</p><p><a href="https://tauri.earth/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://tauri.earth/tags/Router" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Router</span></a> <a href="https://tauri.earth/tags/HomeLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HomeLab</span></a> <a href="https://tauri.earth/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelfHosting</span></a></p>
AliveDevil<p>That urge to build a client app to configure <a href="https://tauri.earth/tags/VyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VyOS</span></a>.</p><p><a href="https://tauri.earth/tags/Avalonia" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Avalonia</span></a> <a href="https://tauri.earth/tags/Desktop" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Desktop</span></a> <a href="https://tauri.earth/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSharp</span></a></p>
ItzTrain<p>I got tired of fussing with <a href="https://hachyderm.io/tags/FRR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FRR</span></a> and trying to use it to do VRF's and routing as it really is geared towards Dynamic Routing! Back to <a href="https://hachyderm.io/tags/VyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VyOS</span></a> for the <a href="https://hachyderm.io/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homelab</span></a>. I am still using VRRP with 3 FFA routers on my <a href="https://hachyderm.io/tags/incus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incus</span></a> hosts. So as long as my upstream router is up. I can reboot hosts all day long and no internet go down.</p><p><a href="https://hachyderm.io/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a> <a href="https://hachyderm.io/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosting</span></a></p>
Paul<p>The <a href="https://social.pfzetto.de/tags/Vyos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Vyos</span></a> firewall currently doesn't support SIIT-DC (Stateless IP/ICMP Translation for IPv6 Data Center Environments). Luckily there is a workaround to configure it anyway: <a href="https://pfzetto.de/blog/siit-dc-for-vyos" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">pfzetto.de/blog/siit-dc-for-vy</span><span class="invisible">os</span></a><br><a href="https://social.pfzetto.de/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>networking</span></a> <a href="https://social.pfzetto.de/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv6</span></a></p>
Marek<p>VyOS 1.5 is somehow broken for me: Babel does not work at all (not even with the example from the documentation) and with BGP you cannot set a source address for installed routes (possible with route-map set src, but has no effect).</p><p>The rolling release seems to be enormously rolling.</p><p><a href="https://layer8.space/tags/VyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VyOS</span></a> <a href="https://layer8.space/tags/Babel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Babel</span></a> <a href="https://layer8.space/tags/FRR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FRR</span></a> <a href="https://layer8.space/tags/BGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BGP</span></a> <a href="https://layer8.space/tags/Networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Networking</span></a></p>
ItzTrain<p>I'm trying to get <a href="https://hachyderm.io/tags/VyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VyOS</span></a> dhcp across it's VRF's.. It doesn't seem to like it unless it's the default vrf, in which I do have services there.. I am running my own Kea dhcp server and that is pretty ehh.. getting dhcp lease information is cumbersome. So naturally i'm running 2.. for the vrf's that I can't use :) ..</p><p><a href="https://hachyderm.io/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homelab</span></a> <br> <br><a href="https://hachyderm.io/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a> <br> <br><a href="https://hachyderm.io/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosting</span></a></p>
ItzTrain<p>Aight!!! I did the VRF thing with <a href="https://hachyderm.io/tags/VyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VyOS</span></a> with 1 vlan routing out a TMO secondary internet provider for just streaming stuff.. <a href="https://hachyderm.io/tags/dhcp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dhcp</span></a> really gave me a run for my money and I couldn't it out trying to use the dhcp service on Vyos. So I'm just hosting my own now and... Yeah! It it works. I have been looking at the Cloud Gateway Max... Pro.. Mini...Biggie.. That looks like interesting to get into not managing my damn router any longer. </p><p><a href="https://hachyderm.io/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homelab</span></a> <a href="https://hachyderm.io/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosting</span></a> <a href="https://hachyderm.io/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a></p>
ItzTrain<p>Uh!! I'm probably moving to a batteries included router next.. Jesus christ! I don't know why I chose to move to VRF's on the router . I guess the big kids are doing it!! Now I can't get VRF's and the DHCP server to work on <a href="https://hachyderm.io/tags/VyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VyOS</span></a> </p><p><a href="https://hachyderm.io/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homelab</span></a> <a href="https://hachyderm.io/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a> <a href="https://hachyderm.io/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosting</span></a></p>
M. Hamzah Khan<p>Super happy <a href="https://intahnet.co.uk/tags/Vyos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Vyos</span></a> have announced Vyos Stream: <a href="https://blog.vyos.io/introducing-vyos-stream" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.vyos.io/introducing-vyos-</span><span class="invisible">stream</span></a></p><p>Using the nightly builds isn't great if you want something stable. I had a few issues in the past where they changed how something worked or was configured and it broke.</p><p>At the same time, the LTS version moves quite slowly. I get a bit of FOMO while running the LTS. 😅 </p><p>Using Vyos Stream is a great middle ground. You get new features, with a reduced risk of things breaking in the following days build.</p>
Jana<p>The change of <a href="https://social.jsteuernagel.de/tags/VyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VyOS</span></a> not allowing just anyone to build ISOs anymore seems to be in effect now.</p><p>I tried building a new ISO and got greeted with this error message:</p><p>E: Failed to fetch <a href="http://dev.packages.vyos.net/repositories/sagitta/dists/sagitta/InRelease" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">http://</span><span class="ellipsis">dev.packages.vyos.net/reposito</span><span class="invisible">ries/sagitta/dists/sagitta/InRelease</span></a> 403 Forbidden [IP: 2606:4700::6812:1e4f 443]</p>
Jana<p>Just yesterday evening I was thinking why seemingly every project that I like has some drama at the moment.</p><p>And now even <a href="https://social.jsteuernagel.de/tags/VyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VyOS</span></a> decides to do a rug-pull of their build tools, just as I decided to double down on VyOS as my cloud router software...</p><p>They say their rolling releases are stable and yes, they are pretty good, but I've had my setup break enough times, when I was on them, that I don't have enough trust in those anymore for critical stuff.</p><p><a href="https://blog.vyos.io/community-contributors-userbase-and-lts-builds" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.vyos.io/community-contrib</span><span class="invisible">utors-userbase-and-lts-builds</span></a></p><p><a href="https://social.jsteuernagel.de/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homelab</span></a> <a href="https://social.jsteuernagel.de/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>networking</span></a></p>
Pete Keen<p>My <a href="https://hachyderm.io/tags/VyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VyOS</span></a> router fell over and won't boot back up :(</p><p>I activated the fallback plan to use the ISP modem (bleh ugh) and now their app is spamming me with push alerts about every single device joining the network.</p>