Je cherche un contrat d'apprentissage en système et réseau. L'école dans laquelle j'ai été pris est l'ENI de Quimper, BTS TSSR.
J'ai une large préférence pour:
le Finistère
les collectivités territoriales, services publiques non répressifs, service hospitalier, radio...
les logiciels libres et open source (#proxmox, #debian, #gns3, etc.)
(Et je parle un peu breton...)
Bon, je suis complètement à court d'idées, j'ai besoin d' #aide sur du #reseau sur ce serveur... Si vous avez une idée ou si vous pouvez partager, j'en peux plus là
Le serveur qui fait tourner cette instance est sur un #proxmox. Jusqu'ici, tout allait bien.
Hier, suite à un plantage, j'ai du reboot le serveur (VPS chez Ionos). Après redémarrage, impossible d'accéder à quoi que ce soit : Interface Proxmox, services dans les conteneurs, rien.
La configuration était la suivante :
Interface externe (ens6) et 2 bridges :
vmbr0, en bridge-port sur ens6 (avec donc son ip publique), utilisé pour l'administration
vmbr1, avec une ip dans un réseau en 192.168.2.0/24 qui sert les conteneurs (reverse proxy pour un et docker pour l'autre)
J'ai dans mon fichier d'interfaces pour vmbr1 ceci :
Après debug, j'ai vu que le trafic passait à nouveau lorsque je foutais en down VMBR0.
J'ai donc, dans l'urgence, changé mes règles pour retirer vmbr0 et le changer par ens6, qui est le nom d'interface "physique".
J'ai pu constater que tout était revenu : accès à l'interface de proxmox, accès aux conteneurs... tout sauf, un point important : impossible depuis le serveur d'utiliser sa propre ip publique.
Par exemple, impossible pour l'instance d'envoyer un mail (le conteneur de mailing est situé derrière la même ip), impossible même depuis le shell de proxmox... ou encore impossible de renouveler les certificats sur le conteneur qui fait reverse.
Für einen Werkvertrag an der UdK wird ein Mensch gesucht, der sich mit #Proxmox, #Virtualisierung, #GPU und #SysAdmin auskennt. Ich stehe selbst gerne zur Seite, habe nur gerade keine Ressourcen den jeweiligen Profs selbst zu helfen.
Ist tendenziell eine eher einmalige Sache zur Einrichtung eines Multi-GPU Systems; aber so Projekte laufen ja manchmal dann doch länger.
Obligatory yearly toot about #FOSS so I can stay on #Fosstodon 🎉
I saw the other day that German state Schleswig-Holstein is going to switch to fully #FOSS. Which is great and hope it works out for them.
Having set up a fully (F)OSS (desktops, apps, servers, etc) IT env for a large non-profit, might I suggest proper enterprise support instead of a lone coffee-addicted sysadmin who tries to keep systems together with hopes, prayers and duct tape? 🥲
That is not to say that everything was bad. Users liked working with #LinuxMint (still my fav distro), #RocketChat and #NextCloud were popular as well. Zimbra as a mailserver was ok, there were a few complaints about the scheduling tool. #Jitsi worked well, at times. I'm trying to remember the other apps that we used.
We had in-house servers with I believe #Proxmox and #Ubuntu vm's on top, managed by #Ansible. That all worked really well. One or 2 Windows VM's for legacy apps.
Hrm, I think I'm calling it a day (or a night). Couldn't figure out yet why on this #Proxmox server a Linux bridge wouldn't forward #Multicast Router Discovery (#MRD) messages generated via @troglobit's mrdisc. While sending to ff02::6a via ICMPv6 echo request or UDP works just fine...
Disabling multicast snooping on the bridge does not help either. Nor does "ebtables -I FORWARD -p IPv6 --ip6-destination ff02::6a -j ACCEPT".
Likely sth. with the #ip6tables with nf-call-ip6tables enabled...
Today I pondered something: Proxmox and others boast native ZFS integration as one of their strengths. Many Proxmox features rely on ZFS's unique capabilities, and many setups are built around them. If Oracle were to send a cease and desist tomorrow, how would the situation unfold?
#homelab Hello there. I have bought a beelink s12 pro. It has 16g memory on board. However, I have heard that a #intel n100 can run with 32G.
Who has an intel n100 or beelink s12 pro and can tell me what 32G memory works well with it?
Also I heard rumours it will run 32G but can never use more than 16G.
Any tips apreciated and please boost! #proxmox#linux#n100
I have a #proxmox problem where it looks like id's in the webgui are wrong.
If I connect to the command prompt it connects to the wrong vm. #homelab
Anybody see that problem before?
And know what to do perhaps?
Happens on #alpine vm's without kvm-client running
Am gestrigen Regentag nahm ich meinen Mut zusammen wollte meinen #Heimserver von #Proxmox 6.4 auf 7.x updaten. Viel zu spät war ich dran, aber es lief seit Jahren alles so schön fehlerfrei. Leider fror das Upgrade bei 58 % ein. Ich konnte herausfinden, dass es etwas mit „memtest“ zu tun hat. Nachdem ich diesen Prozess abschoss, lief das Upgrade bis zum Ende durch jedoch nicht fehlerfrei: Ich kam nicht mehr ins Proxmox-Gui, da „pveproxy“ und „pveservice“ (oder so) nicht mehr starteten. 😞 1/3
I've got the 192.168.1.x network with HA in there. Now, I've got an #OpenWrt router with the IP 192.168.1.190 creating 2 new networks: 192.168.100.x. I now want to get the HA into the 192.168.100.x network, but I can't connect it physically, as both the OpenWrt and HomeAssistant run in containers/VMs on #proxmox. I tried experimenting with IP routes, but no success. Does anyone have a clue for me?
This post is really a small collection of thoughts about Proxmox when used in a home lab situation and home labs in general. I was originally going to post this to Mastodon only but it didn't fit in a single post.
A lot of people (at least what I see on reddit) build Proxmox systems with shared file systems like ceph, even for home lab use.
Ugh, FINALLY got around to getting the last few drives installed in the new rackmount chassis. Figured while I was at it to go ahead and swap out for a beefy #ryzen7 with integrated #radeon graphics since it's a slim build! 😎
#proxmox is up and running, and before long, the #homelab will have another domain controller and some other dedicated #dev machines! 🙌🤘💯 :nixos: :windows: #server#programming
Ok this is maybe a dumb me thing but ever since I migrated #HomeAssistant to an LXC on #Proxmox it has been losing HACS-downloaded components in restart. I used the same docker-compose file I used when I had it on metal, so I'm very confused.
Keep getting tx hang errors on #VMware#ESXi with my #Kubernetes cluster nodes (likely due to a busy ingress?). So fucking tempted to migrate to #Proxmox, but 1) how would I be able to retain my existing servers (half of which are pretty critical) and 2) idk if it would even be a fix for this specific issue.
#Homelabber (s) with experience with both for their #homelab (s), feel free to chime in for any differences between the two - I'm also interested in how compatible Proxmox is with general desktop hardware. My ESXi based server uses pretty much all off the shelf desktop parts (Ryzen 7 1700, B450, etc.) and it's been serving me well, tho I did have to customise the installer ISO and add some drivers for the SATA ports and NIC.
DO NOT #update to #ubuntu#24.04 on #LXC if you use #proxmox, the containers will NOT start. I believe this is something that needs to be fixed by the proxmox team as they seems to be checking for ubuntu version manually in a startup script
#homelab
Hi, I am using this little box with an intel n100
In #proxmox vm, to get a fast #nftables linux vm, should I select 1 socket 4 cores?
Or will nftables work the same speed on 1 core? #linux