Mastodon 🐘

Jonathan B ✈️🪄👨🏻‍💻Does anyone have any experience of the Ubiquiti UniFi USW-LITE-8-POE Switch (USW-LITE-8-POE)? I’m thinking of swapping out the two Netgear switches I use for two of these so that I can power a new Zigbee adaptor and my Wifi AP with POE and use VLANs etc to split off my IoT stuff properly.Can I connect the two directly together? I have two cupboards with my various network bits in linked with a network cable (that I wouldn’t want to put POE over)<a href="https://mastodon.me.uk/tags/ubiquiti" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ubiquiti</a> <a href="https://mastodon.me.uk/tags/unifi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unifi</a> <a href="https://mastodon.me.uk/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#networking</a> <a href="https://mastodon.me.uk/tags/poe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#poe</a> <a href="https://mastodon.me.uk/tags/vlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vlan</a>

Grzegorz Surmann :verified:Juniper SP/Enterprise Config <a href="https://blog.funil.de/4264/sinuspl/english/juniper-networks/juniper-sp-enterprise-config/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blog.funil.de/4264/sinuspl/english/juniper-networks/juniper-sp-enterprise-config/</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/enterprise" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#enterprise</a> <a href="https://mstdn.funil.de/tags/interface" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#interface</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/provider" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#provider</a> <a href="https://mstdn.funil.de/tags/service" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#service</a> <a href="https://mstdn.funil.de/tags/style" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#style</a> <a href="https://mstdn.funil.de/tags/vlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vlan</a>

bituur esztreymsous quel type de feuilles le p'tit bout allait-il de ce pas s'installer ? regarde !. :: <a href="https://pouet.chapril.org/tags/haiku" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#haiku</a> <a href="https://pouet.chapril.org/tags/nawak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nawak</a> <a href="https://pouet.chapril.org/tags/vlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vlan</a> v'lan <a href="https://pouet.chapril.org/tags/zendefond%C2%BA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#zendefondº</a>

Yehor 🇺🇦I finally have a separate guest WiFi network with a QR code on a fridge. And a separate IoT network. Even made the printer work across VLANs. And <a href="https://techhub.social/tags/Plex" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Plex</a> to stream locally. Because the app is on the <a href="https://techhub.social/tags/Samsung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Samsung</a> TV, and I don’t trust it, so it is also on the IoT network. The only thing left to be fixed is <a href="https://techhub.social/tags/AirPlay" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AirPlay</a> on the TV. <a href="https://techhub.social/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a> <a href="https://techhub.social/tags/network" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#network</a> <a href="https://techhub.social/tags/vlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vlan</a> <a href="https://techhub.social/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#networking</a>

T_XCurse you, <a href="https://chaos.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> bridge (or <a href="https://chaos.social/tags/DSA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DSA</a> or <a href="https://chaos.social/tags/switchdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#switchdev</a>) - why do you send this uncalled-for <a href="https://chaos.social/tags/VLAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VLAN</a> deletion notification... (and do I dig deeper into this, maybe finding a bug?, or should I just go for the other approach I wanted to implement anyway, which wouldn't need to hook into the VLAN notifications in the first place...)<a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> <a href="https://chaos.social/tags/rtl83xx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rtl83xx</a> <a href="https://chaos.social/tags/switch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#switch</a>

Makenshi FoxThis week I will be replacing my router (<a href="https://blimps.xyz/tags/Ubiquiti" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ubiquiti</a> <a href="https://blimps.xyz/tags/Edgerouter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Edgerouter</a> Lite) with an Alta Labs <a href="https://blimps.xyz/tags/Route10" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Route10</a>. The ERL has been great, but there is one specific condition which causes severe performance issues. The ERL can offload <a href="https://blimps.xyz/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a>, <a href="https://blimps.xyz/tags/vlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vlan</a> and <a href="https://blimps.xyz/tags/pppoe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pppoe</a> at 1gbs, but not all at once. So, if you try to transfer a lot of ipv6 traffic, it drops to software and it then affects all traffic passing through. The main "culprit" is Steam which prefers ipv6 (as it should!) The new router should not have that limitation.

T_XThe <a href="https://chaos.social/tags/VLAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VLAN</a> code in the <a href="https://chaos.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> bridge gives me some headaches. Took me a while to get why two brmctx <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> contexts are created, one for the untagged VLAN 0, one for the PVID 1. But only the former would be used, with brmctx->vlan not set, even though VLANs were configured. Turns out you need to not only enable multicast_snooping but also mcast_vlan_snooping. And confusingly, only the former is in sysfs. Seems like "ip link" is the most complete thing now, not "brctl", "bridge" tool or sysfs

bentasker.co.uk FeedNew <a href="https://mastodon.bentasker.co.uk/tags/Blog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Blog</a>: Isolating our Guest Wireless Network in OPNSense Author: Ben Tasker<a href="https://www.bentasker.co.uk/posts/blog/house-stuff/creating-isolated-ipv4-and-ipv6-networks-with-vlans-and-opnsense.html?utm_source=rss" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.bentasker.co.uk/posts/blog/house-stuff/creating-isolated-ipv4-and-ipv6-networks-with-vlans-and-opnsense.html?utm_source=rss</a><a href="https://mastodon.bentasker.co.uk/tags/aaisp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aaisp</a> <a href="https://mastodon.bentasker.co.uk/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#networking</a> <a href="https://mastodon.bentasker.co.uk/tags/opnsense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opnsense</a> <a href="https://mastodon.bentasker.co.uk/tags/vlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vlan</a> <a href="https://mastodon.bentasker.co.uk/tags/wireless" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wireless</a>

Richard HectorQuestion for <a href="https://mastodon.nz/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#networking</a> friends:I have 3 <a href="https://mastodon.nz/tags/VLAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VLAN</a> switches. My incoming Internet is adjacent to one of them, but I don't really want anything else much there. Most of my equipment is on the third switch in the chain - ie traffic to there from the internet has to go through all three. Currently my router (<a href="https://mastodon.nz/tags/Debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debian</a> <a href="https://mastodon.nz/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> box) is next to the Internet connection, but I want to move it to the other end. Is that sane?

Paula Gentle on FriendicaEs hat den ganzen verschissenen Tag gedauert, aber VLAN-Config per File und ein Uplink auf Port 22 mit allen <a href="https://libranet.de/search?tag=VLAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VLAN</a> tagged scheine ich hinbekommen zu haben.Nächster Schritt: Trunk mit zwei NICs, um das Ding direkt an die <a href="https://libranet.de/search?tag=pfSense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pfSense</a> anzuschliessen. Dann kann ich endlich den uralten und chronisch überfüllten 24x <a href="https://libranet.de/search?tag=Switch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Switch</a> unterbrechungsfrei ausmustern, der immer noch mein Hauptswitch ist. Dessen Ableben ist ein Damoklesschwert über meiner heimischen IT-Landschaft, dessen Auflösung ich schon seit Jahren vor mir her schiebe. Bin ja kein Netzwerker und <a href="https://libranet.de/search?tag=JunOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JunOS</a> ist jetzt nicht so intuitiv.Der <a href="https://libranet.de/search?tag=Juniper" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Juniper</a> 3400 ist deutlich jünger und hat einen erheblich geringeren <a href="https://libranet.de/search?tag=Stromverbrauch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Stromverbrauch</a>, trotz doppelt so vieler Ports. Danach kann die Serverlandschaft weiter wachsen, die <a href="https://libranet.de/search?tag=Weltherrschaft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Weltherrschaft</a> ist nahe...<a href="https://libranet.de/search?tag=Network" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Network</a> <a href="https://libranet.de/search?tag=EinmalMitProfis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EinmalMitProfis</a>

Johannes KastlEdit: Seems like this was caused by hardware offloading being enabled, which worked fine on 22.x. I am investigating why this is no longer working, but for now I have a working internet connection again! Hooray!Dear <a href="https://digitalcourage.social/tags/OpenWRT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenWRT</a> users out there,I migrated my main router to 24.10.0 (direct update from 22.x was not possible). I got almost everything working again, VLANs, DDNS.But now I got a funny issue: Connections via LAN are NOT working. Connections via Wifi directly on the router ARE working. Connections via Wifi on the access point are NOT working.Ping and DNS queries (with both TCP and UDP) are working fine from all clients to all hosts I tried.But trying to curl a website (or open it in a browser) only works on clients connected via Wifi to the router. As soon as LAN comes into play, the connection hangs until "empty reply from server".Any ideas anyone?<a href="https://forum.openwrt.org/t/connection-issue-after-migration-to-24-10-0-router-can-curl-a-url-clients-cannot/226424" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://forum.openwrt.org/t/connection-issue-after-migration-to-24-10-0-router-can-curl-a-url-clients-cannot/226424</a> <a href="https://digitalcourage.social/tags/openwrt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openwrt</a> <a href="https://digitalcourage.social/tags/router" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#router</a> <a href="https://digitalcourage.social/tags/vlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vlan</a> <a href="https://digitalcourage.social/tags/wifi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wifi</a> <a href="https://digitalcourage.social/tags/adminlife" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#adminlife</a> <a href="https://digitalcourage.social/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a>

Martin 🇪🇺Hat hier wer ne Idee? <a href="https://norden.social/tags/Proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Proxmox</a> <a href="https://norden.social/tags/Homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Homelab</a> <a href="https://norden.social/tags/Network" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Network</a> Ich habe 2 VLANs: 1 & 6. Zukünftig soll alles im Homelab in das <a href="https://norden.social/tags/VLAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VLAN</a> 6 umziehen - dauert noch etwas. Ich hab ne neue Diskstation. Die alte soll im Homelab als Speicher dienen, daher steht sie im VLAN 6. Einige LXC hab ich schon ins VLAN 6 umgezogen. Der Proxmox Host steht noch im VLAN 1. Aus irgendeinem Grund kann der Host mittels Ping keinen Client aus dem VLAN 6 erreichen - und somit auch die Diskstation nicht. Warum?

James Wynn 🧐I recently rebuilt my networks and segregated devices into proper VLANs and everything was working great until I tried to connect to <a href="https://mastodon.social/tags/ProtonVPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ProtonVPN</a>. I tried tweaking all the different settings and could not get it to connect reliably if at all. Finally figured it out. They use 10.2.0.0 for their VPN subnet, which was the same one I was using for my client <a href="https://mastodon.social/tags/VLAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VLAN</a>. So now I get to rebuild stuff again. Ugh.<a href="https://mastodon.social/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#networking</a>

Michael T BabcockDo I expect the average home user to understand these things? No. But could devices have better default options? Certainly yes. Business class switches already have Voice <a href="https://floss.social/tags/VLAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VLAN</a> auto-detect by MAC OUI -- there's no reason not to add a little more fairy dust and help home users keep their stuff separated intelligently while still enjoying the benefits of insecure <a href="https://floss.social/tags/IoT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IoT</a> devices. Some day maybe it will be normalized to hire a pro to install these things, but until then ... <a href="https://floss.social/tags/sysadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sysadmin</a> <a href="https://floss.social/tags/networkSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#networkSecurity</a>

donkardosIn a neighboring office, there is a device (some kind of smart Tuya gadget based on the MAC) that keeps trying to connect to our WiFi router. ``` hostapd: phy1-ap0: STA d8:d6:68:... IEEE 802.11: authenticated ``` We have fired and disabled it.(For some reasons not specified here, it is not an option to go over and ask them what it is.)Is there anything we can do about this? How common is this sort of thing?<a href="https://mastodon.social/tags/tuya" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tuya</a> <a href="https://mastodon.social/tags/vlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vlan</a> <a href="https://mastodon.social/tags/attemptedAttack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#attemptedAttack</a>

lebochequiritFür's Heimnetz hinter der opnsense nen gebrauchten managed Switch von netgear, der out-of-support ist. Yay or nay? <a href="https://social.tchncs.de/tags/askfedi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#askfedi</a> <a href="https://social.tchncs.de/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a> <a href="https://social.tchncs.de/tags/vlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vlan</a> <a href="https://social.tchncs.de/tags/netgear" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#netgear</a>

Kevin Karhan :verified:<a href="https://bsd.network/@dvl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dvl</a> hmm...Not shure if <a href="https://infosec.space/tags/LAGG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LAGG</a> works across different LANs.<ul><li>Usually one LAGGs physical interfaces instead of <a href="https://infosec.space/tags/VLAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VLAN</a>, so the <a href="https://infosec.space/tags/VLANs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VLANs</a> just get transparently spread across the overlay'd LAGG.</li></ul>I guess one would have to setup Inter-VLAN routing instead...

毛茸茸生长 :trans_flag:弱电箱到客厅只有一根网线的解决方案: 交换机单线复用设置教程 <a href="https://www.acwifi.net/29419.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.acwifi.net/29419.html</a><a href="https://bgme.me/tags/%E6%88%91%E5%9C%A8%E7%9C%8B%E4%BB%80%E4%B9%88" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#我在看什么</a> <a href="https://bgme.me/tags/IPTV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPTV</a> <a href="https://bgme.me/tags/vlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vlan</a> <a href="https://bgme.me/tags/%E6%95%99%E7%A8%8B" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#教程</a>

Jez Caudle :verified:I’m looking for a wireless access point that supports VLANs - in the sense that I can create different SSIDs for different VLANs or I can specify which client goes onto which VLAN. Any help appreciated as I’m drowning in marketing fluff at the moment. And boosts always appreciated. <a href="https://infosec.exchange/tags/wifi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wifi</a> <a href="https://infosec.exchange/tags/vlans" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vlans</a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#infosec</a> <a href="https://infosec.exchange/tags/vlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vlan</a>

FotografiosoAls einzige Einschränlung: ich habe die Firewall nicht nach „best practice“ aufgesetzt (also: erstmal alles verbieten und dann Löcher reinbohren), sondern erstmal komplett das Routing erlaubt zwischen den Netzwerken und dann gezielt den Zugriff auf bestimmte Ports im LAN aus dem IoT gesperrt. Für bestimmte IP Adressen, wie das NAS sind alle Ports gesperrt. (5/x) <a href="https://chaos.social/tags/IoT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IoT</a> <a href="https://chaos.social/tags/VLAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VLAN</a>

Recent searches

Search options

Administered by:

Server stats:

#vlan