Post B2aOOn3jbEja2kOfGS by jana@social.jsteuernagel.de
 (DIR) More posts by jana@social.jsteuernagel.de
 (DIR) Post #B0qXoXECKUUjjOLfWa by jana@social.jsteuernagel.de
       2025-12-02T17:49:19Z
       
       1 likes, 0 repeats
       
       Tried to install the Unifi Gateway Lite.But as per usual Unifi shenanigans, PPPoE just didn’t manage to establish a connection.And because I had changed the credentials in an attempt to fix it, the old USG also didn’t connect anymore.So what saved the day for the moment? The modem. Turned on PPPoE in the Vigor 130, gave it the credentials, et voila, it immediately established a PPPoE connection and everything worked.Why again did I think buying another Unifi router was a good idea? :neobot_angry:
       
 (DIR) Post #B0qXodnVu6JE6euxP6 by jana@social.jsteuernagel.de
       2025-12-02T18:11:48Z
       
       1 likes, 0 repeats
       
       Definitely not related (/s):I have just requested a return of that piece of shit and bought a different router :neobot_thumbsup:
       
 (DIR) Post #B0qXpMDwjBb3tNcgiG by rez@social.ultimaterez.com
       2025-12-02T17:52:58Z
       
       1 likes, 0 repeats
       
       @jana I legitimately used to love Unifi stuff - I bought a bunch of it for my new house when I moved in. Now they've changed so much from the company that I used to know that I can never recommend. So sorry to hear that you had such a rotten experience.
       
 (DIR) Post #B0wmN4pcSm3q6SycS0 by jana@social.jsteuernagel.de
       2025-12-05T18:43:56Z
       
       0 likes, 0 repeats
       
       Okay, after being so terribly disappointed with the Unifi Gateway Lite, my Mikrotik hEX S just arrived today!I just pre-configured it (a joy) and now the only thing left is to hope that PPPoE will just work, like it did on the Vigor.
       
 (DIR) Post #B0wmN5zEAXLBgYTo48 by jana@social.jsteuernagel.de
       2025-12-05T18:47:11Z
       
       1 likes, 1 repeats
       
       OMG, there is a Prometheus exporter for Mikrotik stats!And it even advertises how to set it up on FreeBSD, right in the README.I need to check that out, that looks so cool :ohttps://github.com/akpw/mktxp
       
 (DIR) Post #B2aOOjmFnly7rfCA6K by jana@social.jsteuernagel.de
       2025-12-05T19:18:41Z
       
       0 likes, 0 repeats
       
       Put the Mikrotik in place, moved the VLAN tagging from the modem to the router aaaand it worked.That was so simple.This is how a router should work.
       
 (DIR) Post #B2aOOkwvRa6DV3CCNE by jana@social.jsteuernagel.de
       2025-12-05T19:23:12Z
       
       0 likes, 0 repeats
       
       Even IPv6 just works.Wow.I shouldn't be so surprised by a router just working, but I am.This is great.
       
 (DIR) Post #B2aOOlZZ7v0XQtH3bM by jana@social.jsteuernagel.de
       2025-12-05T20:50:31Z
       
       0 likes, 0 repeats
       
       I got stuck debugging an issue where I thought IPv6 on the router itself wasn't working, because I couldn't even ping my monitoring host and certainly not establish a Wireguard tunnel.But upon further analysis it seems like I only can't reach that particular subnet, rejected by a some Telekom router :neobot_confused:
       
 (DIR) Post #B2aOOmGSYRJpZvLJSa by jana@social.jsteuernagel.de
       2025-12-10T13:33:50Z
       
       0 likes, 0 repeats
       
       I dug a bit deeper on the funky connection issue from a DTAG line to my monitoring server.@domi had already confirmed to me that the EPIX exchange regularly has some funkies with IPv6, so now I wanted to figure out whether this was a regional thing, or the entirety of the DTAG network just doesn't know how to reach the target.And after I got a generous donation of RIPE Atlas credits to use, I was able to determine just that! (thanks @arch :3)I ran a probe with a mix of 25 AS3320 (DTAG) nodes and some random worldwide ones.None of the AS3320 were able to reach my target.I ran another test with 50 random nodes from Germany and another 50 worldwide.Some tests from around the world failed, which all don't seem particularly relevant to me.In Germany? Successful connections from Telefonica, Vodafone, 1&1, Oracle, Netcup, Hetzner, Deutsche Glasfaser, multiple regional providers and even randomly an OpenFactory node.Who once again didn't manage a single successful connection? DTAG!IPv4 on the other hand works fine. Even shows a lot less failures around the world.So yeah, don't know who to blame here, but I was able to confirm that the entirety of the DTAG network has no idea how to reach my monitoring server via IPv6. Fun :neobot_woozy:
       
 (DIR) Post #B2aOOn3jbEja2kOfGS by jana@social.jsteuernagel.de
       2026-01-23T19:09:31Z
       
       1 likes, 3 repeats
       
       Remember when in December I had a bit of a debug session why I couldn't reach my monitoring server via #IPv6 from a DTAG internet line?Well, this later motivated @domi to dig a bit deeper and it ended up with @q3k sending some emails to EPIX, DTAG and Lumen about it, as it was obviously a bigger issue of an entire /32 IPv6 prefix from Lumen not being accepted by DTAG.The issue ended up being escalated multiple times and it seemed to take them quite a while to figure out what was wrong.But as of today (or recently, today is when I got note of it), it works!DTAG now accepts the 2a0d:eb00::/32 prefix, which they previously rejected due to, supposedly, an incorrectly documented Lumen AS-SET in the RIPE DB.This is certainly not the escalation I expected after I connect to my server back then :neobot_giggle: