| 17 Jan 2025 |
 magic_rb | but then you have to match up the networks, which is your problem right now i think | 22:26:35 |
 zeno | 
Download image.png | 22:26:50 |
| magic_rb | also then the server shouldnt be a trunk, but generally id avoid this scenario and instead use a trunk | 22:26:52 |
| magic_rb | right yeah okay, then its weird why the packet arrived on vlan4, should have arrived untagged | 22:27:30 |
| magic_rb | check the desktop side | 22:27:34 |
| zeno | 
Download image.png | 22:28:07 |
| magic_rb | that doesnt quite match the diagram | 22:28:37 |
| magic_rb | :) | 22:28:37 |
| magic_rb | you gotta figure out what precisely youre trying to do, because i think we're both getting lost | 22:28:51 |
| zeno | I- is that a good sign? | 22:28:54 |
| zeno | lol | 22:29:00 |
| magic_rb | dunno :) | 22:31:38 |
| zeno | Say e.g. k8s: I used to write up scripts like the one below and just publish the service on VLAN 4 and it just werked®
---
apiVersion: "v1"
kind: "Service"
metadata:
name: "immich-service"
namespace: "immich"
spec:
selector:
app.kubernetes.io/instance: "immich"
app.kubernetes.io/name: "server"
ipFamilyPolicy: "SingleStack"
ipFamilies:
- "IPv4"
ports:
- name: "immich-webui"
port: 2283
targetPort: "http"
protocol: "TCP"
type: "LoadBalancer"
loadBalancerIP: "192.168.7.50"
| 22:32:32 |
| zeno | * Say e.g. k8s: I used to write up scripts like the one below and just publish the service on VLAN 4 and it just werked®
---
apiVersion: "v1"
kind: "Service"
metadata:
name: "immich-service"
namespace: "immich"
spec:
selector:
app.kubernetes.io/instance: "immich"
app.kubernetes.io/name: "server"
ipFamilyPolicy: "SingleStack"
ipFamilies:
- "IPv4"
ports:
- name: "immich-webui"
port: 2283
targetPort: "http"
protocol: "TCP"
type: "LoadBalancer"
loadBalancerIP: "192.168.4.50"
| 22:32:42 |
| zeno | I am kinda lost... especially now that you're telling me that it isn't possible | 22:33:41 |
| zeno | I've been living a lie | 22:33:46 |
| zeno | Anyway | 22:34:34 |
| zeno | I guess my follow-up question now is: when people have a server running e.g. Proxmox and have various VMs running on it, how do they have these VMs on different VLANs and still get it to work? | 22:36:44 |
| magic_rb | you can have them on different vlans | 22:37:20 |
| magic_rb | but youre mixing your nets | 22:37:27 |
| magic_rb | the primary problem is the address you have on your PC rn | 22:37:36 |
| magic_rb | its 192.168.2.100 when it must be 192.168.4.100 | 22:37:46 |
| zeno | Yes, but how can they reach them? | 22:37:46 |
| magic_rb | well you must have a router which routers between the vlans | 22:38:06 |
| zeno | So the server would have to physically be on that network? | 22:38:07 |
| zeno | Physical or can you route on a switch? | 22:38:29 |
| magic_rb | id keep to the 1 vlan == 1 network mapping ideally | 22:38:31 |
| magic_rb | you cant route on a switch a switch isnt a router | 22:38:43 |
| magic_rb | but the thing you have i doubt is a switch | 22:38:48 |
| magic_rb | it sounds like a L3 switch, ie a dumbed down router | 22:39:02 |
