You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need help with troubleshooting my homelab dhcp issue; which is working on one interface (ens18) but not the other (ens19); while webgui and dns is working on both.
edit restarting the container hints at the issue indeed, but how do I change this?
INF ts=1733816158.2315943 logger=role.dhcp msg=starting DHCP Server instance=network-ha-1 version=0.18.0+f925061b port=67 interface=ens18
Edit2: in the meantime the way I solved this is by having dhcp-relay from vlan30 to vlan22.
Rest of the original post:
My current setup is:
server network across vlan 22
client network across vlan 30
Gravity initial configuration & setup was on vlan 22. There it's working. I'm using "network_mode: host" and I set "INSTANCE_LISTEN: 0.0.0.0"
I've added a second nic to also add dns & dhcp to my client network via gravity. Dns is working fine, DHCP on the other hand is not. The host where gravity is hosted has its: 172.22.2.1 on ens18/vlan22 and 172.30.1.2 on ens19/vlan30.
The webgui is available on both, dns-resolution is available on both. But DHCP doesn't respond on the ens19-nic.
My dhcp config for 172.22 is:
And for 172.30 is:
if I run discovery on the 172.30 subnet I find myself but also the default gateway (my unifi router) and any static ip clients configured.
The network config from the server where gravity is on:
I have a VM previously used for syncthings that I'm testing with. If I add it's nic to the vlan 30 group and assign a static IP I can ping as well as dns request, which the gravity instance answers. Proof is screenshot 1 - 3.
However when I try set the nic to dhcp and try to get an ip, no response from gravity. see screenshot 4.
The switch is vlan aware and routing is disabled between them, so vlan 30 can only communicate with vlan 30.
My gut feeling is that; much like dns with the instance_listen config I need to tell the dhcp-daemon that it needs to listen on all interfaces. But with my google fu I don't know how to do that with etcd & dhcp. I can't seem to find any config or run any command that might be related to etcd dhcp.
But is this really the problem and if not do you have guidance on how to troubleshoot this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I need help with troubleshooting my homelab dhcp issue; which is working on one interface (ens18) but not the other (ens19); while webgui and dns is working on both.
edit restarting the container hints at the issue indeed, but how do I change this?
Edit2: in the meantime the way I solved this is by having dhcp-relay from vlan30 to vlan22.
Rest of the original post:
My current setup is:
Gravity initial configuration & setup was on vlan 22. There it's working. I'm using "network_mode: host" and I set "INSTANCE_LISTEN: 0.0.0.0"
I've added a second nic to also add dns & dhcp to my client network via gravity. Dns is working fine, DHCP on the other hand is not. The host where gravity is hosted has its: 172.22.2.1 on ens18/vlan22 and 172.30.1.2 on ens19/vlan30.
The webgui is available on both, dns-resolution is available on both. But DHCP doesn't respond on the ens19-nic.
My dhcp config for 172.22 is:
And for 172.30 is:
if I run discovery on the 172.30 subnet I find myself but also the default gateway (my unifi router) and any static ip clients configured.
The network config from the server where gravity is on:
I have a VM previously used for syncthings that I'm testing with. If I add it's nic to the vlan 30 group and assign a static IP I can ping as well as dns request, which the gravity instance answers. Proof is screenshot 1 - 3.
However when I try set the nic to dhcp and try to get an ip, no response from gravity. see screenshot 4.
The switch is vlan aware and routing is disabled between them, so vlan 30 can only communicate with vlan 30.
My gut feeling is that; much like dns with the instance_listen config I need to tell the dhcp-daemon that it needs to listen on all interfaces. But with my google fu I don't know how to do that with etcd & dhcp. I can't seem to find any config or run any command that might be related to etcd dhcp.
But is this really the problem and if not do you have guidance on how to troubleshoot this?
1
2
3
4
Beta Was this translation helpful? Give feedback.
All reactions