#vxlan

0 Beiträge0 Beteiligte0 Beiträge heute

Grzegorz Surmann :verified:Juniper EVPN/VXLAN mesh or ring <a href="https://blog.funil.de/3457/sinuspl/english/juniper-networks/juniper-evpn-vxlan-mesh-or-ring/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blog.funil.de/3457/sinuspl/english/juniper-networks/juniper-evpn-vxlan-mesh-or-ring/</a> <a href="https://mstdn.funil.de/tags/evpn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#evpn</a> <a href="https://mstdn.funil.de/tags/jumboframes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#jumboframes</a> <a href="https://mstdn.funil.de/tags/juniper" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#juniper</a> <a href="https://mstdn.funil.de/tags/mesh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mesh</a> <a href="https://mstdn.funil.de/tags/ring" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ring</a> <a href="https://mstdn.funil.de/tags/vxlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vxlan</a>

Grzegorz Surmann :verified:Quick fixes for Juniper problems <a href="https://blog.funil.de/3551/sinuspl/english/juniper-networks/quick-fixes-for-juniper-problems/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blog.funil.de/3551/sinuspl/english/juniper-networks/quick-fixes-for-juniper-problems/</a> <a href="https://mstdn.funil.de/tags/clear" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#clear</a> <a href="https://mstdn.funil.de/tags/cli" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cli</a> <a href="https://mstdn.funil.de/tags/error" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#error</a> <a href="https://mstdn.funil.de/tags/evpn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#evpn</a> <a href="https://mstdn.funil.de/tags/juniper" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#juniper</a> <a href="https://mstdn.funil.de/tags/junos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#junos</a> <a href="https://mstdn.funil.de/tags/loop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#loop</a> <a href="https://mstdn.funil.de/tags/network" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#network</a> <a href="https://mstdn.funil.de/tags/statistics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#statistics</a> <a href="https://mstdn.funil.de/tags/vxlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vxlan</a>

Thomas Liske<a href="https://ibh.social/tags/ifstate" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ifstate</a> 1.13.2 was released: <a href="https://codeberg.org/liske/ifstate/releases/tag/1.13.2" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codeberg.org/liske/ifstate/releases/tag/1.13.2</a>(available in <a href="https://fosstodon.org/@alpinelinux" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@alpinelinux</a> edge + 3.21 3.20 + 3.19 and in <a href="https://c3d2.social/@m4rc3l" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@m4rc3l</a>'s Nix flake <a href="https://codeberg.org/m4rc3l/ifstate.nix" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codeberg.org/m4rc3l/ifstate.nix</a>)This maintenance release includes fixes for configuring FDB entries.The configuration of VXLAN with non-default UDP ports, unicast and static flooding now works correctly: <a href="https://ifstate.net/examples/vxlan.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://ifstate.net/examples/vxlan.html</a><a href="https://ibh.social/tags/linuxnetworking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linuxnetworking</a> <a href="https://ibh.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> <a href="https://ibh.social/tags/vxlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vxlan</a>

Freifunk StuttgartNeues aus dem Maschinenraum: wir haben unsere beiden Proxmox-Cluster miteinander vernetzt. Wir verwenden dazu <a href="https://chaos.social/tags/vxlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vxlan</a>. Als Underlay dienen <a href="https://chaos.social/tags/wireguard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wireguard</a> Tunnel mit <a href="https://chaos.social/tags/babel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#babel</a> als Routingprotokoll. Ziel ist unsere gesamte Infrastruktur in <a href="https://chaos.social/tags/stuttgart" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#stuttgart</a> zu hosten, aber immer noch die Möglichkeit zu haben auf einen anderen Standort auszuweichen. <a href="https://chaos.social/tags/ffs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ffs</a> <a href="https://chaos.social/tags/hostlocally" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hostlocally</a>

Mike LossmannIt's the long-awaited part two of the EVPN Series! Next is a quick overview of What is VxLAN! <a href="https://bit.ly/480p41F" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://bit.ly/480p41F</a> <a href="https://mastodon.social/tags/VXLAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VXLAN</a> <a href="https://mastodon.social/tags/DC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DC</a> <a href="https://mastodon.social/tags/Networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Networking</a> <a href="https://mastodon.social/tags/technology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#technology</a>

Daniel ツVXLAN (Virtual Extensible LAN) is a network virtualization technology that helps overcome the limitations of traditional VLANs by enabling larger, scalable L2 networks over L3 infrastructure.In <a href="https://infosec.exchange/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kubernetes</a>, VXLAN can be used by CNI plugins (like <a href="https://infosec.exchange/tags/Flannel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Flannel</a>) to create overlay networks, allowing Pods across different nodes to communicate seamlessly, regardless of underlying physical networks. This makes multi-node clusters easier to manage at scale! 🚀<a href="https://infosec.exchange/tags/VXLAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VXLAN</a> <a href="https://infosec.exchange/tags/K8s" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#K8s</a> <a href="https://infosec.exchange/tags/CloudNative" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudNative</a> <a href="https://infosec.exchange/tags/Networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Networking</a>

WiresharkHere are even more agenda highlights from the upcoming SharkFest'24 EUROPE conference! - VXLAN, EVPN & other intricacies unpacked (Pierre Besombes) - Why web pages remain vulnerable to Layer 7 DoS Attacks (Michal Soltysik) - Wireshark Techniques for Security Analysts (Walter Hofstetter)More info: <a href="https://sharkfest.wireshark.org/sfeu" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://sharkfest.wireshark.org/sfeu</a>See you soon in Vienna, Austria! <a href="https://ioc.exchange/tags/Wireshark" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Wireshark</a> <a href="https://ioc.exchange/tags/VXLAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VXLAN</a> <a href="https://ioc.exchange/tags/EVPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EVPN</a> <a href="https://ioc.exchange/tags/DoS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DoS</a>

Stefano MarinelliBridging Networks Across VPS With Wireguard and VXLAN on FreeBSD<a href="https://it-notes.dragas.net/2024/07/15/bridging-networks-across-vps-wireguard-vxlan-freebsd/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://it-notes.dragas.net/2024/07/15/bridging-networks-across-vps-wireguard-vxlan-freebsd/</a><a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a> <a href="https://mastodon.bsd.cafe/tags/VXLan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VXLan</a> <a href="https://mastodon.bsd.cafe/tags/Wireguard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Wireguard</a> <a href="https://mastodon.bsd.cafe/tags/Networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Networking</a> <a href="https://mastodon.bsd.cafe/tags/IT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IT</a> <a href="https://mastodon.bsd.cafe/tags/SysAdmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SysAdmin</a> <a href="https://mastodon.bsd.cafe/tags/NoteHUB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NoteHUB</a>

Stefano MarinelliGood morning, friends of the <a href="https://mastodon.bsd.cafe/tags/BSDcafe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSDcafe</a> and <a href="https://mastodon.bsd.cafe/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediverse</a> I'd like to share some details on the infrastructure of BSD.cafe with you all. Currently, it's quite simple (we're not many and the load isn't high), but I've structured it to be scalable. It's based on <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a>, connected in both ipv4 and ipv6, and split into jails:* A dedicated jail with nginx acting as a reverse proxy - managing certificates and directing traffic * A jail with a small <a href="https://mastodon.bsd.cafe/tags/opensmtpd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensmtpd</a> server - handling email dispatch - didn't want to rely on external services * A jail with <a href="https://mastodon.bsd.cafe/tags/redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redis</a> - the heart of the communication between <a href="https://mastodon.bsd.cafe/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a> services - the nervous system of BSDcafe * A jail with <a href="https://mastodon.bsd.cafe/tags/postgresql" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#postgresql</a> - the database, the memory of BSDcafe * A jail for media storage. The 'multimedia memory' of BSDcafe. This jail is on an external server with rotating disks, behind <a href="https://mastodon.bsd.cafe/tags/cloudflare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cloudflare</a>. Aim is georeplicated caching of multimedia data to reduce bandwidth usage. * A jail with Mastodon itself - <a href="https://mastodon.bsd.cafe/tags/sidekiq" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sidekiq</a>, <a href="https://mastodon.bsd.cafe/tags/puma" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#puma</a>, <a href="https://mastodon.bsd.cafe/tags/streaming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#streaming</a>. Here is where all processing and connection management takes place.All communicate through a private LAN (in bridge) and is set up for VPN connection to external machines - in case I want to move some services, replicate or add them. The VPN connection can occur via <a href="https://mastodon.bsd.cafe/tags/zerotier" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#zerotier</a> or <a href="https://mastodon.bsd.cafe/tags/wireguard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wireguard</a>, and I've also set up a bridge between machines through a <a href="https://mastodon.bsd.cafe/tags/vxlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vxlan</a> interface over <a href="https://mastodon.bsd.cafe/tags/wireguard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wireguard</a>.Backups are constantly done via <a href="https://mastodon.bsd.cafe/tags/zfs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#zfs</a> snapshots and external replication on two different machines, in two different datacenters (and different from the production VPS datacenter).<a href="https://mastodon.bsd.cafe/tags/sysadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sysadmin</a> <a href="https://mastodon.bsd.cafe/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tech</a> <a href="https://mastodon.bsd.cafe/tags/servers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#servers</a> <a href="https://mastodon.bsd.cafe/tags/ITinfrastructure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ITinfrastructure</a> <a href="https://mastodon.bsd.cafe/tags/BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSD</a>

Peter N. M. HansteenTunneling vxlan(4) over WireGuard wg(4) <a href="https://undeadly.org/cgi?action=article;sid=20230214061330" rel="nofollow noopener noreferrer" target="_blank">https://undeadly.org/cgi?action=article;sid=20230214061330</a> <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openbsd</a> <a href="https://mastodon.social/tags/vxlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vxlan</a> <a href="https://mastodon.social/tags/wireguard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wireguard</a> <a href="https://mastodon.social/tags/wg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wg</a> <a href="https://mastodon.social/tags/vpn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vpn</a> <a href="https://mastodon.social/tags/tunneling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tunneling</a>

p̻̻̥r̥̻̥o̻j̤͛ec͔t̞dp :verifiedpurple:Currently patching my Proxmox cluster to prep the experimental SDN functionality to enable me to do VXLAN across my cluster of nodes.I want to test this so I can have virtual routers with devices on the same internal networks but spread across multiple physical nodes.I'm familiar with doing this on VMware with dVSes and VLANs but trying to replicate it on Proxmox. If this doesn't work as expected I may end up trying some other options. Hope to solve this in software so I don't have to buy gear.<a href="https://infosec.exchange/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a> <a href="https://infosec.exchange/tags/proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proxmox</a> <a href="https://infosec.exchange/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#networking</a> <a href="https://infosec.exchange/tags/sdn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sdn</a> <a href="https://infosec.exchange/tags/vxlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vxlan</a> <a href="https://infosec.exchange/tags/ovs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ovs</a> <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosted</a> <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a>

heise online (inoffiziell)heise+ | Netzvirtualisierung: VXLAN für standortübergreifende Layer-2-Vernetzung Das VXLAN kombiniert die Vorteile des Routings wie die parallele Nutzung mehrerer Links mit der Möglichkeit, Layer-2-Segmente zu vergrößern. <a href="https://www.heise.de/hintergrund/Netzvirtualisierung-VXLAN-fuer-standortuebergreifende-Layer-2-Vernetzung-4875789.html" rel="nofollow noopener noreferrer" target="_blank">Netzvirtualisierung: VXLAN für standortübergreifende Layer-2-Vernetzung</a> <a href="https://squeet.me/search?tag=Layer-2-Vernetzung" rel="nofollow noopener noreferrer" target="_blank">#Layer-2-Vernetzung</a> <a href="https://squeet.me/search?tag=Netzvirtualisierung" rel="nofollow noopener noreferrer" target="_blank">#Netzvirtualisierung</a> <a href="https://squeet.me/search?tag=VXLAN" rel="nofollow noopener noreferrer" target="_blank">#VXLAN</a> <a href="https://squeet.me/search?tag=VirtualeXtensibleLocalAreaNetwork" rel="nofollow noopener noreferrer" target="_blank">#VirtualeXtensibleLocalAreaNetwork</a> <a href="https://squeet.me/search?tag=Virtualisierung" rel="nofollow noopener noreferrer" target="_blank">#Virtualisierung</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik: