So I got the task to rebuild the computing cluster for our research group.
Unfortunately I have no education in networking whatsoever, so all I could do is google.
So we have a HP Proliant server running Proxmox.
The Proliant server is connected to the institutes network. Lets call this network A (x.x.9.0./21)
In proxmox I created a VM running ubuntu serrver 24.04.
In proxmox I defined two linux bridges:
vmbr0 with port eno1 and CIDR x.y.9.4/21 (which is also how I access proxmox via the browser) and gateway x.x.8.254
vmbr1 with port eno2 and CIDR 192.168.0.1/24
I have assigned both these network devices to the Ubuntu Server. Which is therefore connected to network A, with the assigned ip of x.y.9.1, and to network B (all connected to a TP-Link switch), with the assigned ip of 192.168.0.1 .
Now I have an additional supermicro server which is connected to the switch and has an assigned ip of 192.168.0.31.
From the ubuntu server I can ping the supermicro aswell as my office pc (x.y.9.66).
Unfortunately I dont seem to be able to ping the supermicro from my office pc or the otherway around.
on the ubuntu server yields:
on my office pc yields:
Now I can't even ping 192.168.0.1 from my office pc as all I get is:
However I can ssh on it using the ip 192.168.0.1.
Any idea what might be the issue?
All im trying to do is setting up HTCONDOR in a seperate network...
Unfortunately I have no education in networking whatsoever, so all I could do is google.
So we have a HP Proliant server running Proxmox.
The Proliant server is connected to the institutes network. Lets call this network A (x.x.9.0./21)
In proxmox I created a VM running ubuntu serrver 24.04.
In proxmox I defined two linux bridges:
vmbr0 with port eno1 and CIDR x.y.9.4/21 (which is also how I access proxmox via the browser) and gateway x.x.8.254
vmbr1 with port eno2 and CIDR 192.168.0.1/24
I have assigned both these network devices to the Ubuntu Server. Which is therefore connected to network A, with the assigned ip of x.y.9.1, and to network B (all connected to a TP-Link switch), with the assigned ip of 192.168.0.1 .
Now I have an additional supermicro server which is connected to the switch and has an assigned ip of 192.168.0.31.
From the ubuntu server I can ping the supermicro aswell as my office pc (x.y.9.66).
Unfortunately I dont seem to be able to ping the supermicro from my office pc or the otherway around.
Code:
ip route show
Code:
default via x.y.8.254 dev ens18 proto static
x.y.8.0/21 dev ens18 proto kernel scope link src x.y.9.1
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.0.0/24 dev ens19 proto kernel scope link src 192.168.0.1
Code:
ip route show
Code:
default dev tun0 scope link
default via x.y.8.254 dev enp34s0 proto static metric 100
x.y.8.0/21 dev enp34s0 proto kernel scope link src x.y.9.66 metric 100
131.220.224.202 via x.y.8.254 dev enp34s0 src x.y.9.66
131.220.247.0/24 dev tun0 scope link
169.254.0.0/16 dev enp34s0 scope link metric 1000
192.168.0.0/24 via x.y.9.1 dev enp34s0 proto static metric 100Now I can't even ping 192.168.0.1 from my office pc as all I get is:
Code:
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.1 icmp_seq=1 Packet filtered
From 192.168.0.1 icmp_seq=2 Packet filtered
From 192.168.0.1 icmp_seq=3 Packet filtered
^C
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2053msHowever I can ssh on it using the ip 192.168.0.1.
Any idea what might be the issue?
All im trying to do is setting up HTCONDOR in a seperate network...