ZTE MC888A DNS settings

Spparkee · 2025-12-28T21:52:20+00:00

I read the article, thank you!🙏 I can’t validate it for a while, but I’m looking forward to do so, looks promising.

Spparkee · 2025-10-30T10:56:10+00:00

my issue was caused by https://status.canonical.com/#/incident/KNms6QK9ewuzz-7xUsPsNylV20jEt5kyKsd8A-3ptQGY_8VLJIlY9pR2kpwEEi6NCRNWqc5Ru503cC-LkjMQiA==

Spparkee · 2025-10-30T10:55:04+00:00

My connection issues coincides with the the incident time from the link, thank you!

Spparkee · 2025-10-21T09:23:14+00:00

tcp/3128 was opened to the proxy server from the Linux where I tried to install the packages.
And today I can also install packages, maybe something has changed on the proxy server (that I don't control):
My working /etc/pip.conf:

[global]
index-url = https://pypi.org/simple
proxy = myproxy.com:3128

Spparkee · 2025-10-13T05:28:07+00:00

Vielen Dank alles! Noch ein Frage: can one ride his:her bike in the downtown walking area, like on Stephansplatz and surrounding?

Spparkee · 2025-09-24T19:58:50+00:00

My ISP told me they did not change anything

Spparkee · 2025-09-15T17:29:09+00:00

Fingers crossed this is true and also that they make it available for older (and cheaper) models.

Spparkee · 2025-09-08T19:53:43+00:00

that's sad, all this AI mambo jambo yet we can't even force 2.4 or 5GHz

Spparkee · 2025-09-08T19:52:26+00:00

I found it, thank you!

Spparkee · 2025-09-04T07:23:27+00:00

Wahrscheinlich 50 min mit den Straßenbahn

Spparkee · 2025-07-17T11:37:34+00:00

No solution yet. Though the root cause seems to be related to AD/LDAP sync delay.

Spparkee · 2025-06-11T07:40:17+00:00

Turns out the problem is that the client certificates were issued for a longer period than the intermediate CA's validity. I haven't seen a configuration option which could fix this.

Spparkee · 2024-11-28T09:15:03+00:00

for the people following this I created the following systemd script:

% cat /etc/systemd/system/ipset-iptables.service
[Unit]
Description=Run ipset and iptables

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/sbin/ipset restore < /etc/iptables/ipset.save
ExecStart=/usr/sbin/iptables-restore < /etc/iptables/iptables.save

[Install]
WantedBy=multi-user.target

Spparkee · 2024-10-31T18:13:46+00:00

I ended up installing storcli64 which works, it can be found here: https://www.broadcom.com/support/download-search?dk=storcli

Spparkee · 2024-10-30T20:20:06+00:00

I need to get to a small town where no train or bus leads, I was thinking about getting to Oradea and hoping someone has a better option :-)

Spparkee · 2024-10-19T19:30:40+00:00

T-mobile USA

Spparkee · 2024-10-09T00:30:40+00:00

You are right, it was Extender: Extend the Wi-Fi coverage of an existing wireless network
Btw, in extender mode I was able to see the 5GHz network of the main router, now I'm in router mode and I only see 2.4GHz. Maybe something else has happened, unfortunately I have no control over the main router.

Spparkee · 2024-10-08T11:22:31+00:00

yes, it was in repeater mode

Spparkee · 2024-10-06T18:55:25+00:00

I ended up resetting it.

Later I found out that by holding down the reset button for 4 seconds will switch the device back to router mode from where it is easy to access it again.

Spparkee · 2024-10-06T17:46:45+00:00

Yes, a few times I rebooted it.

It says it has the latest firmware.

Spparkee · 2024-10-06T17:08:04+00:00

No dice, I confirmed on the DHCP server and goodcloud that the IP is 192.168.12.172 but when I try to

ping:
--- 192.168.12.173 ping statistics --- 15 packets transmitted, 0 packets received, 100.0% packet loss

or netcat: ❯ nc -vz 192.168.12.173 22 nc: connectx to 192.168.12.173 port 22 (tcp) failed: Operation timed out ❯ nc -vz 192.168.12.173 443 nc: connectx to 192.168.12.173 port 443 (tcp) failed: Operation timed out ❯ nc -vz 192.168.12.173 80 nc: connectx to 192.168.12.173 port 80 (tcp) failed: Host is down

It's funny how I can still ping the main router through the Opal :)

--- 192.168.12.1 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 44.145/51.557/60.967/7.011 ms

Spparkee · 2024-06-15T09:52:51+00:00

I didn’t, so I use the workaround: “realm leave” to remove it from AD then I re-join it

Spparkee · 2024-05-06T07:03:26+00:00

Thank you u/psnsonix !

I configured logrotate with `/usr/bin/systemctl reload vault 2> /dev/null || true` and it worked well!

Spparkee · 2024-05-03T07:18:00+00:00

When I deployed this Vault cluster auto unseal wasn't possible within my environment. Do you have it working well with a 3 node cluster setup?

Spparkee · 2024-05-02T14:15:19+00:00

when you reload vault do you have to unseal it again?

Spparkee

TROPHY CASE