New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
network config
Hi All,
I have two machines
Hetzner Cloud (10.0.0.3)
interfaces:
- interface: eth0
dhcp: true
routes:
- network: 10.1.0.0/16
gateway: 10.0.1.1
metric: 100
- network: 10.0.0.0/16
gateway: 10.0.1.1
metric: 100
Hetzner Dedicated (10.1.0.2) and Hetzner Cloud and Dedicated are connected via vSwitch
interfaces:
- interface: eth0
dhcp: false
addresses:
- 10.1.0.2/24
routes:
- network: 10.1.0.0/16
gateway: 10.1.0.1
metric: 200
#mtu: 9000
- interface: eth1
dhcp: true
vlans:
- vlanId: 4001
addresses:
- 10.0.1.2/24
mtu: 1400
routes:
- network: 10.1.0.0/16
gateway: 10.0.1.1
metric: 100
- network: 10.0.0.0/16
gateway: 10.0.1.1
metric: 100
Note: eth0 is LAN and dont have connectivity to Hetzner Cloud, only VLAN 4001 have connectivity to Hetzner Cloud
My requirement is
1) 10.0.0.3 should be able to reach 10.1.0.2
2) 10.1.0.2 should be able to reach 10.0.0.3
What is wrong in above config?
Comments
Did you contact Hetzner? Probably a vlan / internal NW issue to the cloud.
I verified. I have no issues connecting 10.0.0.3 to 10.0.1.2 and vice versa.
I want 10.0.0.3 to reach 10.1.0.2 via the eth1 interface.
1) is it possible?
2) do the above config is correct for that
ChatGPT says:
Before I am posting here, I verified the same with ChatGPT. Even though it says there is no issue in it.
But I cannot ping 10.1.0.2 from 10.0.0.3.