I checked this route but fiber modem are currently rare. There are only few WiFi 6/7 routers which accepts fiber.
My ISP on the other hand is quite friendly. They initially provided me with a fiber modem, which sucked as it was quite old, so I told them to give me a simple modem as I have my own ethernet wifi router. They replaced it the next day.
Any way to figure this out? The modem they have provided looks like a layer 2 bridge, i.e., it just converts optical frames to ethernet frames. The login/auth process happens on my router.
Honestly the network card that you will probably need might already pull more than the modem
I eventually want to learn OPNsense, play with VLANs, per-device monitoring, adblocking right at the firewall itself. I will purchase a PC for the firewall for sure. So was thinking would it be better if adding an SFP to it would future proof it. But power is a concern.
This is something I completely forgot to account for. I heard that some SFP modules (10G) can consume a lot of power. I think the devices are pretty low powered. I'll have to get a smartmeter and rethink the setup. Thanks a lot!
Does accessing your router page via caddy work when you’re actually on your home network
Unfortunately no, which rules out an issue with wireguard.
Have you tried a different web browser to rule out your LLM suggested cookie issues
It's not the stale cookie issue which goes away when opening a website in incognito. I think it expects the cookie to have the original host information.
Let me paste the list of issues the LLM mentioned. The following section is from the LLM
<LLM>
The router’s web UI expects the original hostname (e.g., 192.168.0.1) and builds redirects or CSRF tokens based on it. Caddy sends its own host (myproxy.example.com).
Authentication cookies are set for the original domain and may be dropped or rewritten by the proxy, causing the server to think the user is unauthenticated.
The router returns Location: http://192.168.0.1/... which points the browser back to the internal address, bypassing the proxy.
Tokens are generated using the Origin or Referer header; the proxy changes these, making the token invalid on POST.
The router forces HTTPS or blocks HTTP when it sees a mismatch, and Caddy may be terminating TLS while the upstream expects plain HTTP.
Some admin UIs use WebSocket for status updates; if Caddy doesn’t forward the upgrade, the page may reload to the login screen.
The router’s UI may be served from / but expects relative paths; Caddy’s uri rewrite can break those links.
</LLM>
It has also mentioned some solutions for each cause. But I don't want to blindly apply them without knowing what is wrong.
Nothing is exposed to public, other than my wireguard port. I'm running caddy internally. All DNS entries are local only. The router login page cannot be accessed from outside.
When the next generation of DC come online the cost of per bot will continue to tumble to the point where it won’t cost much to turn even Lemmy into a bot ridden wasteland.
I don't see that happening anytime soon. Unlike reddit, this is federated and unmonetized. Bots will be scraping it, but why will they be posting?
I myself run all my services over wireguard. But I run ssh natively though but with extra hardening (fail2ban/sshkey/no default port/max retries, etc). Plus my IP changes every 24 hours. However, I did learn how to setup online services and this can be a stepping stone.
If one is experimenting, exposing the port is fine (temporarily). But if someone is running a service 24/7 over the internet, and the person does not have any cyber security acumen, wireguard is the clear winner.
If you tell me what kind of hardware you have, i can direct you to the correct resource. I have done it for my TPLink router, which has support for noip.com. OpenWRT/OPNSense has dedicated plugins or it's baked-in.
Holy sheet! Looks like my homelab is booked for this entire year.