Question regarding #Multicast, especially with #IPv6: Is there any concept of signaling the availability of multicast route(r)s to hosts / potential listeners?
On #Linux I see it as a usability issue/bug that I have to manually type "ip -6 route add ff1e::/16 dev wlp1s0 table local". Otherwise, even for routeable mulicast addresses, listeners will be installed on the first non-localhost interface by default. Which for me is br0, not wlp1s0.
If I announce ff7e::/64 via uradvd (it doesn't even allow using /16...) it gets added to the default table on #Linux. While it would be needed in the "local" table instead, so this is not working.
Also in #NetworkManager when adding routes in there manually I cannot select the table.
And I can't use a netmask for #IPv6 (#multicast) routes either? Like "ip -6 r add ff7e::/ff0f:: dev wlp1s0 table local"?
So I need to add 16 routes (or even 5*16 even considering all routeable multicast scopes)?
Also, whenever my laptop goes into standby and wakens up again, #NetworkManager has forgotten all these multicast routes I had manually added.
Generally all this is not a big issue for me myself. But for a mass adoption of #IPv6#multicast, by non-technical people, it seems that this might need a solution? Or did I miss one?
@wonka good question. Right no it looks like #NetworkManager can't do that, as written before. For the manual route table selection that should probably be added.
For any automatic multicast route additions, I'm so far still not sure what would need fixing (all kinds of network managers? or the #Linux (and other OSes) #IPv6 stack? or RFCs?)
Di cosa dovrei #incazzarmi di più: del fatto che ormai da mesi — e in questi ultimissimi giorni la #storia è peggiorata #tragicamente, https://octospacc.altervista.org/wp-content/uploads/2024/02/image-7.png — la linea #Internet di casa salta di continuo, mettendo da sé continui bastoni tra le ruote al mio workflow… o del fatto che quando collego il telefono via tethering USB il mio sistema desktop sembra non essere sempre in grado di routare correttamente i pacchetti — in certi casi capisce che deve farli passare attraverso il telefono sennò non vanno da nessuna parte, ma altre volte si ostina a mandarli al mio bridge ethernet? #MANNAGGIA!!! 🗡️🗡️
È una domanda retorica, ovviamente; mi #incazzo più con #Vodafone, che mio padre paga per farci avere in cambio un servizio che dire #scadente è fargli un complimento, di quanto mi possa mai arrabbiare contro un software no-profit per un #problema che posso aggirare praticamente scollegando dei cavi. Però davvero non ne posso più, non solo questo comportamento mi ruba tempo quando lavoro al PC, ma mi manda pure giù le cose che ospito sul serverino in casa, e che palle. 😭️
Ogni tanto ricordo di questo bordello a mio padre, ma fino ad ora ancora non l’ho convinto a provare a comprare un #router nuovo, uno vero con cui rimpiazzare quel rottame della #VodafoneStation… lui dice che probabilmente i problemi sono sulla linea, e in parte anche io credo sia così (ma chissà quale segmento della linea!); però se anche così fosse il caso, resta comunque indecente il fatto che, mentre il #collegamento alla WAN si scollega e il #modem tenta di ricollegarsi, la Station non è nemmeno in grado di roteare pacchetti in LAN… cioè, fai ping e avoja ad aspettare, non risponde. È evidente che pure il #software che sta lì sopra fa schifo, mica solo la linea. E-waste puro. 💀️
@ffmancera presented in the @fosdem#Distributions DevRoom today about how not to break Linux distros when building a project that several distributions rely on.
What in the absolute fuck? #RaspberryPi no longer supports configuring your wifi directly, from bookworm on you need to use fucking cloud-init?!@ Are you shitting me?
Where is the configuration file that doesn't need a custom tool? Stop with this shit.
@jpaskaruk
Yes, nmtui is in curses. It uses bar characters to show the strength of connection for available wireless networks; I recommend that you try it for your RPi.
It's a shame that it's not simpler to set up networks with GNU/Linux. But in fairness the current system with #NetworkManager is designed to keep a computer connected if wifi drops, if you carry your laptop to a café, etc. It's more complex than what you need for simple cases, but it does handle the general.
Hier übrigens der deutsche Screenshot, wie man das #37c3#WLAN manuell unter #GNOME / #Ubuntu / #Fedora und co (anderen #Linux Distributionen) konfiguriert.
Ich hab böse Probleme nach dem Debian Update auf 12.4.
Der vermtl. Networkmanager lässt das ganze System einfrieren. Nichtmal eine andere Konsole ALT+F1 geht mehr. Nur noch ein HardShutdown geht, löst aber nicht die Ursachen.
Restarting your apps while the network is offline makes you realize some things are silly… like needing to click the Reload button in #web#browsers' error pages, when they very well know when the operating system is fully back online anyway.
Therefore, I filed a request for #GNOMEWeb / #Epiphany to do that for me when #GNOME / #NetworkManager signals that online connectivity has been restored: https://gitlab.gnome.org/GNOME/epiphany/-/issues/2230
#NetworkManager 1.44.2 is out now with better log IPv4 Address Conflict Detection (ACD) conflicts, the ability to honor the CLICOLOR_FORCE environment variable and to allow missing default gateway with oFono. Get it from your distro's repositories!
Check the new "Donation list" to support your favourite free and open source software.
It includes all the #donation links with all the listed #tutorials and #services we provide.
@tbernard Evolution and GNOME Software are already capable of handling #NetworkManager's "metered connection" property; would be nice if #Epiphany and #Firefox would take this into account and load less stuff (but what?)
How to connect to protonvpn via openvpn
Protonvpn has some instructions to connect via openvpn:...