path is part of the http protocol. Most firewalls only parse the first couple layers (ethernet->ip->tcp/udp), not http as well, unless they do deep package inspection. Idk if openwrt/banip has functionality

I don’t think openwrt can do this. Im running k3s with nginx as ingress but the issue is it doesn’t see the actual ip but rather the ip of the container so i can’t use nginx to block countries.

That is what i currently have setup but cert-manager is giving me a headache and not working correctly so im looking into http instead since its easier to setup

Oh that is actually a great idea thanks!

Very valid point.

Im actually running k3s on it so im not looking for any NAS specific OS. But if i picked a more general OS like fedora this issue might not have appeared. The reason i picked Alpine is since everything is running in containers i don’t need any fancy OS i just need to install k3s. But apperently Alpline can cause some issues :D

Oh i just did ethtool -I eth0 and now it does show up as being able to do 1G.

k3s-alpine-lap-6:~# ethtool -I eth0
Settings for eth0:
	Supported ports: [ TP	 MII ]
	Supported link modes:   10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	Supported pause frame use: Symmetric Receive-only
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	Advertised pause frame use: Symmetric Receive-only
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Link partner advertised link modes:  10baseT/Half 10baseT/Full
	                                     100baseT/Half 100baseT/Full
	                                     1000baseT/Full
	Link partner advertised pause frame use: No
	Link partner advertised auto-negotiation: Yes
	Link partner advertised FEC modes: Not reported
	Speed: 1000Mb/s
	Duplex: Full
	Auto-negotiation: on
	master-slave cfg: preferred slave
	master-slave status: slave
	Port: Twisted Pair
	PHYAD: 0
	Transceiver: external
	MDI-X: Unknown
	Supports Wake-on: pumbg
	Wake-on: d
	Link detected: yes
	Link Down Events: 2

As additional troubleshooting step i connected a know working device to the cable and was able to get 1GB

1. Im not 100% certain but I assume yes. Im trying to set it up as a nas. I just did setup-alpine, rebooted it and placed it in my basement. It should have services consistently running on it like sshd, k3s, … which become unavailable/available every few minutes.
2. Except for a keyboard that i used for troubleshooting no usb devices are connected. Should i attach an usb to see if it gets unmounted?
3. I notices this aswell which i quite strange since it is connected using a cat 5.e cable which should be able to do 1G. The cable is connected to a gigabit switch so that also shouldn’t be the problem. Asfar as cabling and switching is concerned everything should be able to do 1G

If you need additional information let me know!

I did the step i mentioned above but this wasn’t able to solve my issue :(

Thanks for your reply! This is a path i wanna look into. Just to confirm that im understanding correct running /sbin/modprobe -i r8169 && sleep 1 && /usr/sbin/ethtool --set-eee eth0 eee off and then rebooting is what i should try right?

Additional information im on Alpine 3.22.3. If this is an Alpine specific issue im able to switch distros but i prefer not to if it isn’t needed.

1. simply don’t run an exit node (from home)
2. run you relay no mether the type of a cheap vps that’s tor friendly

Oh alright, thanks a lot for your explanation. I learned a lot, im going with the operator route!

Thank you for your help!

Thanks for your response, could you explain what the advantages of an operator are in this example?

And what is the matter with the licensing? I never heard this issue before.

The link that you attached looks like it is for the pgvecto.rs extention instead of vectorchord.

Ceph is really cool, i also wanna use it in the future but i need way more disks for that :). Are those 25 worker nodes virtual machines? How did you attatch the disks to the ceph nodes?

Im not using any hypervisor (yet), but in the feature im probably going to look at proxmox.

Never heard of cloudstack before but what i just read and what you described sounds really intresting!

27 nodes in 12 minutes sounds insane :)

Other people also recommanded this to me, i will take a look at it! Thanks!!!

Oh alright, thanks for explaining!

And does this work for ingress? I searched a little bit around but as far as i understand metallb is for k8s services?

Thanks for your reply, i havent look into metallb before but i will try it out!

Currently I only will need to use it for k8s so kube-vip will do the job for now.