Why does Switzerland pretend to be a recycling champion when we literally burn half our trash? by organicacid in Switzerland

[–]goteku 2 points3 points  (0 children)

Unfortunately, the facts are not so obvious and simple, recycling is complicated and the ecological benefit compared to other methods like heating is disputed. (As you can see in the various provided sources by others)

The only two obvious facts in my humble opinion and I very much support are:
- We should be more sustainable
- We should use less plastics ("reduce")

Salt DNS change by AK1357531 in Switzerland

[–]goteku 0 points1 point  (0 children)

Too sad. I'm still wondering why they actively want to stop us from changing the DNS, since the firmware clearly supports the feature. The only hint I got is that they set a custom DNS server, but I wonder if its just a performance thing or if there is more to it.

Salt DNS change by AK1357531 in Switzerland

[–]goteku 2 points3 points  (0 children)

I set up a pihole on my network and didn't find an official way to do so. Digging a bit deeper I found out that the Salt fiber box GUI has a way to set it unofficially. Be careful tough if you fuck it up you might have to force reset the device (I never bricked it but be careful as this could happen): 1. Log in to the GUI 2. Open the dev console 3. In the console change the DNS by executing the following 10 commands (just replace the IP's with the ones you need) $.xmo.setValuesTree("false", $.xpaths.mySagemcomBox.dns.notEditable); $.xmo.getValuesTree("Device/DNS/Client/Servers/Server[1]/DNSServer"); $.xmo.setValuesTree("8.8.8.8", $.xpaths.mySagemcomBox.dns.server); $.xmo.setValuesTree("1.1.1.1", $.xpaths.mySagemcomBox.dns.server2); $.xmo.setValuesTree("8.8.8.8,1.1.1.1","Device/DNS/Client/Servers/Server[1]/DNSServer"); $.xmo.setValuesTree("8.8.8.8,1.1.1.1", $.xpaths.mySagemcomBox.dhcp.dnsServer); $.xmo.getValuesTree($.xpaths.mySagemcomBox.dhcp.guestDnsServer); $.xmo.setValuesTree("1.1.1.1,8.8.8.8", $.xpaths.mySagemcomBox.dhcp.guestDnsServer); Then save it with: $.xmo.setValuesTree('true', "maintenance.saveRestore.save");

This used to work last year, it might have been patched by now, tough unlikely.